Warning: These documents are under active development and subject to change (version 2.1.0-beta).
The latest release documents are at: https://purl.dataone.org/architecture

Use Case 38 - Reserve an IdentifierΒΆ

Revisions
View document revision history.
Goal
Reserve an identifier to ensure it is available at some reasonable time in the future.
Summary
As new content is added to the DataONE system, it is desirable to reserve an identifier in advance of creating the content as it is necessary for the client to generate relationships between content that may not exist in the DataONE system (e.g. a new data set with associated science metadata).
Actors
ITK, Coordinating Node
Preconditions
  • CN and MN operational
Triggers
  • A client needs to reserve an identifier so that associations can be created in the system metadata
Post Conditions
  • An identifier is reserved and guaranteed to be unique for some finite period of time.
../../_images/38_uc.png

Figure 1. Use case 38. Note that id a Member Node needs to reserve an identifier then it would use the functioanlity of the Investigator Toolkit Library - that is, the reserveIdentifier operation is not required for Member Node functionality.

../../_images/38_seq.png

Figure 2. Sequence diagram for use case 38. The Coordinating Node needs to keep track of identifiers that have been reserved, and this information needs to be replicated between Coordinating Nodes. The reserved identifier should not be discoverable and should not be involved with any Member Node synchronization or Member Node replication.

This material is based upon work supported by the National Science Foundation under Grant Numbers 083094 and 1430508.

Any opinions, findings, and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the National Science Foundation.