Versions Compared

Old Version 3

changes.mady.by.user Alan Orth

Saved on

compared with

New Version 4

changes.mady.by.user Tim Donohue

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Quality control
  • Improvements to the bibliographic record (metadata available in workflow can be different than those asked of the submitter)
  • Check of policy / copyright

 

Withdrawn item

It is a logical deletionthe removal of an Item from the archive. However, a withdrawn item is still available to Administrative users. The Item can be restored and it can be used to keep track of what has been available for a while on the public site.

...

  • 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 )


Private item

Note

Despite its name, a "private" item is not necessarily access restricted. It's simply hidden from all search/browse/OAI results, and is therefore only accessible via direct link (or bookmark). If you wish to access restrict the item so that it is no longer available to a certain group of users (or only available to Admins), you should edit the Item's Authorization Policies (via the Edit Item screens).

This state should only refer to the discoverable nature of the item. A private item will not be included in any system that aims to help users to find items. So it will not appear in:

...

An item that is in a stable state, available in the repository under the defined access control list (ACL) rule. Changes to these items are possible only for a restricted group of users (administrators) and should produce versioning according to the Institution's policy.


Embargoed Item (as in DSpace 3.0+):

Are a special case of Archived/Published Item. The item has some time based access policy attached to it and/or the underlying bitstreams. Specifically, read permission for someone (EPerson Group) starting from a defined date. Typically embargo is applied to the bitstreams so that "fulltext" has initially very limited access (normally administrators or other "repository staff" groups) and only after a defined date will the fulltext become visible to all users (Anonymous group). This scenario is used to implement typical "embargo requirements" from publishers -- see Delayed Open Access.

...