oodt-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris A. Mattmann (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OODT-225) Augment cas-filemgr with the ability to deal with product collections
Date Fri, 14 Dec 2012 00:34:13 GMT

     [ https://issues.apache.org/jira/browse/OODT-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

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

    Fix Version/s:     (was: 0.5)
                   0.6

- push out to 0.6
                
> Augment cas-filemgr with the ability to deal with product collections
> ---------------------------------------------------------------------
>
>                 Key: OODT-225
>                 URL: https://issues.apache.org/jira/browse/OODT-225
>             Project: OODT
>          Issue Type: New Feature
>          Components: file manager
>         Environment: from the JPL internal JIRA
>            Reporter: Chris A. Mattmann
>            Assignee: Chris A. Mattmann
>             Fix For: 0.6
>
>
> This is an issue to track progress towards giving the file manager the ability to deal
with product collections. Collections are defined as one or more products, and an associated
metadata object. The major design trade off is going to be the level of granularity with regards
to how the filemgr will provide collections, in other words, will the file manager natively
support a collections object? Or, will the filemgr support collections through the use of
additional meta-information in the product object?
> I'm leaning towards natively creating an core filemgr object, called ProductCollection,
and adding an attribute to the Product class of type ProductCollection, that is an instance
of the ProductCollection for which the Product belongs to. So, the Product class would have
an additional field, like:
> {code:java}
> private ProductCollection collection;
> {code}
> and we'd have an additional class like:
> {code:java}
> public class ProductCollection{
> private String id;
> private String name;
> private List<Product> products;
> private Metadata met;
> //....
> }
> {code}
> Collection information would be transferable via XML-RPC using an external API that we
would add to the filemgr to support dealing with Collections. The API would look like:
> {code:java}
> public interface Collectable{
> public ProductCollection getCollection(Product p);
> public void addProductToCollection(Product p, ProductCollection c);
> public List<Product> getProducts(ProductCollection c);
> public Metadata getCollectionMetadata(ProductCollection c);
> }
> {code}
> One open issue is whether or not a Product can belong to multiple ProductCollections.
I think that ultimately it should be able to, but to keep the API clean and simple for now,
we'll restrict a Product's membership to a single ProductCollection.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message