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 35 - Query Coordinating Node for Metadata Describing a Member NodeΒΆ

Revisions
View document revision history.
Goal
Describe a member node, especially API endpoints
Summary

Naive clients may want to find out more about member nodes before interacting with them. In particular, clients need to determine the API endpoints for the Member Node. Information supplied might include the capabilities supported and state of health summary.

Such information is also useful to Coordinating Nodes for determining content replication policies and rules.

Actors
  • Coordinating Node
  • Client requesting info
Preconditions
  • Coordinating Nodes are operational
Triggers
  • Request by client
Post Conditions
  • Client has locations where data object can be retrieved

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.