[
https://issues.apache.org/jira/browse/OODT-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann resolved OODT-72.
-----------------------------------
Resolution: Fixed
- took care of this in r1054155. I documented the property I added
{code}org.apache.oodt.cas.filemgr.metadata.expandProduct{code} which made more
sense to me. I set it to false by default, so we are fully backwards compat
with existing FMs. Note, in rr1054000, I added a FilemgrMetExtractor that can
also be used to set {code}FILE_LOCATION{code} based on calling a Versioner. I
think this really represents the best of all of the suggested approaches in the
issue.
Thanks to bfost for the healthy debate and for making this the best patch it
could be.
> Unable to set Metadata based off Product Versioning during Product ingestion
> ----------------------------------------------------------------------------
>
> Key: OODT-72
> URL: https://issues.apache.org/jira/browse/OODT-72
> Project: OODT
> Issue Type: Improvement
> Components: file manager
> Affects Versions: 0.1-incubating
> Environment: none
> Reporter: Brian Foster
> Assignee: Chris A. Mattmann
> Priority: Minor
> Fix For: 0.2
>
>
> Ingest order:
> - add product to catalog
> - metextractors run
> - add metadata to catalog
> - versioner runs (on client or on server)
> - add references to catalog
> This prevents Metadata elements such as FileLocation from being set based off
> Product References since metadata is added to catalog pre-versioning
> - A known work-around is to run the versioner twice (once in a MetExtractor
> and again when the Versioner is run in the ingest process) . . . however this
> is very much a work-around and setting elements such as FileLocation is a
> very common functionality.
> I purpose that Versioning take place before MetExtractors run.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
