Subelements

The following subelements of name are used in the DAMS:

• namePart
• role

Subelement name/namePart

Guidelines for use

The name itself is always contained in a namePart subelement. Currently, the DAMS does not support breaking up names into parts (e.g. given and last name).

Name parts should appear in the same order as in their authorized form (the authority cited in the metadata). If no authority is used for personal names, last name or family name should appear first, followed by a comma, followed by first or given names.

Enter "no attribution" if no contributor is provided in the resource and if no contributor information can be supplied.

Attributes

Currently no attributes for namePart are implemented in the DAMS.

Subelements

No subelements for nameParts.

Subelement name/role

Guidelines for use

Attributes

No attributes for role.

Subelements

The following subelement of role is used in the DAMS:

• roleTerm

Subelement name/role/roleTerm

Guidelines for use

Enter role term from a local or recommended vocabulary:

• MARC Code List for Relators (marcrelator)
  Use the Relator term, not the Relator code (e.g. use "Forger" instead of "frg")
• Union List of Artist Names (ulan)
• local authority for role terms

Enter "not applicable" if no attribution.

Attributes

Subelements

No Subelements for roleTerm.

XML Examples

<name authority="naf" authorityURI="http://id.loc.gov/authorities/names" type="personal" displayLabel="Contributor name" usage="primary">
<namePart>Evans, Walker, 1903-1975</namePart>
<role> 
<roleTerm lang="eng" type="text" authority="marcrelator" authorityURI="http://id.loc.gov/vocabulary/relators">Photographer </roleTerm>
</role>
</name>

<name type="personal" usage="primary" displayLabel="Contributor name">
<namePart >Owens, Mark</namePart>
<role>
<roleTerm lang="eng" type="text" authority="marcrelator" authorityURI="http://id.loc.gov/vocabulary/relators">author</roleTerm> 
</role>
</name>

<name type="corporate" displayLabel="Contributor name">
<namePart>Texas Architects</namePart>
<role>
<roleTerm lang="eng" type="text" authority="ulan" authorityURI="http://vocab.getty.edu/ulan/">architectural firm</roleTerm> 
</role>
</name>

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

The following specific guidelines apply for the DAMS:

MARC 21

see http://www.loc.gov/standards/mods/mods-mapping.html#name. 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.