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 36 - Resolve an Object LocationΒΆ

Revisions
View document revision history.
Goal
Communicate the locations where a DataONE object can be found
Summary

Within DataONE, a registered object may be held on one or more Member Nodes (depending on replication policy) and in the case of science metadata, on Coordinating Nodes. Clients must be able to ask a Coordinating Node for those locations.

The response to this query is a list of member node identifiers and the URL endpoint of their DataONE API implementation.

The client will need to retrieve information about the node from the node registry (Use case 35) in order to accurately determine the URL that can be used to retrieve the object bytes (Use case 01).

Actors
  • Coordinating Node
  • Client requesting info
Preconditions
  • Coordinating Nodes are operational
  • Client has an identifier for an object
  • Object exists in the DataONE system and has been recorded by the Coordinating Nodes
Triggers
  • Request by client
Post Conditions
  • Client has more information about the location of the object.
../../_images/36_uc.png

Figure 1. Use case diagram for Use Case 36.

../../_images/36_seq.png

Figure 2. Sequence diagram for implementation of use case 36.

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.