Metadata and Searching
Overview
The Rosetta Digital Asset Management System uses a few different types of metadata for its assets. Most of the descriptive metadata is Dublin Core, which is sourced from Aleph and ArchivesSpace. These source records must be crosswalked into Rosetta Dublin Core using code defined by the CJH Metadata Lab. This synchronization between systems means that CJH staff should rarely have to edit Dublin Core records in Rosetta, unless it is to change or add an Aleph/ArchivesSpace identifier.
Search Glossary
Rosetta lets users search on a huge list of possible metadata fields. Unfortunately this list cannot be edited, and the majority of fields on the list are not in use. Here is a list of fields that *are* commonly used and can be searched on.
Metadata Mapping
Many of the above fields are mapped from Aleph or ArchivesSpace records. Here are the mappings for each source record.
Aleph MARC to DC
The Aleph MARC to DC crosswalk utilizes MARC XML furnished by the Aleph REST API and transforms it into Dublin Core using an XSLT stylesheet
| Aleph MARC | Rosetta Dublin Core |
|---|---|
| 210, 245, 246 (all subfields) | Title |
| 100a, 110a | Creator |
| 260c, 264c | Date |
| 500a | Description |
| 520ab | Description |
| 545ab | Description |
| 555au | Relation |
| 700ae | Contributor |
| 710ae | Contributor |
| 773ao | Relation |
| 09x | Identifier |
| 001 | Identifier |
| 506a | Rights |
| 540a | Rights |
ArchivesSpace Metadata to Rosetta Dublin Core
The ArchivesSpace to Rosetta DC crosswalk utilizes the ArchivesSpace API and both Archival Object and Resource metadata to create the Rosetta Dublin Core record
| ArchivesSpace | Rosetta Dublin Core |
|---|---|
| Title (Archival Object) | Title |
| Title (Resource) | isPartOf |
| Call Number (Resource) | Identifier |
| Container Information (Archival Object) | Source |
| Language (Archival Object) | Language |