Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: clarification for WITHDRAWN_READ

...

  • Staging area for item to be removed when copyright issues arise with publisher. If the copyright issue is confirmed, the item will be permanently deleted or kept in the withdrawn state for future reference.
  • Logical deletion delegated to community/collection admin, where permanent deletion is reserved to system administrators
  • Logical deletion, where permanent deletion is not an option for an organization
  • Removal of an old version of an item, forcing redirect to a new up-to-date version of the item (this use case is not currently implemented out-of-box in DSpace, see )

By design, withdrawing an item is reversible. As an administrator, you can reverse the withdrawing of an item, through the action "reinstate". As a mechanism to support this, a resource policy state "WITHDRAWN_READ" was introduced.

When as item is withdrawn, all READ policies associated with the item and its underlying bundles and bitstreams, are changed into WITHDRAWN_READ policies. This achieves 2 things:

  1. The READ policy information in itself is still preserved, and can get switched back to normal READ policies if the item gets reinstated.
  2. As long as the item is withdrawn, those WITHDRAWN_READ policies should not give any users or groups read rights. 

WITHDRAWN_READ was introduced in DS-3097 after it was observed that even though an item was withdrawn, the related bitstreams were still accessible. 


Non-Discoverable item (also known as Private item)

...