SUNScholar/Embargo Systems/3.X

Back to Embargo Systems

Introduction
''' There was a MAJOR change in the embargo functionality with the release of DSpace versions 3.2 when using the XMLUI. '''

There is a basic and an advanced policy method for setting embargoes.

Embargoes can be set during submission of an item or retroactively set after submission.

''Read carefully and prepare yourself during an upgrade.'

Also see: https://jira.duraspace.org/browse/DS-3218

Urgent Notice
The wording for the simple embargo form was confusing users, so the following were submitted to change the wording: With our repository we updated the messages.xml file with the changes incorporated for DSpace 4.0.
 * https://jira.duraspace.org/browse/DS-1709
 * https://jira.duraspace.org/browse/DS-1764

See example below: Access Settings Visible to a group of selected users (no selection needed for Anonymous) Item will be visible once accepted into archive Embargo Access until Specific Date Visible/Embargoed Name Description Reason Confirm Policy &amp; add another Groups Error format date When Embargo selected, date is required An identical policy for this group and this action is already in place. Policies List Private Item If selected, the item won't be searchable <message key="xmlui.Submission.submit.AccessStep.column0">Name <message key="xmlui.Submission.submit.AccessStep.column1">Action <message key="xmlui.Submission.submit.AccessStep.column2">Group <message key="xmlui.Submission.submit.AccessStep.column3">Start Date <message key="xmlui.Submission.submit.AccessStep.column4">End Date <message key="xmlui.Submission.submit.AccessStep.table_edit_button">Edit <message key="xmlui.Submission.submit.AccessStep.table_delete_button">Remove <message key="xmlui.administrative.authorization.AccessStep.label_date_help">Accepted format: yyyy, yyyy-mm, yyyy-mm-dd

Note for upgrade from 1.8.2 to 3.2
If you enabled embargoes in 1.8.2 then make sure to remove the embargo date option in your customsied input-forms.xml file.

See: http://wiki.lib.sun.ac.za/index.php/SUNScholar/Embargo_Systems/1.8.2#Modified_input_form_for_inputing_a_lift_date

Step 1 - Select simple or advanced embargo
The user has an opportunity to choose between, simple or advanced embargo settings.

To switch between the two, you need to set following variable in the dspace.cfg file.

xmlui.submission.restrictstep.enableAdvancedForm=false At Stellenbosch University with SUNScholar we have chosen to stay with the "simple" embargo method.

See example below: xmlui.submission.restrictstep.groups=Anonymous xmlui.submission.restrictstep.enableAdvancedForm=false
 * 1) Special Group for UI: all the groups nested inside this group
 * 2) will be loaded in the multiple select list of the RestrictStep

Step 2 - Enable Embargoes During Submission
To enable the new embargo changes are required to the item-submission.xml file, located in your config directory. This file determines which steps are executed in the submission of a new item.

Two new submission steps have been introduced in the file. By default, they are not activated yet:
 * AccessStep: the step in which the user can set the embargo at item level, effectively restricting access to the item metadata.
 * UploadWithEmbargoStep: the step in which the user can set the embargo at bitstream level. If this step is enabled, the old UploadStep must be disabled, leaving both steps enabled will result in a system failure.

To enable the new embargo, ensure that the new steps are uncommented, while the old UploadStep needs to be commented out.

Type the following to edit the submission file: nano $HOME/ source /dspace/config/item-submission.xml

See example below. submit.progressbar.access <processing-class>org.dspace.submit.step.AccessStep</processing-class> <xmlui-binding>org.dspace.app.xmlui.aspect.submission.submit.AccessStep</xmlui-binding> <workflow-editable>true</workflow-editable>

submit.progressbar.upload <processing-class>org.dspace.submit.step.UploadWithEmbargoStep</processing-class> <xmlui-binding>org.dspace.app.xmlui.aspect.submission.submit.UploadWithEmbargoStep</xmlui-binding> <workflow-editable>true</workflow-editable>

Step 3 - Rebuild webapps
Click on the heading above.