[kepler-dev] [Bug 4581] New: - Handle multiple revisions of components in the Component Library

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=4581

           Summary: Handle multiple revisions of components in the Component
                    Library
           Product: Kepler
           Version: 1.x dev
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P3
         Component: actors
        AssignedTo: aschultz at nceas.ucsb.edu
        ReportedBy: aschultz at nceas.ucsb.edu
         QAContact: kepler-dev at kepler-project.org


It is possible for many different revisions of an object to contain the same
semantic types.  The question is how to handle this in the Component Library.

Imagine you have two different KARS
one with a component, urn:lsid:someauth:namespace:24:10
and the other with a component,  urn:lsid:someauth:namespace:24:11
both of which have equivalent semantic types.

These two components should show up properly in the Ontology tree in the
Component Library but since they would be in the same place there is a
collision.  For this reason, LSID cannot be used as the identifier in the
Component Library.  The new Library Index has a unique Library Index ID (LIID)
for each item that shows up in the Component Library tree.  With this LIID we
can associated multiple LSIDs with any given LIID (see LIBRARY_LSIDS table in
the sql).

This problem is not limited to LSID revisions.  But also objects that have the
same name and the same semantic type.