***Work in progress. Contact the DAMS Management Team with Questions
...
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
| 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) usage attribute (usage="primary" is automatically applied for display and/or citation purposes) |
| MODS subelements/attributes | <title> |
| MODS examples | <titleInfo lang="lat" usage="primary"> <title>Canticum canticorum</title> </titleInfo> <titleInfo lang="eng" usage="primary"> <title>Land surveying and agriculture equipment: a history</title> </titleInfo> |
| DC mapping | map <titleInfo> and all subelements to <dc:title> |
| 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 - one <titleInfo><title> with lang attribute required |
| Repeatable | no |
| Authority Control | 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. 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 |
| Form field labels/display labels | Title
|
| Notes |
...
| 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. |
...