You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by "Suresh Marru (Updated) (JIRA)" <ji...@apache.org> on 2012/03/12 21:02:43 UTC
[jira] [Updated] (AIRAVATA-52) [GSoC] Create OODT File Manager
extension for Airavata
[ https://issues.apache.org/jira/browse/AIRAVATA-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Suresh Marru updated AIRAVATA-52:
---------------------------------
Component/s: GFac
Description: Create an OODT File Manager extension point for Airavata for data and workflow cataloging. Also investigate the use of cas-catalog from OODT too. Airavata GFac has an data cataloging interface which by default publishes to the Airavata registry. An implementation to use the rich data cataloging features of OODT will enhance the users to store and retrieve richer metadata from workflow execution. (was: Create an OODT File Manager extension point for XBaya for data and workflow cataloging. Also investigate the use of cas-catalog from OODT too.)
Labels: gsoc2012 mentor (was: gsoc2012)
Summary: [GSoC] Create OODT File Manager extension for Airavata (was: [GSoC] Create OODT File Manager extension for XBaya)
> [GSoC] Create OODT File Manager extension for Airavata
> ------------------------------------------------------
>
> Key: AIRAVATA-52
> URL: https://issues.apache.org/jira/browse/AIRAVATA-52
> Project: Airavata
> Issue Type: New Feature
> Components: GFac, XBaya
> Reporter: Chris A. Mattmann
> Priority: Minor
> Labels: gsoc2012, mentor
> Fix For: WISHLIST
>
>
> Create an OODT File Manager extension point for Airavata for data and workflow cataloging. Also investigate the use of cas-catalog from OODT too. Airavata GFac has an data cataloging interface which by default publishes to the Airavata registry. An implementation to use the rich data cataloging features of OODT will enhance the users to store and retrieve richer metadata from workflow execution.
--
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