...
An item that is in a “stable” state available on the repository under the defined ACL rule. Changes to these items are possible only for a restricted group of users (administrators) and should produce versioning according to the Institution policy.
Embargoed Item (as in DSpace 3.0+):
Are a special case of Archived/Published Item. The item has some time based ACL attached to it and/or the underlying bitstreams. Specifically read permission for someone (EPerson Group) starting from a defined date. Typically embargo apply to the bitstreams so that "fulltext" has initially very limited access (normally administrators or other "repository staff" groups) and only after a defined date the fulltext become visible to all users (Anonymous group). This scenario is used to implement typical "embargo requirements" from publishers see http://en.wikipedia.org/wiki/Delayed_open_access
If the metadata of the item should be visible only to 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 full rights aware, this mean that in different UIs or with different configurations (legacy lucene search or DBMS browse) some metadata of 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 limitation:
- no one, not ever authorized users, are able to find the item browsing or searching the repository
- you need to manage externally a schedule that alert you when the embargo is expired so to re-enable the discoverable nature of the item