Page History
...
DSpace 3.0 XMLUI Embargo Functionality
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.
As a DSpace administrator, you can choose to integrate either Simple or Advanced dialog screens as part of the item submission process. These are outlined in detail in the sections Simple Embargo Settings and Advanced Embargo Settings.
...
- 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 added.
Note: the new embargo is not supported on JSPUIthe new Embargo functionality in DSpace 3.0.
This 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.
...
Pre-DSpace 3.0 Embargo Compatibility
Current Embargo solution have 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
...