DRS Opaque Storage
This page describes current and future 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?
Opaque storage in the DRS may be an option if your digital content is in file formats that are not fully supported by DRS (fully supported means content in formats well understood by DRS staff and supported by DRS tools and delivery services) or can't be adequately processed (appraised, cataloged, etc.) in advance of DRS deposit. Opaque storage is designed for temporary, safe storage of content until the format is fully supported and/or until a collection is ready to be fully processed.
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. There are no intellectual restrictions on what an opaque collection of files can represent. 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 is not deliverable by public delivery services. However, it is 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 in DRS 1 and DRS 2. | Available in DRS 2 only. |
| Cost: | Content is stored in a compressed zip file. This requires less storage space resulting in lower storage fees. (Regular DRS storage fees apply.) | Content is stored as individual files which tends to result in higher storage fees. (Regular DRS storage fees apply.) |
| Size: | Up to 4 GB. | Up to 50 GB (the limit for all DRS files and objects). |
| Technical and administrative metadata support: | Metadata at container level. | More granular metadata - At the object level and individual file level. |
For more information:
Information about creating opaque containers using Batch Builder:
http://hul.harvard.edu/ois/systems/drs/bb-userguide/bb-userguide.pdf
Information about opaque objects (DRS 2 Content Model reference):
http://hul.harvard.edu/ois/systems/drs/docs/drs2-contentmodels.pdf
Contact LTS for more information:
http://nrs.harvard.edu/urn-3:hul.ois:digprojhelp