You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "Chris A. Mattmann (Assigned) (JIRA)" <ji...@apache.org> on 2012/01/16 04:17:50 UTC
[jira] [Assigned] (OODT-368) Refactoring of metadata extraction
functionality for opendapps module
[ https://issues.apache.org/jira/browse/OODT-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann reassigned OODT-368:
--------------------------------------
Assignee: Chris A. Mattmann
> Refactoring of metadata extraction functionality for opendapps module
> ---------------------------------------------------------------------
>
> Key: OODT-368
> URL: https://issues.apache.org/jira/browse/OODT-368
> Project: OODT
> Issue Type: Improvement
> Components: opendapps
> Affects Versions: 0.4
> Reporter: Luca Cinquini
> Assignee: Chris A. Mattmann
> Attachments: opendapps-asf-20120105.patch
>
>
> The main purpose of this patch is to refactor the metadata parsing functionality into an extensible framework of MetadataExtractors. The MetadataExtractor interface defines the general capability of parsing a metadata source and adding (name,value) pairs into the CAS metadata container. The existing code for parsing THREDDS metadata catalogs has been moved from the DatasetCrawler class to a ThreddsMetadataExtractor that implements the aforementioned interface. Additionally, another implementation, DasMetadataExtractor, has been added to parse an Opendap DAS stream and capture the NetCDF global attributes (for now). Finally, an NcmlMetadataExtractor has been added as a stub implementation for future parsing of NcML documents.
> The patch also contains the following changes and additions:
> o The OODT profiles are assigned a UUID as identifier, since the THREDDS dataset ID is used as the resource identifier
> o The THREDDS catalogs are parsed to extract the CF standard names and variable long names, where found
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira