***Work in progress. Contact the DAMS Management Team with Questions

Next-Level Collections

MODS Element:   [name of element]

...

Form field(s)

Provides form field label(s) and input guidelines.

...

Repeatable

...

Indicates whether the element is repeatable.

...

Form Required?

...

Indicates if the element is required or recommended by the form.

...

Subelement/Attribute Name

...

Details

...

XPath Syntax

...

Subelement or Attribute Name

...

Describes how each subelement/attribute will be used in the DAMS.

...

Provides an example of the resulting XML datastream from the MODS, MADS, or DAMS Custom datastream.

...

<titleInfo> container element that contains all subelements related to title information

lang attribute (values: eng as default; otherwise, any ISO-639-2 language codes)

usage attribute (usage="primary" is automatically applied for display and/or citation purposes)

...

...

map <titleInfo> and all subelements to <dc:title>

...

MARC 21 fields 130, 240, 245, 246, 247, 730, 740

<titleInfo type><title> = MARC 21 field 245

<titleInfo type><translated> = MARC 21 field 246

<titleInfo type><alternative> = MARC 21 field 246

<titleInfo type><uniform> = MARC 21 fields 130, 240, 730

MARC 21 field 247 is used for former title for Serials

MARC 21 field 740 is used for uncontrolled related titles

...

<titleInfo> will have default lang="eng" unless otherwise specified. Refer form users to to ISO-639-2 language codes.

Titles should be as concise as possible.

Refer to content standards like CCO, RDA, DCRMs, etc.

Follow your unit/collection guidelines per Supervisor/Collection Owner

...

Title

• Language (if not English) (text field with prompt to enter ISO-639-2 language code)

...

Description 

...

<abstract> 

lang attribute (values: eng as required default; otherwise, any ISO-639-2 language codes)

displayLabel attribute value "Description" when lang attribute value is "eng"

...

none

...

map <abstract> to dc:description

...

<abstract> will have default lang="eng" unless otherwise specified. Refer form users to to ISO-639-2 language codes.

not enforced in form; Follow your unit/collection guidelines per Supervisor/Collection Owner.

Best practice suggestions are to include collection title, summary of included content, and the date or date span of the contents' original creation if known.

No raw OCR output.

No full-text transcription of a textual or linguistic resource.

...

Description

...

Contributor

...

<name> container element that contains all subelements related to name information.

type attribute (values: personal, corporate, conference, family)

authority attribute (values: naf, viaf, local )

authorityURI attribute (values: http://id.loc.gov/authorities/names, http://viaf.org/, local URI if available)

displayLabel attribute (value: Contributor name )

usage attribute (when multiple names are stored, apply usage="primary" to one for display and/or citation purposes)

...

<namePart>

<role><roleTerm>
lang attribute
type attribute (value: text)
authority attribute (values: local, marcrelator, ulan)
authorityURI attribute (values: local URI if available, http://id.loc.gov/vocabulary/relators, or http://vocab.getty.edu/ulan/)

...

<name authority="naf" authorityURI="http://id.loc.gov/authorities/names" type="personal" displayLabel="Contributor name">
<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>

...

map <name><namePart><role><roleTerm type="text">creator or author to dc:creator.

map <name usage="primary"><namePart><role><roleTerm type="text">author to dc:creator.

map <name><namePart><role><roleTerm type="text">[anything other than creator or author or publisher] to dc:contributor.

map <name><namePart><role><roleTerm type="text">publisher to dc:publisher.

...

<name> = MARC 21 fields 1XX and 7XX

When used with <name type="personal">, <namePart> = MARC 21 fields 100, 700

When used with <name type="family">, <namePart> = MARC 21 fields 100, 700

When used with <name type="corporate">, <namePart> = MARC 21 fields 110, 710

When used with <name type="conference">, <namePart> = MARC 21 fields 111, 711

<name><namePart type="termsOfAddress"> ≈ MARC 100 and 700 subfields b and c

<name><displayForm> ≈ MARC 21 field 245 subfield c (This subfield may include other information in addition to the display form of the name.)

<name><role> = MARC relator code 1XX and 7XX subfield 4; or its textual form 100, 110, 700, 710 subfield e, and 111 and 711 subfield j

...

Recommended, optional in form. Name Authority File (NAF), Virtual International Authority File (VIAF), or local authority for names if applicable. Use marcrelator terms or ULAN terms for roleterms.

Follow your unit/collection guidelines per Supervisor/Collection Owner.

Best practice recommendation is to indicate a person responsible for the collection's administration in the DAMS, using (fill in here some guideline of value and authority) role term.

...

For requirement, indicate a person responsible for the collection's administration in the DAMS.

For greater interoperability, name elements should appear in the same order as in their authorized form (the authority cited in the <name> authority attribute). 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.

...

Contributor Name

• Type (select personal, corporate, conference, or family)
• Authority (if any) (select naf, viaf, or local)
• Primary (yes or no)

Role

• Authority (select marcrelator, ulan, or local)
• Authority URI (text field for marcrelator or ulan main URI )
• Language (if not English) (text field for lang attribute with prompt to use ISO-639-2 language codes)

...

Type

...

<typeOfResource>

lang attribute (value: eng)

collection attribute (value: yes)

manuscript attribute (value: yes, when selected by user)

...

none

...

<typeOfResource lang="eng" collection="yes" manuscript="yes">text</typeOfResource>

<typeOfResource lang="eng" collection="yes">mixed material</typeOfResource>

...

map <typeOfResource> to <dc:type>

...

 Leader/06 with the following controlled list of textual values:

• mixed material = Leader/06 value "p"

Attributes are used to further indicate whether the resource is a collection or an aggregation of items (designated in MARC 21 in Leader/07 (Bibliographic level)) or manuscript in nature (designated in MARC 21 as a separate Leader/06 code that combines the manuscript property with a resource type).

...

Type of Resources

...

Identifier

...

<identifier>

type attribute: (values: utldamsURI, utldamsPID, uri, pid, local)

...

no subelements

...

<identifier type=”pid”>isla-1234567-89 </identifier>
<identifier type="utldamsPID" displayLabel="UTLDAMS PID" > utlarch:67c766da-7364-49f8-82a5-443b13f8bd07 </identifier>

<identifier type=”local” displayLabel="Local">batch no.12456523</identifier>

...

The MODS <identifier> element is mapped to <dc:identifier>.

...

map those with attribute type "URI" to MARC 21 field 856

...

Follow your unit/collection guidelines per Supervisor/Collection Owner for local identifiers. Each identifier input separately.

Use local identifier type to record tape vault numbers for facilitate vault restore requests.

...

UTLDAMS URI

UTLDAMS PID

URI

Persistent Identifier (PID)

Local Identifier

...

Consult with developers on: possibility of drop down menu for identifier types to cut down on number of form fields; need for more than one PID; repeatable not just to allow one of each identifier type, but also to allow multiple of all or some identifier types. Writing PIDs of member objects into bag-info txt file for bagging (captures hasMember type of relationships, while including the rels-ext for the collection in the bag captures isMemberOf, allowing us to rebuild structure in each direction and be assured of collections' completeness outside of the interface/DAMS environment - important for preservation purposes).

Appropriate method for handling MODS write of utldamsURI and utldamsPID identifiers is pending, for object-level elements also.

Source Collection

...

<relatedItem> container that contains all subelements related to description of the source collection the asset originated from.

type attribute (value: source)

displayLabel attribute (value: Source collection)

...

<identifier> (if any collection identifiers apply)
type attribute (values: uri, pid, local)
displayLabel attribute (values: Source collection URI, Source collection persistent identifier, Source collection local identifier)

<titleInfo><title> (name of source collection)
lang attribute
displayLabel attribute (value: Source collection name)

...

<relatedItem displayLabel="Source collection" type="source"> 
<identifier type="local" displayLabel="Source collection local identifier">2011-01</identifier>
<identifier type="uri" displayLabel="Source collection URI">https://repositories.lib.utexas.edu/handle/2152/24081</identifier>
<titleInfo lang="eng" displayLabel="Source collection name">
<title>Oral Histories Collection</title>
</titleInfo>
</relatedItem>

<relatedItem displayLabel="Source collection" type="source">
<identifier type="uri" displayLabel="Source collection URI">https://archive.org/details/ArchiveIt-Collection-5070</identifier>
<titleInfo lang="eng" displayLabel="Source collection name">
<title>Internet Archive Collection</title>
</titleInfo>
</relatedItem>

...

map <relatedItem type="source"> and all subelements to dc:source.  Mapping multiple subelements to the single dc:source element will require addition of punctuation and re-ordering of elements (via XSLT) to achieve the desired result.

...

with attribute type "source" MARC 21 fields  590 , 79X 

...

Source Collection Identifier

Source Collection Name

...

Repository

...

<location>

...

<physicalLocation> (typically includes specific information used to locate a resource within a collection, such as the name or code of an institution/repository, and perhaps subcollection. Recommended guidelines limit this to indicating the physical, institutional home of an analog resource that has been digitized, not for a physical location of digital files. )

lang attribute

authority attribute (values: naf, viaf, local)

authorityURI attribute (values: http://id.loc.gov/authorities/names, http://viaf.org/)

displayLabel attribute (value: Repository)

...

...

<location><physicalLocation> does not easily map to any Dublin Core element

...

Repository

...