[
https://issues.apache.org/jira/browse/OODT-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969208#action_12969208
]
Brian Foster commented on OODT-72:
----------------------------------
- aside from wrapping the versioner inside a MetExtractor there is NO way, when
using the ingestProduct method, to set FileLocation . . . and this requires the
MetExtractor to dynamically load the Versioner and create a cloned Product
object so to trick the Versioner into thinking it is filling the References for
the actual Product, so that the References can then be retrieved from this
cloned Product and then FileLocation set based off that . . . then later the
versioner is again dynamically loaded and re-run on the actual Product object
used for ingestion.
- the Metadata object could be cloned before calling the versioner . . . that
would address your "un-modifiable metadata" conserns
------------
An alternative solution might be to optionally have the filemgr fill a
FileLocation like metadata field when retrieving a Product's Metadata . . .
FileLocation doesn't necessarily need to be stored in the catalog as it
typically is not queried on
> 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: Brian Foster
> 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.
