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 32 - Transfer Object OwnershipΒΆ

Revisions
View document revision history.
Goal
User or organization takes over ‘ownership’ of a set of objects (write access for orphaned records), or the existing owner of an object would like to transfer ownership to another principal.
Summary
Ownership transfer needs to be supported so that all there is always someone that has the ability to manage the object. There are many circumstances w where such changes are required, and the DataONE infrastructure should support this operation both technically and operationally.
Actors
  • Current and new data owner
  • Data managers
Preconditions
  • Content exists in the DataONE system
  • Owner wants to transfer ownership role
  • Organization needs to take control of objects (owner no longer filling that role)
Triggers
  • Current owner no longer able to fill that role
Post Conditions
  • Object ownership has been changed
  • Updated to roles updated through the federation
../../_images/32_seq.png

Figure 1. Interactions for use case 32. User or organization takes over ‘ownership’ of a set of objectsn(write access for orphaned records).

Notes

  • Q. Is there an authority for any given data/metadata object? A. The authority for any object is expressed in the system metadata element SystemMetadata.rightsHolder.

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.