Effects of installation

This patch adds three tables to the DSpace database: embargoitem, embargoprofiletype, and embargoselectprofile.

Change embargo lengths

Change the table "embargoselectprofile" in the database. Out of the box, the table looks like this:

 profile_id | profile_type | name | values_in_months 
------------+--------------+------+------------------
          1 |            1 | JHU  | 6|12|24|120|180

You may add profiles as you see fit. Give each a unique and descriptive name so that collection creators choose the appropriate one. Change the pipe-delimited string in the values_in_months column to provide different embargo lengths.

Change item-submission.xml

Add strings to messages.xml

The following keys need to be added to messages.xml (for English) or translated:

<message key="xmlui.administrative.collection.general.options_embargoes">Embargo settings</message>

<message key="xmlui.administrative.collection.EditCollectionEmbargo.title">Embargo settings</message>

<message key="xmlui.administrative.collection.EditCollectionEmbargoForm.main_head">Embargo settings</message>

<message key="xmlui.administrative.collection.EditCollectionEmbargo.trail">Embargo settings</message>

<message key="xmlui.administrative.collection.EditCollectionEmbargoForm.label_enable">Enable embargoes</message>

<message key="xmlui.administrative.collection.EditCollectionEmbargoForm.label_discovery">Allow discovery of embargoed items</message>

<message key="xmlui.administrative.collection.EditCollectionEmbargoForm.label_bypass">Select the groups able to bypass embargo</message>

<message key="xmlui.administrative.collection.EditCollectionEmbargoForm.label_durations">Select allowable durations</message>

<message key="xmlui.administrative.collection.EditCollectionEmbargoForm.help_enable">When checked, submitters to this collection will be prompted to place an embargo on their submission.</message>

<message key="xmlui.administrative.collection.EditCollectionEmbargoForm.help_discovery">When checked, allows metadata for embargoed items to be publicly visible in browse and search results, RSS feeds, and OAI-PMH harvesting. Users who discover embargoed items can then contact the original submitter to obtain a copy. If left unchecked, embargoed items will be invisible except to those allowed to bypass the embargo (see below).</message>

<message key="xmlui.administrative.collection.EditCollectionEmbargoForm.help_bypass">By default, the collection administrator and original submitter can view embargoed items. If other users or groups should be able to view the items, use this button to add a new policy with action BYPASS_EMBARGO to the collection.</message>

<message key="xmlui.administrative.collection.EditCollectionEmbargoForm.help_durations">Duration refers to the embargo lengths users may choose among.</message>

<message key="xmlui.administrative.collection.EditCollectionEmbargo.submit_save">Save Embargo Settings</message>

<message key="xmlui.administrative.collection.EditCollectionEmbargo.submit_cancel">Cancel</message>