Page History

...

• 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 deletion. The Item can be restored and it can be used to keep track of what has been available for a while on the public sitethe removal of an Item from the archive. However, a withdrawn item is still available to Administrative users (and may optionally be restored to the archive at a later date). A withdrawn item disappears from DSpace (except from Administrative screens) and the item appears to be deleted.

Expected use cases:

• 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

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:

...

It should be accessible under the actual ACL rules Authorization Policies of DSpace using direct URL or query method such as:

...

An item that is in a stable state, available in the repository under the defined ACL ruleAuthorization Policies. 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.

If the metadata of the item should be visible only to a specific group of users, it is possible to define an embargo policy also for the ITEM itself.  A READ policy for a specific group will mean that only the users in that group will be able to access the item splash page. Note that currently only some UIs (JSPUI/XMLUI) and in a very specific configuration (discovery enabled as search provider, and the SOLRBrowseDAOs is used for the Browse system) are fully rights awareare fully rights aware (see Discovery documentation for more information, especially the section on "Access Rights Awareness").  This means that in different UIs or with different configurations (legacy lucene search or DBMS browse)  , some metadata of a restricted item could be exposed to unauthorized users. When you need to work with UIs not fully rights aware, a workaround can be to use the "Private Item" flag to make the item undiscoverable so that metadata will be not exposed to unauthorized users. Please note that this workaround has several major limitations:

...