Use Case 23 - Owner Expunge ContentΒΆ

Revisions
View document revision history.
Goal
User can find out where all copies of my data are in the system and can expunge them.
Summary

In some cases it may be desirable for a data owner to remove all their content from the system, however this use case conflicts with the general premise of DataONE to preserve information. A useful compromise may be to expunge content that has no known references to it.

There may be situations where content removal may be necessary for system or community integrity - for example if content uploaded to the system is determined to contain dangerous content such as viruses, the data owner is discovered to have committed fraud, or the content may be protected and must be removed for legal reasons.

In any case, it would seem that a data manager or curator should be involved in such decisions.

Actors
  • Data owner
  • Data curator
  • Member Nodes
  • Coordinating Nodes
  • Notification system (referrers should be notified of removal)
Preconditions
  • Content exists in the system that must be removed
  • A decision has been made to remove all / some content
Triggers
  • All triggers for this should be through administrative / curatorial procedures.
Post Conditions
  • The targeted content is no longer present in the DataONE system
  • Subscribers are be notified of the change
../../_images/23_seq.png

Figure 1. Interactions for use case 23, User can find out where all copies of my data are in the system andncan expunge them

Notes

  • Dealing with inappropriate usage of (ie, copyrighted objects that are stored)

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.