[
https://issues.apache.org/jira/browse/OODT-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187109#comment-13187109
]
Luca Cinquini commented on OODT-368:
------------------------------------
Thanks Chris, this is awesome. Are you saying I forgot the Apache license ?
Sorry about that...
As for the import comment on packages.... that is an Eclipse feature, I tend to
use Eclipse to re-organize and prune the imports automatically, so we don't
have stale imports. The drawback is that all comments are removed :(.
Anyway, this is great, I'll move on with the latest patch, at least for now.
thanks, Luca
> 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
> Fix For: 0.4
>
> 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
