***Work in progress, help documentation coming soon!
Next-Level Collections
MODS Element: [name of element]
Definition | Definition of the element as applied in UTL DAMS (often based on MODS definition). |
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 (Subelements will have "Subelement" written below the subelement name in italics for clarification) | Describes how each subelement/attribute will be used in the DAMS. | Provides the XPath Syntax noted in metadata mapping sheets and employed in XML forms for the individual subelement or attribute |
XML |
Provides an example of the resulting XML datastream from the MODS, MADS, or DAMS Custom datastream. |
Dublin Core |
Provides the mapping to the Dublin Core metadata schema. |
MARC Mapping |
This mapping gives equivalencies between MARC and MODS data elements |
Title
Definition | A word, phrase, character, or group of characters, normally appearing in a resource, that names it or the work contained in it. |
MODS element name/attributes | <titleInfo> container element that contains all subelements related to title information lang attribute (values: eng as default; otherwise, any ISO-639-2 language codes) type attribute (values: translated, alternative, uniform) displayLabel attribute
usage attribute (when multiple titles are stored, apply usage="primary" to one for display and/or citation purposes) authority attribute (when type="uniform" use authority="naf" or authority="viaf") authorityURI attribute (values: http://viaf.org/, http://id.loc.gov/authorities/names) |
MODS subelements/attributes | <title> |
MODS examples | <titleInfo lang="lat"> <title>Canticum canticorum</title> </titleInfo> <titleInfo type="translated" lang="eng"> <title>Land surveying and agriculture equipment: a history</title> </titleInfo> <titleInfo type="alternative" lang="eng" displayLabel="Also known as"> <title>Bush-Cheney 2000</title> </titleInfo> <titleInfo type="uniform" displayLabel="Uniform/preferred title" lang="eng" authority="naf" authorityURI="http://id.loc.gov/authorities/names" usage="primary"> <title>Missale Carnotense</title> </titleInfo> |
DC mapping | map <titleInfo> and all subelements (such as optional <subTitle>) to <dc:title>. Prescribed punctuation separating elements of title need to be defined in XSLT and inserted during transformation. |
MARC mapping | 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 |
Required | yes - at least one <titleInfo><title> with lang attribute required |
Repeatable | yes |
Authority Control | Recommended, optional in form. Name Authority File (NAF) or Virtual International Authority File (VIAF) for uniform titles. Otherwise, follow unit/collection guidelines per Supervisor/Collection Owner. |
Input Guidelines | <titleInfo> will have default lang="eng" unless otherwise specified. Refer form users to to ISO-639-2 language codes. For uniform titles, use NAF preferred form. If none in NAF, consult VIAF. Titles should be as concise as possible. Refer to content standards like CCO, RDA, DCRMs, etc. Recommendation for minimal but appropriate use of punctuation. Follow your unit/collection guidelines per Supervisor/Collection Owner |
Form field labels/display labels | Title
|
Notes | For object details display, if there is a type attribute, include in parentheses alongside title value: Missale Carnotense (Uniform/preferred title) |
Description
Definition | A summary of the content of the resource. |
MODS element name/attributes | <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" |
MODS subelements/attributes | none |
MODS example | <abstract lang="eng" displayLabel="Description">Describes the results of an ongoing evaluation of State activity relating to improvement of criminal records. Activities reviewed include upgrading of accuracy and completeness of records, automation, implementation of positive identification procedures and procedures for responding to firearm background check inquiries.</abstract> |
DC mapping | map <abstract> to dc:description |
MARC mapping | 520 |
Required | yes, one with lang="eng" |
Repeatable | yes, to accommodate multiple languages |
Authority Control | not enforced in form; Follow your unit/collection guidelines per Supervisor/Collection Owner |
Input Guidelines | <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. |
Form field label/display label | Description |
For discussion |
Contributor
Definition | Person, organization, or event (conference, meeting, etc.) associated in some way with the resource. |
MODS element name/attributes | <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) |
MODS subelements/attributes | <namePart> <role><roleTerm> |
MODS example | <name authority="naf" authorityURI="http://id.loc.gov/authorities/names" type="personal" displayLabel="Contributor name"> <name type="personal" usage="primary" displayLabel="Contributor name"> <name type="corporate" displayLabel="Contributor name"> |
DC mapping | 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. |
MARC mapping | <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 |
Required | yes - at least one |
Repeatable | yes |
Authority Control | 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. |
Input Guidelines | 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. |
Form field label/display label | Contributor Name
Role
|
For discussion | BC: I'm unclear about how the valueURI attribute should be implemented. It doesn't show up in the examples or in the form field label sections. |
Type
Definition | A term that specifies the characteristics and general type of content of the resource. |
MODS element name/attributes | <typeOfResource> lang attribute (value: eng) collection attribute (value: yes) manuscript attribute (value: yes, when selected by user) |
MODS subelements/attributes | none |
MODS example | <typeOfResource lang="eng" collection="yes" manuscript="yes">text</typeOfResource> <typeOfResource lang="eng" collection="yes">mixed material</typeOfResource> |
DC mapping | map <typeOfResource> to <dc:type> |
MARC mapping | Leader/06 with the following controlled list of textual values:
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). |
Required | yes |
Repeatable | no |
Authority Control | controlled list of 11 terms from MODS guidelines: text, cartographic, notated music, sound recording, sound recording-musical, sound recording-nonmusical, still image, moving image, three dimensional object, software/multimedia, mixed material |
Input Guidelines | select from MODS controlled list of 11 terms |
Form field label/display label | Type of Resources |
For discussion |
Identifier
Definition | Contains a unique standard number or code that distinctively identifies a resource. |
MODS element name/attributes | <identifier> type attribute: (values: utldamsURI, utldamsPID, uri, pid, local) |
MODS subelements/attributes | no subelements
|
MODS example | <identifier type=”utldamsURI”>https://dams.lib.utexas.edu/islandora/object/utlarch%3A67c766da-7364-49f8-82a5-443b13f8bd07</identifier> <identifier type=”pid”>isla-1234567-89 </identifier>
<identifier type=”local” displayLabel="Local">batch no.12456523</identifier>
|
DC mapping | The MODS <identifier> element is mapped to <dc:identifier>. |
MARC mapping | map those with attribute type "URI" to MARC 21 field 856 |
Required | yes, at least: utldamsURI, utldamsPID |
Repeatable | yes |
Authority Control | local list of identifier types (per attributes above) |
Input Guidelines | 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. |
Form field label/display label | UTLDAMS URI UTLDAMS PID URI Persistent Identifier (PID) Local Identifier |
For discussion | 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
Definition | Source collection (physical or digital) the assets contained in the collection originated from. |
MODS element name/attributes | <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) |
MODS subelements/attributes | <identifier> (if any collection identifiers apply) <titleInfo><title> (name of source collection) |
MODS example | <relatedItem displayLabel="Source collection" type="source"> <relatedItem displayLabel="Source collection" type="source"> |
DC mapping | 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. |
MARC mapping | |
Required | no, but recommended for digitized assets, especially those intended for public access |
Repeatable | Yes (may be necessary for DAMS collections made from mixed source collections for exhibit, research or other purposes) |
Authority Control | local controlled list of identifier types |
Input Guidelines | Follow your unit/collection guidelines per Supervisor/Collection Owner. Collection names and identifiers should be as standardized as possible. |
Form field label/display label | Source Collection Identifier Source Collection Name |
For discussion |
Repository
Definition | The institution or repository that holds the original resource or from which it is available. |
MODS element name/attributes | <location> |
MODS subelements/attributes | <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) |
MODS examples | <location> <physicalLocation lang="eng" authority="viaf" authorityURI="http://viaf.org/" displayLabel="Repository">Alexander Architectural Archive</physicalLocation> </location> <location> <physicalLocation lang="spa" authority="viaf" authorityURI="http://viaf.org/" displayLabel="Repository">Centro de Investigaciones y Documentación de la Costa Atlántica</physicalLocation> </location> <location> <physicalLocation lang="eng" authority="local" displayLabel="Repository" >Walter Geology Library</physicalLocation> </location> <location> <physicalLocation lang="eng" displayLabel="Repository">University of Texas Libraries, Alexander Architectural Archive</physicalLocation> </location> |
DC mapping | <location><physicalLocation> does not easily map to any Dublin Core element |
MARC mapping | MARC 21 field 852 (subfields depend on attributes) and 535 (when the MARC record is describing the surrogate and the originals or duplicates are housed in a repository different from the repository that holds the surrogate) |
Required | no, but recommended for digitized assets, especially those intended for public access |
Repeatable | Yes (may be necessary for DAMS collections made from mixed source collections for exhibit, research or other purposes) |
Authority Control | Follow unit/collection guidelines per Supervisor/Collection Owner. Repository names should be as standardized as possible (potential authorities include Virtual International Authority File (VIAF) or local controlled list of repository names). |
Input Guidelines | If using a recommended authority, select from drop down menu to apply appropriate authority and authorityURI values in MODS. |
Form field label/display label | Repository |
For discussion |