DRS Opaque Storage

This page describes options for using opaque storage in the DRS. Opaque storage is designed for content not eligible for or not ready for full DRS services that would nevertheless benefit from secure storage.

Why use opaque storage?
Depositing opaque content in the DRS provides an option for secure, safe storage for digital content in file formats that are not fully supported* by DRS or that can't be adequately processed (appraised, cataloged, etc.) in advance.

* "Fully supported" means that the content is in formats that are both well understood by DRS staff and supported by DRS tools and delivery services.

What are DRS preservation options for content in opaque storage?
Using DRS opaque storage, some minimal preservation services will be available for content that otherwise would not receive any preservation services, including:

Secure redundant storage
File integrity monitoring
Technical characterization of files

What types of content can use opaque storage?
Content can consist of files in any format. A collection of opaque files can represent an intellectual or physical organization. For instance, it could represent a single intellectual work (e.g. a video game), relate to an individual (e.g. all donated works from a faculty member) or be associated with a particular medium (e.g. selected content from a hard drive).

How can content in opaque storage be accessed?
Content in DRS opaque storage can be deliverable by the DRS File Delivery Service (when the DRS access flag is set to R - Restricted to Harvard or P - Public delivery). It is also accessible to authorized users via the DRS Web Admin administrative interface.

Comparison of opaque deposit options
DRS offers two opaque storage options: opaque container and opaque object. The table below shows how these options differ.

	Opaque Container	Opaque Object
Availability:	Available	Available
Storage:	Content is stored in a compressed zip file	Content is stored as individual files
Access:	Authorized users can download an entire zip file in DRS Web Admin (but not individual content files stored within the zip file). Opaque containers can be made publicly deliverable via the DRS File Delivery Service. Delivery restrictions are subject to DRS Access flags set for each file.	Authorized users can download one or more individual files in DRS Web Admin. All files in the Opaque objects automatically get an FDS (FIle Delivery Service) delivery URN on deposit. Delivery restrictions are subject to DRS Access flags set for each file.
Size:	Tested with up to 50 GB per zip container	Tested with up to 50 GB per file
Cost:	DRS storage fees apply	DRS storage fees apply

For more information:

Information about creating opaque containers and opaque objects for the new DRS using Batch Builder.
DRS Content Model Reference
Contact LTS for more information if you are starting a new DRS deposit project with opaque content: http://nrs.harvard.edu/urn-3:hul.ois:drshelp