Technical topics


Does the SDR require specific file formats?
No, specific file formats are not required for deposit in the SDR. However, SDR staff can advise on "archival-quality" file formats and data encoding specifications that are conducive to information preservation as well as other digital preservation best practices.

Does the SDR support hierarchically structured datasets?
Currently the best way to maintain hierarchical structure of datasets in the SDR is to wrap up the directory structure in a Zip container file for deposit. The Zip file will be presented on the PURL page for download by users.

Does SDR offer system emulation or file format migration services?
The SDR system protects digital content from loss and corruption by preserving bits in a highly-secure system where redundant copies are stored across storage systems in geodiverse locations. The SDR does not currently offer formal services in format migration or system emulation, but we believe that both format migration and system emulation will play a role in enabling future access to today’s digital content. The SDR staff have digital preservation expertise and can advise and consult now on these and other methodologies for accessing deposited content into the future.

Does the SDR have an API?
A digital object with the appropriate visibility settings can be programmatically accessed via RESTful calls to its PURL (persistent URL) in the SDR. The SDR does not yet have an exposed API for deposit; we are interested in working with the campus community to identify opportunities in this space. 

Does the SDR support ORCIDs?
We are currently designing support for researcher ORCiD IDs in the repository. The Libraries have published several guides about ORCiD at Stanford.

Does SDR support (including indexing, searching, publishing, etc.) structured metadata or domain specific ontologies or taxonomies?
The SDR supports descriptive metadata in MODS and DC (Dublin Core) for discovery. Depositors can deposit other forms of structured metadata in the SDR as opaque file(s) for preservation and for sharing the metadata for re-use in other environments.