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.

Searching in Rosetta

Searching in Rosetta happens the three levels of the Rosetta data model: IE, Representation, File.

TIP
To include both FILE and IE information in a search, search on the FILE level and customize your search Columns in the Columns tab to include IE level information

Here is how that data model breaks down for an example IE.

• The IE level is the overarching object: The "Photographs"
• The REP level is representations of Intellectual Entities: The Modified Master viewable to patrons, the Preservation Master viewable to staff
• The FILE level is files that make up Intellectual Entities: 3124174_la-ar25060-b01-f07.pdf

You can search on any field for any of these levels, but Rosetta will ONLY bring up the level on which you are searching.

Rosetta lets users search on a huge list of possible metadata fields. Many of those fields are technical metadata fields which we do not include in our descriptive metadata for indexing. Unfortunately this master list of search fields cannot be edited, and the majority of fields on the list are not in use. The Search Glossary below includes fields that *are* commonly used and can be searched on. You can find these fields by typing any or all of the field name in the field search bar.

Search Glossary

Access Rights Policy ID (IE)

• Search for IEs based on their Access Policy ID code. Options provided.

Collections

• Search for IEs based on their Collection in the Collection Management module. These collections were created programmatically from MARC records and will need significant data cleanup in the future. Options provided.

Contributor - Deposit Agent (DC)

• The username of the staff member who prepared the object for ingest. Free text.

Deposit ID

• Deposit ID for an ingest activity. Free text.

FILE - Identifier - DTLPID (DC)

• DigiTool PID associated with a FILE. Free text.

File Extension

• Extension of a file.

File Label

• Label for a file in the IE's Struct Map (left-hand side of the IE viewer). Free text.

File Original Name

• The filename of a FILE. Free text.

File PID

• The Rosetta FILE PID. Free text.

File Size Bytes

• The size of a FILE. Free text.

IE Creation Date

• The date the IE was created in Rosetta. Choose date from calendar.

IE Modification Date

• The date the IE was last modified in Rosetta. Choose date from calendar.

IE PID

• The Intellectual Entity (IE) PID. Free text.

Identifier (DC)

• The Dublin Core identifier associated with an IE. Often used for the Aleph identifier. Free text.

Identifier - Archivesspace (DC)

• A qualified Dublin Core Identifier for the ArchivesSpace Archival Object Ref ID associated with an IE. Free text.

Identifier - DTLPID (DC)

• A qualified Dublin Core Identifier for the DigiTool PID associated with a FILE. Free text.

Is Part Of (DCTERMS)

• A DCTERMS field often used by the ArchivesSpace crosswalk to show the IE's relationship with an ArchivesSpace Resource. Free text.

Partner Name

• The partner to whom the IE belongs. Options provided.

Preservation Type

• The preservation type of a REP associated with an IE. Options provided.

Relation (DC)

• A Dublin Core field often used by Aleph MARC crosswalk for Finding Aid or Collection information. Free text.

Source (DC)

• A Dublin Core field often used by the ArchivesSpace crosswalk to store Box/Folder/Item numbers. Free text.

Title (DC)

• A Dublin Core field for storing the title of an IE. Free text.

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
Ref ID (Archival Object)	Identifier - Archivesspace