In ArchivesSpace, the Digital Object data model is used to record information about digitized or born-digital archival resources. The University of Denver uses the Digital Object data model for two purposes:
Digital Objects are linked to the record for the Archival Object for which they are surrogate. Digital Objects are a sub-class of the Instance class in the ArchivesSpace data model; the corresponding sub-class for physical materials is the Top Container.
When a Digital Object is linked to, and made representative of, an Archival Object in ArchivesSpace, it is possible for the MODS Export function for that Archival Object to access the Digital Object metadata and populate the <digitalOrigin> and <part> elements of the MODS record with it. More information on this may be found in the workflow instructions below.
The University of Denver maintains the ao_mods plugin for exporting MODS records from an Archival Object record, and the digitizer plugin for facilitating the creation and linking of Digital Objects from an item record.
Required fields will appear in bold.
| Title | |
| Description | The name of the resource being described. |
| Local Rules | Auto-populated from the linked Archival Object |
| Examples | |
| ArchivesSpace Key | digital_object.title |
| Digital Object ID | |
| Description | The unique identifier for the resource being described. |
| Local Rules | When ingested to Digital Collections DU, the handle of the digital object; when not yet ingested, the path to the object on the shared drive or SFTP server |
| Examples | |
| ArchivesSpace Key | digital_object.digital_object_id |
| Publish | |
| Description | Switch for publishing the record in the public user interface |
| Local Rules | Ensure this box is checked if you wish for the record to appear in the public user interface |
| Examples | |
| ArchivesSpace Key | digital_object.publish |
| File Versions | |
| Description | Files constituting the resource |
| Local Rules | Each Digital Object must contain at least one file. This is to ensure we have a complete inventory of files that have been digitized. If a Digital Object is compound (i.e. contains more than one file), use one File Version for each constituent file in the compound object. The MODS Export plugin looks for Digital Objects with more than one File Version and exports one <part> element for each. Digital Collections DU uses this metadata to determine when to use Compound Object viewers. |
| Examples | |
| ArchivesSpace Key | digital_object.file_versions |
| File Versions: File URI | |
| Description | The name provided to the constituent file. |
| Local Rules | Enter the file name as-is (no repository, SFTP, or shared drive paths). |
| Examples | |
| ArchivesSpace Key | file_version.file_uri |
| File Versions: File Format Name | |
| Description | The MIME type of the constituent file. |
| Local Rules | Select from the drop-down list. |
| Examples | |
| ArchivesSpace Key | file_version.file_format_name |
| File Versions: Caption | |
| Description | A description of the file itself, used to indicate the view depicted or its order in a sequence. |
| Local Rules | Required if the Digital Object has more than one file; otherwise optional. |
| Examples | |
| ArchivesSpace Key | file_version.caption |
| User Defined: MODS Digital Origin | |
| Description | The means by which the object came to be in its represented digital form. |
| Local Rules | Select from the drop-down list. Values are from the Library of Congress MODS specifications. |
| Examples | |
| ArchivesSpace Key | user_defined.enum_2 |