Page History

...

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.

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.  This is part of the normal process of upgrading from DSpace 1.8.x to 3.0.

 - dspace/etc/[postgres-oracle]/database_schema_18-3.sql

For PostgreSQL databases, the executed commands are:

ALTER TABLE resourcepolicy ADD rpname VARCHAR(30);
ALTER TABLE resourcepolicy ADD rptype VARCHAR(30);
ALTER TABLE resourcepolicy ADD rpdescription VARCHAR(100);
ALTER TABLE item ADD discoverable BOOLEAN;

update item set discoverable=true;

For Oracle databases, the executed commands are:

...

embargo will be set at item level or bitstream level a new ResourcePolicy will be added.

dspace.cfg

As already mentioned the user will be given the opportunity to choose between:

...

You are free to use existing metadata fields, or create new fields. If you choose the latter, you must understand that the embargo system does not create or configure these fields: i.e. you must follow all the standard documented procedures for actually creating them (i.e. adding them to the metadata registry, or to display templates, etc) - this does not happen automatically. Likewise, if you want the field for "terms" to appear in submission screens and workflows, you must follow the documented procedure for configurable submission (basically, this means adding the field to input-forms.xml). The flexibility of metadata configuration makes if it easy for you to restrict embargoes to specific collections, since configurable submission can be defined per collection.

...