[ 
https://issues.apache.org/jira/browse/OODT-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969361#action_12969361
 ] 

Paul Ramirez commented on OODT-72:
----------------------------------

There seems to be an underlying backwards compatibility issue here that is not 
being discussed. It's probably not a great idea to change the order of ingest 
operations after there are many systems deployed that already account for this 
behavior. Not to say that this should never be done but just that extreme 
caution should be taken with this type of change. If any of the steps of the 
ingestion process get changed they should by default work as they do now to 
support backwards compatibility. However, when we went down this path before it 
seemed to cascade into larger changes. At first blush it might seem that this 
is a move an call down a few lines but the unintended side affects could really 
be bigger. 

It would be helpful to add in some concrete examples of "FileLocation being set 
based off Product References". In addition, anything else that would need to 
leverage the product references to generate metadata. I think if we flush that 
out this will help flush out if the ingestion process has an issue that needs 
to be resolved.

> 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.

Reply via email to