LSID Registration Services

STATUS:

The content on this page is outdated. The page is archived for reference only. For more information about current work see Kepler Life Science Identifiers (KeplerLSIDs)

Overview

In order to keep track lf LSIDs within the kepler system and to make syncing the local and remote systems easier, we need to develop a remote registrar of LSIDs. This system should be available on the Ecogrid and should allow developers and users to register LSIDs which then can never be used again.

Use Cases

1. User creates a new component in Kepler and needs an LSID for the component. The user requests a new LSID with a specified namespace (scope). The system returns the next available object for that namespace.
2. User creates an updated version of an existing component and needs a new revision number. The user requests a revision number from the LSID registrar. The system responds with the newest revision number for that object.
3. User would like to register his/her own namespace. The user requests the namespace with an object id of 1 and revision id of 1. The system responds with either an error message if the namespace is already in use or an affirmation message if the request was successful.
4. User adds a new external component to Kepler. An LSID is requested. This is basically the same as UC1.

Functions

• void addLSID(KeplerLSID lsid)
• void getNextObject(KeplerLSID lsid)
• void getNextRevision(KeplerLSID lsid)
• boolean isRegistered(KeplerLSID lsid)

Problems with Metacat ID system

1. If you've registered x.1.2 you can't go back and register x.1.1
2. full lsids are not stored so we loose the authority information

Questions

1. Should this be implemented as part of Metacat or standalone
   • If it's standalone, how do we make sure that the ids in the standalone LSID repository are kept up to date with what is in the component repository (metacat)
2. What do we do with offline systems