Subelements

For information about a Digital Source Collection, the following subelements of <relatedItem> are used in the DAMS:

• titleInfolocation
• identifier

Subelement <relatedItem><titleInfo>

Guidelines for use

<titleInfo> is a container element that contains subelements related to title information.

Attributes

Subelements

For information about a Digital Source Collection, the following subelement of <titleInfo> is used in the DAMS:

• title

Subelement <relatedItem><titleInfo><title>

Guidelines for use

Enter Input the name of external a physical or digital collection in from which the asset belongsoriginated.

Attributes

No attributes for <title> are currently implemented in the DAMS.

Subelements

No subelements for <title> are currently implemented in the DAMS.

Subelement

<relatedItem><identifier>

Guidelines for use

<location> is a container element; specific data is recorded in the subelements.

Attributes

No attributes for <location> are currently implemented in the DAMS.

Subelements

For information about a Digital Collection, the following subelement of <location> is used in the DAMS:

• url

Subelement <relatedItem><location><url>

Guidelines for use

<url> is for an electronic location from which the resource is available. Enter the URL of an external digital collection in which the asset belongsEnter identifiers for a physical or digital collection from which the asset originated.

Attributes

Subelements

No subelements for <url>.

Subelement <relatedItem><identifier>

Guidelines for use

Enter URI of external digital collection in which the asset belongs.

Attributes

Subelements

No subelements for <identifier>.

XML Examples

<relatedItem displayLabel="DigitalSource collection" type="source" usage="hostprimary">
	<titleInfo lang="eng" displayLabel="Source collection name">
		<title>The Rita M. Cacas Filipino American Community Archives collection, Special Collections, University of Maryland Libraries</title>
	</titleInfo>
	<identifier type="URIlocal" displayLabel="DigitalSource collection URI>urn:oasis:names:specification:docbook:dtd:xml:4.1.2<local identifier">0371-MDHC</identifier>
	<location>
		<url<identifier type="uri" displayLabel="DigitalSource collection URLURI">http>https://omekaarchives.lib.utexasumd.edu/repositories/2/greatcollection</url>
	</location>resources/1423</identifier>
	<titleInfo<identifier langtype="engpid" displayLabel="DigitalSource collection persistent name">
		<title> Architecture Video Collection </title>
	</titleInfo>identifier">http://hdl.handle.net/1903.1/42646</identifier>
</relatedItem>

Mappings

Dublin Core

Depending on the direction of mapping necessary, check

• DC to MODS: https://www.loc.gov/standards/mods/dcsimple-mods.html
• MODS to DC: http://www.loc.gov/standards/mods/mods-dcsimple.html

MARC 21

See http://www.loc.gov/standards/mods/mods-mapping.html. The following specific guidelines apply for the DAMS:

Solr

In general, all MODS metadata is imported into the DAMS Solr server upon ingest. The ingest process generates Solr fields typically named according to the following schema:

mods_value*_suffix

where

• value* can be one or multiple element, subelement or attribute names that allow to distinguish Solr fields
• suffix is s, t, ss, ms or mt, which refers to the type of data stored in a Solr field and how it is indexed. The Solr index usually contains multiple copies of each field with the same content, distinguished by their suffix.

The following table shows mappings between MODS elements and Solr fields for those fields that are currently used for display in the Collections portal, or where additional processing happens in Islandora or during the publishing process. Suffixes are ignored, unless relevant for the mapping.