Page History
...
Warning | ||
---|---|---|
| ||
By enabling the DSpace 3.0 Embargo functionality you will break JSPUI submission functionality. JSPUI is not yet compatible with the new XMLUI Embargo. If you use JSPUI, please see the Pre-DSpace 3.0 Embargo section. |
Embargoes can be applied per item and per bitstream. The item level embargo will be the default for every bitstream, although it could be customized at bitstream level.
...
- Edit Item
- Edit Bitstream
- Wildcard Policy Admin Tool
Configuring and using
...
Embargoes in DSpace 3.0
Warning | ||
---|---|---|
| ||
By enabling the DSpace 3.0 Embargo functionality you will break JSPUI submission functionality. JSPUI is not yet compatible with the new XMLUI Embargo. If you use JSPUI, please see the Pre-DSpace 3.0 Embargo section. |
Introduction
The following sections describe the steps needed to configure and use the new Embargo functionality in DSpace 3.0.
Note: when the embargo will be set at item level or bitstream level a new ResourcePolicy will be addedThis embargo functionality is implemented using DSpace's system for ResourcePolicies.
Database
As a first step, the following script needs to be executed to ensure that your DSpace database gets extended with 3 new fields, required by the new embargo.
...
The Pre-DSpace 3.0 embargo functionality (see below) has been modified to adjust the policies setter and lifter. These classes now also set the dates within the policy objects themselves in addition to setting the date in the item metadata.
Anchor | ||||
---|---|---|---|---|
|
Embargo model and life-cycle
...