[kepler-dev] [Bug 2572] - Export KAR can produce several actors with the same lsid

bugzilla-daemon@ecoinformatics.org bugzilla-daemon at ecoinformatics.org
Fri Jun 15 12:27:44 PDT 2007


berkley at nceas.ucsb.edu changed:

           What    |Removed                     |Added
             Status|NEW                         |ASSIGNED
   Target Milestone|Unspecified                 |1.0.0

------- Comment #1 from berkley at nceas.ucsb.edu  2007-06-15 12:27 -------
This is a problem with how we store lsids in the cache.  The problem is that
the generated kar file does not get cached when it is created (although it
could be cached later).  If we store the lsid in the database upon kar
creation, it will have to get a new lsid when it is inserted into the cache
(because there is no way to know that the object being put into the cache is
the same as the one that was created earlier since we lose control of it). 
Another way around this is to ask the user if they wish to get a unique lsid or

The heart of this is that we still need a centralized way to keep track of
lsids.  We are still dependent on the local machine to generate ids, which in
no way guarantees they are unique.  To really fix a lot of these ID issues, we
need a central ID repository (or we need to use library.kepler-project.org as

More information about the Kepler-dev mailing list