Page Comparison

Overview

DRS2 supports rights metadata that specifies the terms and restrictions on stored content. Rights metadata is optional and should be applied to objects and files as needed.

Rights metadata can be applied by a depositor using Batch Builder or by a curator using Web Admin. This section describes how to add rights metadata to objects and files using the DRS2 Web Admin.

About rights metadata

Rights metadata can be found under the Rights tabfor objects and files.  Rights metadata is a set of fields collectively known as a rights segment.  More than one rights segment can be present if there is more than one rights basis, rights document or restriction that applies to the content.

...

• Download prohibited (audio files only).  Select this value and the audio content may be streamed or rendered, but it will not be provided to the user as savable content.
• Maximum image delivery dimension (JPEG200 image files only).  Select this value and you will be prompted to supply the maximum pixel size for the longest dimension.  The Image Delivery Service will restrict delivery of this image to the specified maximum dimensions.

Anchor
maximagesize maximagesize

How to limit still image delivery size

You can assign file-level rights metadata that will limit the maximum size of a JPEG2000-based delivery still image delivered by the Image Delivery Service (IDS).  By default, the maximum size IDS can deliver is 2400 pixels in the longest dimension.  For example, if a donor agreement or license restricts delivery size below this default, use file rights metadata to set a lower maximum size.

...

1. Display the file’s summary page and select the Rights tab (on the left).
2. Click + add rights block to create a new rights segment.
3. Select the rights basis (required).  This indicates the type of rights document (license, policy or statute) that is the basis for restricting delivery size.  Or select risk assessment if this restriction arises from the curator’s judgment.
4. Select the rights document (required if basis is license, policy or statute).  The pull-down list displays the object owner supplied name of eligible documents in your owner code. See Preparing rights documentation for information on eligibility requirements.
5. Enter the maximum image delivery dimension.  Add an integer that indicates the maximum pixel size of the image’s longest dimension. 
6. Click the Save changes button to commit this change.  If the Save button is not active (green), click once anywhere on the form to activate it.

Anchor
prohibitdownload prohibitdownload

How to prohibit download of audio or video files

You can assign file-level rights metadata that will prohibit download of an audio or video file.  This prohibition will allow streaming delivery of the audio or video but will prevent it from being provided as savable content.  For example, if you acquire digital audio accompanied by a license that prohibits download, use file rights metadata to enforce this requirement.

...

1. Display the file’s summary page and select the Rights tab (on the left).
2. Click + add rights block to create a new rights segment.
3. Select the rights basis (required).  This indicates the type of rights document (license, policy or statute) that is the basis for restricting delivery size.  Or select risk assessment if this restriction arises from the curator’s judgment.
4. Select the rights document (required if basis is license, policy or statute).  The pull-down list displays the object owner supplied name of eligible documents in your owner code. See Preparing rights documentation for information on eligibility requirements.
5. Check the Download Prohibited box. 
6. Click the Save changes button to commit this change.  If the Save button is not active (green), click once anywhere on the form to activate it.

How to indicate a delivery embargo

If access to content needs to be prohibited for a fixed period of time, you can specify the embargo delivery restriction.  This restriction is applied in object-level metadata. 

...

1. Display the object’s summary page and select the Rights tab (on the left).
2. Click + add rights block to create a new rights segment.
3. Select the rights basis (required).  This indicates the type of rights document (license, policy or statute) that is the basis for restricting delivery size.  Or select risk assessment if this restriction arises from the curator’s judgment.
4. Select the rights document (required if basis is license, policy or statute).  The pull-down list displays the object owner supplied name of eligible documents in your owner code. See Preparing rights documentation for information on eligibility requirements.
5. Select the embargo restriction.
6. Specify a Start date (yyyy-mm-dd) and either a Duration or End date (yyyy-mm-dd).  Click the Calculate embargo button and the system will fill in the third value. 
7. Click the Save changes button to commit this change.  If the Save button is not active (green), click once anywhere on the form to activate it.

Adding a review date or note

A review note or review date is optional metadata that indicates the need for further review of the content.  Review metadata is perceived as related to rights metadata, so it is located on the rights tab of an object or file.  You can search for objects or files by review date or keywords in review note, but in this release there is no automated functionality associated with either value. 

...

1. Display the object or file summary and select the Rights tab (on the left).
2. Click + add review date to create a new Needs Review segment.
3. Click into the review date field to open a calendar and select a date.  Or, press Escape to close the calendar and input the date manually (format must be MM/DD/YYYY).
4. Click into the review note field to add a free text note. 
5. Click the save changes button to commit this change.  If the Save button is not active (green), click once anywhere on the form to activate it.

Preparing rights documentation for deposit

When the rights basis value is license, statute, or Harvard policy, a pointer to rights documentation stored in DRS is required.  You can point to rights documentation deposited under your owner code or under the H.LIB.SHARED owner code that is accessible to all owners.

...