Infrastructure » DataONE API

Replicas provide assurance to users that an object will be available into the future. There are some cases where content has not be replicated, for example, immediately after a new member node comes online, much if not all of the content will not be replicated; or in the general case, any new object will have some time before it is replicated; some content may not be replicated by policy.

Since replication is one of the foundations of access assurance, DataONE should be advertising the available assurance to end users, so that they may be informed that for reasons outside of DataONE's control, that content may not be reliably available.

The focus of this story is on how client tools should be making this information available in a consistent manner to end users, and also to define som language describing the relative stability of content based on the number of replicas (and perhaps some additional information about the member node reliability)