Mapping archival and bibliographic metadata schemas to Compass MODS - smith-special-collections/sc-documentation GitHub Wiki

This mapping was created in reference to the CLIR YWCA digitization grant (2016-2018). Though not comprehensive of the metadata that could be exported from ArchivesSpace for a component record or its parent resource record or exported from Aleph for a title's record, it is representative of the fields that are used by Smith College Special Collections in Compass for digital object records.

The working spreadsheet for these mappings exist here.

An example MODS XML record based on this mapping may be found here.

An example of the exported metadata from Aleph may be found here.

Archival metadata to Compass MODS

This mapping should be used to facilitate the transform of exported ArchivesSpace component record data to MODS XML for the purpose of ingesting metadata into Compass. Note: For the following fields, see rules for inheritance of description for digital objects:

  1. Agents
  2. Subjects
  3. Language of materials
  4. Physical description
  5. Scope and content
  6. Conditions governing access
  7. Conditions governing use
  8. Arrangement

The rules for inheritance outline the level(s) from which description is being pulled for digital object record.

ArchivesSpace PUI Label ArchivesSpace SUI Label ArchivesSpace Table.Field MODS Compass Fields Notes
Title Resource: Component: Basic Information: Title archival_object.title <titleInfo><title> Title
Date Resource: Component: Dates: Expression date.expression <originInfo><dateIssued> or <originInfo><dateCreated> Date issued or Date created If label = "Issued", use <dateIssued>. If label = "Creation", use <dateCreated>.
n/a Resource: Component: Dates: Start date.begin <originInfo><dateCreated encoding="iso8601" point="start"> or <originInfo><dateIssued encoding="iso8601" point="start"> n/a backend
n/a Resource: Component: Dates: End date.end <originInfo><dateCreated encoding="iso8601" point="end"> or <originInfo><dateIssued encoding="iso8601" point="end"> n/a backend
Extent Resource: Component: Extents: Number extent.number <physicalDescription><extent> Extent extent.number and extent.extent_type should be concatenated in single <physicalDescription><extent>, example: 10 linear feet.
Extent Resource: Component: Extents: Type extent.extent_type <physicalDescription><extent> Extent extent.number and extent.extent_type should be concatenated in single <physicalDescription><extent>, example: 10 linear feet.
Extent Resource: Component: Extents: Container summary extent.container_summary <physicalDescription><extent> Extent
Related names Resource: Component: Agent link: Role abstract_agent.linked_agent_roles <name><role><roleTerm authority="marcrelator"> (if role = creator or source) Field name designation Agents that have the role "subject" should be mapped to element <subject><name>. If role in ArchivesSpace is "creator", the MAR relator term is "creator". If role in ArchivesSpace is "source", the MARC relator term is "donor".
Related names Resource: Component: Agent link: Agents abstract_agent.title <name><namePart> Creator, Name, etc. See rules for description inheritance for digital object records.
Subjects Resource: Component: Subjects subject.title <subject><topic> (if term type = "Topical") or <subject><genre> (if term type = "Genre/Form") or <subject><geographic> (if term type = ""Geographic"") or <subject><name> (if agent role = "Subject") Topical subject or Genre or Geographic subject or Name subject See rules for description inheritance for digital object records.
Language of materials Resource: Component: Notes: Language of materials: Content note_singlepart.content type="langmaterial" <language><languageTerm> Language See rules for description inheritance for digital object records.
Physical description Resource: Component: Notes: Physical description: Content note_singlepart.content type="physdesc" <physicalDescription><note type="physical description" displayLabel="Physical Description"> Physical description note See rules for description inheritance for digital object records.
Arrangement Resource: Component: Notes: Arrangement: Content note_text.content type="arrangement" <abstract> Description See rules for description inheritance for digital object records.
Conditions governing access Resource: Notes: Conditions governing access: Content or Resource: Component: Notes: Conditions governing access: Content note_text.content type="accessrestrict" <accessCondition type="use and reproduction" displayLabel="Collection Use and Reproduction"> (if from the resource) or <accessCondition type="use and reproduction" displayLabel="Object Use and Reproduction"> (if from the component) Collection use and reproduction (if from resource) or Object use and reproduction (if from component) See rules for description inheritance for digital object records.
Conditions governing use Resource: Notes: Conditions governing use: Content or Resource: Component: Notes: Conditions governing use: Content note_text.content type="userestrict" <accessCondition type="restriction on access" displayLabel="Collection Access"> (if from the resource) or <accessCondition type="restriction on access" displayLabel="Object Access"> (if from the component) Collection access (if from the resource) or Object access (if from the component) See rules for description inheritance for digital object records.
n/a Resource: Component: Notes: Scope and content: Content note_text.content <abstract> Description See rules for description inheritance for digital object records.
Physical storage information Resource: Component: Instances: Top container top_container.type <location><shelfLocator> Physical storage information [top_container.type top_container.indicator] and [sub_container.type_2 sub_container.indicator_2] should be concatenated with a comma and space in single <location><shelfLocator> : example, Box 1, folder 2.
Physical storage information Resource: Component: Instances: Top container top_container.indicator <location><shelfLocator> Physical storage information [top_container.type top_container.indicator] and [sub_container.type_2 sub_container.indicator_2] should be concatenated with a comma and space in single <location><shelfLocator> : example, Box 1, folder 2.
Physical storage information Resource: Component: Instances: Child type sub_container.type_2 <location><shelfLocator> Physical storage information sub_container.type_2 and sub_container.indicator_2 should be concatenated with a space in single <location><shelfLocator>. [top_container.type top_container.indicator] and [sub_container.type_2 sub_container.indicator_2] should be concatenated with a comma and space in single <location><shelfLocator> : example, Box 1, folder 2.
Physical storage information Resource: Component: Instances: Child indicator sub_container.indicator_2 <location><shelfLocator> Physical storage information sub_container.type_2 and sub_container.indicator_2 should be concatenated with a space in single <location><shelfLocator>. [top_container.type top_container.indicator] and [sub_container.type_2 sub_container.indicator_2] should be concatenated with a comma and space in single <location><shelfLocator> : example, Box 1, folder 2.
Digital materials: Identifier Resource: Component: Instances: Digital object: Identifier digital_object.component_id <identifier type="local"> Identifier Use for digital object identifier.
digital_object.uri <identifier type="asdouri"> Identifier Use for ArchivesSpace digital object API URI.
archival_object.uri <identifier type="asaouri"> Identifier Use for ArchivesSpace archival object API URI.
n/a Resource: Ref ID resource.ref <identifier type="asrefid"> Identifier Use for ArchivesSpace archival object ref ID.
n/a Resource: Component: Instances: Digital object: Notes: Conditions governing use: Persistent ID note_digital_object.persistent_id <accessCondition type="copyright" displayLabel="Copyright Statement" xlink:href="**value**"> Copyright statement Use for DPLA rights statement URI.
Digital materials: Conditions governing use Resource: Component: Instances: Digital object: Notes: Conditions governing use: Content note_digital_object.content <accessCondition type="copyright" displayLabel="Copyright Statement" xlink:href="value"> Copyright statement Use for DPLA rights statement.
n/a Resource: Basic Information: Title abstract_archival_object.title <relatedItem type="host" displayLabel="Collection"> Collection
n/a Resource: Finding Aid Data: EAD location resource.ead_location <relatedItem type="host" displayLabel="Collection"><identifier type="uri" displayLabel="Finding aid"> Finding aid Asteria finding aid url
n/a Repository: Parent institution repository.parent_institution_name <location><physicalLocation> Repository
n/a Repository: Repository name repository.name <name role="unit" authority="marcrelator"><namePart> Unit

Bibliographic metadata to Compass MODS

This mapping should be used to facilitate the transform of exported MARC records from Aleph to MODS XML for the purpose of ingesting metadata into Compass.

Aleph Label MARC Field MODS Compass Fields Notes
Title Title: 245 <titleInfo><title> Title
Title Sub-title: 245 ǂb <titleInfo><subtitle> Subtitle
Variant title Alternative title: 246 <titleInfo type="alternative"><title> ???
Publisher Place of publication: 260 ǂa <originInfo><place><placeTerm type="text"> Place of publication
Publisher Publisher: 260 ǂb <originInfo><publisher> Publisher
Publisher Date of publication: 260 ǂc <originInfo><dateIssued> Date issued
Extent 300 ǂa <physicalDescription><extent> Extent
Summary note 520 ǂa <abstract> Description
Subjects Topical subject added entry: 650; geographic subject added entry: 651; genre subject added entry 655 <subject> Topical subject or Genre or Geographic subject or Name subject
Other author(s) 700 (person name added entry), 710 (corporate name added entry) <name><namePart> Creator, name, etc.
⚠️ **GitHub.com Fallback** ⚠️