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 (JIRA)" <ji...@apache.org> on 2011/06/19 09:51:47 UTC

[jira] [Created] (OODT-266) Product Manifest Ingester

Product Manifest Ingester
-------------------------

                 Key: OODT-266
                 URL: https://issues.apache.org/jira/browse/OODT-266
             Project: OODT
          Issue Type: New Feature
          Components: file manager
         Environment: JPL internal JIRA
            Reporter: Paul Ramirez
            Assignee: Paul Ramirez
             Fix For: 0.4


Create an product manifest ingester to archive a product based on references listed in a file. The manifest file will likely only need file references for items to be included and a reference to the metadata file for the product. It may be that the metadata file is not even referenced in the manifest for the first go around. An examination of how the other ingesters gather metadata will be done first and the same methodology should be followed. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (OODT-266) Product Manifest Ingester

Posted by "Chris A. Mattmann (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OODT-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris A. Mattmann updated OODT-266:
-----------------------------------


- push out to 0.5
                
> Product Manifest Ingester
> -------------------------
>
>                 Key: OODT-266
>                 URL: https://issues.apache.org/jira/browse/OODT-266
>             Project: OODT
>          Issue Type: New Feature
>          Components: file manager
>         Environment: JPL internal JIRA
>            Reporter: Paul Ramirez
>            Assignee: Paul Ramirez
>             Fix For: 0.5
>
>
> Create an product manifest ingester to archive a product based on references listed in a file. The manifest file will likely only need file references for items to be included and a reference to the metadata file for the product. It may be that the metadata file is not even referenced in the manifest for the first go around. An examination of how the other ingesters gather metadata will be done first and the same methodology should be followed. 

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

        

[jira] [Updated] (OODT-266) Product Manifest Ingester

Posted by "Chris A. Mattmann (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OODT-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris A. Mattmann updated OODT-266:
-----------------------------------

    Fix Version/s:     (was: 0.4)
                   0.5

- push to 0.5
                
> Product Manifest Ingester
> -------------------------
>
>                 Key: OODT-266
>                 URL: https://issues.apache.org/jira/browse/OODT-266
>             Project: OODT
>          Issue Type: New Feature
>          Components: file manager
>         Environment: JPL internal JIRA
>            Reporter: Paul Ramirez
>            Assignee: Paul Ramirez
>             Fix For: 0.5
>
>
> Create an product manifest ingester to archive a product based on references listed in a file. The manifest file will likely only need file references for items to be included and a reference to the metadata file for the product. It may be that the metadata file is not even referenced in the manifest for the first go around. An examination of how the other ingesters gather metadata will be done first and the same methodology should be followed. 

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