List of all available metadata fields that can be created and edited through the DAMS GUI. Click on the name of a field for a more detailed documentation of each field, including documentation about the underlying MODS XML elements.

Please refer to the UT Libraries Metadata Documentation for guidelines and templates: UT Libraries Metadata Documentation

Digital Asset Level

• Page:
  Contributor — REQUIRED REPEATABLE MULTILINGUAL
  

  MODS Element name: <name>

  Short definition: Person, organization, or event (conference, meeting, etc.) associated in some way with the resource.

  Input guidelines: At least one contributor name or "no attribution" statement required. Multiple Contributors can be added to an asset's metadata. Designate a primary contributor, even if only one contributor is entered. If one contributor has multiple roles, repeat entire Contributor section with new role term. To input name and type, use authority list of names (NAF, VIAF, or local authority). If no authority is available for personal names, input Last Name, First Name. For local authorities, enter authority URI with a description of the authority file. For role terms, input MARC 21 Relator terms (not codes), ULAN terms or local authority terms.

• Page:
  Creation, Issuance, Copyright date — REQUIRED
  

  MODS Element name: <originInfo><dateCreated> (Creation date) or <originInfo><dateIssued> (Issuance date); <originInfo><copyrightDate> (Copyright date)

  Short definition: Information about the original creation, publication or copyright date of the resource (adapted from MODS standard). An asset's metadata need to contain either a Creation date or an Issuance date. If both dates are present, the asset cannot be published to the Collections portal.

  Input guidelines: It is strongly recommended to input known dates in a structured format: YYYY-MM-DD (year-month-date). You can also enter year and month (YYYY-MM), or year only (YYYY). For unknown dates, enter "undated". For uncertain dates, select a date qualifier (approximate, inferred, or questionable). Alternatively, a limited number of textual date information can be entered: circa/ca/c/ca./c. YYYY, 19th century, 1960s, late 1850s, mid 4th century.

  Creation Date: Original creation date of the resource, most relevant to discovery of the resource by end-users. Input the original Creation date/ Start date of creation of the resource. End date of creation is recommended if a date range is applicable, but it is not mandatory.

  Issuance Date: The date that the resource was published, released, or issued. End date of issuance is recommended if a date range is applicable, but it is not mandatory.

  Copyright Date: A date in which a resource is copyrighted (date copyright was established, e. g. through registration).
  

• Page:
  Description — REQUIRED REPEATABLE MULTILINGUAL
  

  MODS Element name: <abstract>

  Short definition: A summary of the content of the resource.

  Input guidelines: Can include an abstract, table of contents, or account of described resource. This element provides end users with information about the digital resource that assists them in making a judgment about its likely usefulness, and also provides context, if needed, for controlled vocabulary used in the record. When creating a MODS record for a digital surrogate, record a summary of the content of the original resource. If only a portion of the resource was digitized, summarize only that portion. Do not include raw OCR output or full-text transcription of a textual or linguistic resource. At least one “eng” entry is required. Enter the appropriate three-letter language code from ISO-639-3 language codes. The use of a content standard of choice is strongly recommended. Follow your unit/collection guidelines per Supervisor/Collection Owner.

• Page:
  Digital Collection — REPEATABLE
  

  MODS Element name: <relatedItem type="host" displayLabel="Digital collection">

  Short definition: Digital collection/s in the DAMS or other access systems to which the asset belongs. Distinct from Source Collection.

  Input guidelines: Input name, identifier, and/or URL of digital collections to which the asset belongs, such as those in other access systems. If you enter information about a collection to which an asset belongs as Source Collection, do not duplicate this information here.

  Do not enter information about an asset's parent collection in the DAMS.

  Information about the DAMS parent collection of an asset is automatically added upon ingest.

• Page:
  Extent — MODS Element name: <physicalDescription><extent>

  Short definition: A statement of the number and specific material of the units of the resource that express physical extent.

  Input guidelines: Enter the number of pages in a paginated resource, or the dimensions of bibliographic or graphic materials. Avoid using symbols to denote units of measurement (e.g. 1"). Example values include number of photographs or an image's dimensions, or duration for A/V material. The field may be used with electronic resources, e.g. for digitized collection of slides, to show how many slides constitute the resource. Consult RDA or DACS standards for best practices. Follow your unit/collection guidelines per Supervisor/Collection Owner.

• Page:
  File Format — REQUIRED
  

  MODS Element name: <physicalDescription><internetMediaType>

  Short definition: The electronic file format type/extension of the object.

  Input guidelines: Select/enter the value that corresponds to file type/extension of object to be ingested. e.g. CR2, GIF, JPEG, PSD, TIFF. The file format in subelement <internetMediaType> is specified according to the template given in IANA's list of Media Types (formerly known as MIME types). Note that the expected values in the DAMS in some cases differ from the IANA specification. The expected values for JPEG and GIF images are "image/jpeg" and "image/gif" respectively, even though these values are not present in the IANA list. Example: For images in TIF (Tagged Image File) format, the expected value for internetMediaType is "image/tiff".

• Page:
  Form or Medium — REPEATABLE MULTILINGUAL
  

  MODS Element name: <physicalDescription><form>

  Short definition: A designation of a particular physical presentation of a resource, including the physical form or medium of material for a resource.

  Input guidelines: Characterize the form of the digitized or analog original using terms describing the material, support, or technique. Use authority control, e.g. AAT, TGM, LCGFT or locally controlled vocabularies. This field/element set is not used to describe the content of a resource. Use the Genre and/or Type of Resource elements to describe the content of the resource. If you do not use a controlled vocabulary, check the Type facet on the Collections portal to avoid spelling variants for uncontrolled terms.
  

• Page:
  Genre — REPEATABLE MULTILINGUAL
  

  MODS Element name: <genre>

  Short definition: A term or phrase that designates a category characterizing a particular style, form, or content, such as artistic, musical, cinematic, literary composition, etc.

  Input guidelines: Describe the content of the resource (e.g.; daguerreotypes, short films, portraits). Use the Form/Medium field set to characterize the physical form of the resource itself. Designate a primary genre, even if only one genre is entered. Use authority control and enter term from a recommended vocabulary: Art & Architecture Thesaurus, Thesaurus for Graphic Materials, Library of Congress Genre/Form Terms, Library of Congress Subject Headings.

• Page:
  Identifier — REPEATABLE
  

  MODS Element name: <identifier>

  Short definition: Contains a unique standard number or code that distinctively identifies a resource.

  Input guidelines: Input one identifier per text field/element and designate the corresponding identifier type. Currently, the following identifier types are supported by the DAMS:

  • URI: Persistent identifier in the form of typically a URL (e.g. DOI/Handle, ARK, URN). A URI may or may not be resolvable.
  • PID: Persistent identifier that is not in the form of a URI
  • OCLC Source: OCLC number referring to a catalog entry describing the original work, e.g. the physical original of a digitized work
  • OCLC Surrogate: OCLC number referring to the catalog entry describing a digital copy of a work (if such a catalog entry exists)
  • Local: Any identifier string for local use, e.g. call number, file names or tape vault numbers.

  Follow your unit/collection guidelines per Supervisor/Collection Owner for local identifiers.

  The following identifier element type values are reserved for identifiers that are automatically created by the DAMS upon ingest of an asset:

  • utldamsURI
  • utldamsPID
  • fileName

  Do not remove, alter or overwrite these identifiers. Do not use the reserved identifier type values when preparing your own metadata outside of the DAMS.

  For more information see the following documentation page: Identifier (autogenerated).

• Page:
  Identifier (autogenerated) — AUTOGENERATED
  

  MODS Element name: <identifier>

  Short definition: System-generated identifiers for assets in the DAMS.

  Input guidelines: Upon ingest, the DAMS automatically creates identifier metadata elements type with the following values:

  • utldamsURI: the URI of an asset in the DAMS
  • utldamsPID: the PID (unique identifier string) for an asset in the DAMS
  • fileName: the name of the data file ingested as the main data object for an asset in the DAMS (the OBJ datastream)

  Do not remove, alter or overwrite identifier elements with types utldamsURI, utldamsPID or fileName. Do not use these identifier type values when preparing your own metadata outside of the DAMS.

  Removing, altering or overwriting these identifier elements will cause the DAMS to malfunction.

• Page:
  Key Date (autogenerated) — AUTOGENERATED
  

  MODS Element name: <originInfo><dateCreated keyDate="yes"> (Creation date) or <originInfo><dateIssued keyDate="yes"> (Issuance date)

  Short definition: System-generated, machine-readable date value derived from either Creation Date or Issuance Date.

  Input guidelines: The system will create a machine-readable date element with a keyDate attribute based on the user-provided information for Date created or Date issued. If a date range is specified, only the start date will be used as key date. If textual date information is provided, the key date will be a numerical date approximating the textual date information. The machine-readable date is for instance used for sorting of search results.

  The ingest process currently ignores a keyDate attribute set by users when preparing metadata as MODS XML. Instead, the system will create a new machine-readable date element with a keyDate attribute based on dateIssued or dateCreated (in this order and depending on which of the two is available). Any user-provided keyDate attribute will be stripped from the metadata upon ingest.

  If you want to designate a specific date element as the key date in metadata prepared for batch ingest, add the following attribute-value pair to the respective element: keyGen="yes".

• Page:
  Language — REQUIRED REPEATABLE MULTILINGUAL
  

  MODS Element name: <language>

  Short definition: A designation of the language in which the content of a resource is expressed.

  Input guidelines: Enter the full (English) language name in the Language Name text field, as found in the list of language Reference Names provided by SIL: https://iso639-3.sil.org/code_tables/download_tables. Capitalize the first letter of the name. If the asset does not contain linguistic content, enter "not applicable" (no capitalization). In the Language Code field, indicate the language of the resource by entering the appropriate three-letter language code from ISO-639-3 language codes. If the language name is given as 'not applicable' (the asset does not contain linguistic content), use code 'zxx'.
  

• Page:
  MODS Language of Cataloging — REQUIRED REPEATABLE MULTILINGUAL
  

  MODS Element name: <recordInfo><languageOfCataloging>

  Short definition: The language of the text of the cataloging in the MODS record.

  Input guidelines: Indicate the language of the text of the cataloging by entering the appropriate three-letter language code from ISO-639-2b language codes.  Designate a primary language, even if only one language is entered.

• Page:
  MODS Record Content Source — REQUIRED REPEATABLE
  

  MODS Element name: <recordInfo><recordContentSource>

  Short definition: Name of the organization, unit or entity that either created or modified the original metadata record.

  Input guidelines: Default is University of Texas Libraries. Replace as needed. The name or code should be pulled from an authoritative list and indicated in the authority and authorityURI attribute. This field/element should be repeated for each code or name recorded.

• Page:
  MODS Record Creation Date (autogenerated) — AUTOGENERATED
  

  MODS Element name: <recordInfo><recordCreationDate>

  Short definition: The date on which the MODS record was first created in or ingested into the DAMS.

  Input guidelines: This MODS element is automatically created upon first ingest of a metadata record in the DAMS. Do not add a recordCreationDate element to externally created MODS metadata, as it will be overwritten at the time of ingest.
  

• Page:
  MODS Record Origin Statements — REPEATABLE 
  

  MODS Element name: <recordInfo><recordOrigin>

  Short definition: Information about the origin or provenance of the MODS record.

  Input guidelines: Use to record information about the origin, or provenance of the MODS record including what methods were used to prepare the MODS record (machine generated or human prepared) and what transformations have been applied (e.g., the result of converting an existing MARC 21 record to MARCXML and to MODS). Follow your unit/collection guidelines per Supervisor/Collection Owner.

• Page:
  Note — REPEATABLE
  

  MODS Element name: <note>

  Short definition: General textual information relating to a resource.

  Input guidelines: Select one of the pre-specified note types from the dropdown field. The following note types are currently available:

  Notes displayed on the Collections portal (public)
  

  • citation: Input standardized citations that may be valuable for users. Note that Collections portal will automatically generate some citation formats.
    
  • condition: Input statement about the original asset's condition. Apply content standards like RDA, DCRM or DACS to record information about an item's condition.
    
  • date captured: Input capture/recording/digitization dates. Input only the date in structured format YYYY-MM-DD. To record time intervals, append a forward slash ('/') to the start date of the interval, followed by the end date of the interval, without spaces between dates and separator (example: 2012-05-29/2012-05-31). If only part of a date is known, enter year and month only (YYYY-MM) or year only (YYYY).
    
  • date other: Input other dates of interest. Input only the date in structured format YYYY-MM-DD. To record time intervals, append a forward slash ('/') to the start date of the interval, followed by the end date of the interval, without spaces between dates and separator (example: 2012-05-29/2012-05-31). If only part of a date is known, enter year and month only (YYYY-MM) or year only (YYYY).

  • general (default): Input notes intended for public display on front end and not accommodated by other elements or note types.

    Template note text available for assets where only metadata is published to the Collections Portal and for redacted assets: Metadata text templates

  • origin: Input details about asset origin/provenance not adequately captured elsewhere. Apply content standards like RDA, DCRM or DACS to record information about origin/provenance.
  • scale: Input scale for non-cartographic resources (as opposed to values in Subject-Cartographics fields).

  Notes not displayed on the Collections portal (internal)

  • description: Input descriptive information not intended/suitable for public display. Enter descriptive information intended for the public in the Description form field.
  • date issued: Input publication/dissemination dates. Input only the date in structured format YYYY-MM-DD. To record time intervals, append a forward slash ('/') to the start date of the interval, followed by the end date of the interval, without spaces between dates and separator (example: 2012-05-29/2012-05-31). If only part of a date is known, enter year and month only (YYYY-MM) or year only (YYYY).

  • file path: Input file reference to aid location of related files in separate storage systems.

    It is best practice to reference the tape vault location of the original presentation grade file ingested into the DAMS.

  • merged: Input indication that asset is the result of merging various parts into one (e.g., piecemeal scans of oversize material).
    
  • UTL GeoData ID (utlGeoDataID): Enter GeoData ID for content that might also be ingested into the GeoData portal. See detailed instructions on adding map content.
• Page:
  Place of Publication or Origin — REPEATABLE MULTILINGUAL
  

  MODS Element name: <originInfo><place>

  Short definition: Name of a place associated with the issuing, publication, release, distribution, manufacture, production, or origin of a resource.

  Input guidelines: Refer to content standards like RDA or DACS to determine which places to input. Indicate the language of the Place by entering the appropriate three-letter language code from ISO-639-3 language codes. Designate a primary place, even if only one place is entered.
  

• Page:
  Publisher — REPEATABLE MULTILINGUAL
  

  MODS Element name: <originInfo><publisher>

  Short definition: The name of the entity that published, printed, distributed, released, issued, or produced the resource, or a statement about publication/origin.

  Input guidelines: Input a named entity determined to be the publisher/originator for a resource or a statement about publication/origin. Descriptive standards such as RDA or DACS should be used to format the name of the publisher.

• Page:
  Related Resource — REPEATABLE MULTILINGUAL
  

  MODS Element name: <relatedItem type="host" displayLabel="Parent work"> or <relatedItem type="series"> or <relatedItem> (no attributes)

  Short definition: Information that identifies other resources related to the one being described, excluding information entered for Source collection or Digital collection.

  Input guidelines: Enter information that identifies other resources related to the one being described. Identify parent works, series that the asset is a part of, or other general related resources that aren't otherwise captured by Digital Collection or Source Collection fields.

  Do not enter information about an asset's parent collection in the DAMS.

  Information about the DAMS parent collection of an asset is automatically added upon ingest.

• Page:
  Repository — REQUIRED MULTILINGUAL
  

  MODS Element name: <location><physicalLocation>

  Short definition: The institution or repository that holds the original resource or where it is available.

  Input guidelines: Contains the name of the repository owning the physical original of a digitized resource. Controlled terminology, only the following values are currently permitted for this field/element:

  • Alexander Architectural Archives, University of Texas Libraries, The University of Texas at Austin
  • Architecture and Planning Library Special Collections, University of Texas Libraries, The University of Texas at Austin
  • Architecture and Planning Library, University of Texas Libraries, The University of Texas at Austin
  • Benson Latin American Collection, LLILAS Benson Latin American Studies and Collections, The University of Texas at Austin
  • Fine Arts Library, University of Texas Libraries, The University of Texas at Austin
  • Perry-Castañeda Library Maps, University of Texas Libraries, The University of Texas at Austin
  • University of Texas Libraries, The University of Texas at Austin (default)
  • Walter Geology Library, University of Texas Libraries, The University of Texas at Austin

  If you need additional values for this field, please consult with the DAMS management team.

• Page:
  Rights — REQUIRED
  

  MODS Element name: <accessCondition>

  Short definition: Indication of rights relating to access and use of a resource.

  Input guidelines: Select an appropriate statement about the copyright status (options include standard public domain mark and statements from http://rightsstatements.org and https://creativecommons.org/licenses/). Also select a value indicating the access restrictions to be enforced by the UT Libraries Collections portal. The following statements are available in the DAMS:

  Copyright status (<accessCondition type="use and reproduction">)
  

  URI stored in MODS	Short statement meaning
  http://rightsstatements.org/vocab/InC/1.0/	In Copyright
  http://rightsstatements.org/vocab/InC-OW-EU/1.0/	In Copyright - EU Orphan Work
  http://rightsstatements.org/vocab/InC-EDU/1.0/	In Copyright - Educational Use Permitted
  http://rightsstatements.org/vocab/InC-NC/1.0/	In Copyright - Non-Commercial Use Permitted
  http://rightsstatements.org/vocab/InC-RUU/1.0/	In Copyright - Rights-Holder(s) Unlocatable or Unidentifiable
  http://rightsstatements.org/vocab/NoC-CR/1.0/	No Copyright - Contractual Restrictions
  http://rightsstatements.org/vocab/NoC-NC/1.0/	No Copyright - Non-Commercial Use Only
  http://rightsstatements.org/vocab/NoC-OKLR/1.0/	No Copyright - Other Known Legal Restrictions
  http://rightsstatements.org/vocab/NoC-US/1.0/	No Copyright - United States
  http://rightsstatements.org/vocab/CNE/1.0/	Copyright Not Evaluated
  http://rightsstatements.org/vocab/UND/1.0/	Copyright Undetermined
  http://rightsstatements.org/vocab/NKC/1.0/	No Known Copyright
  https://creativecommons.org/publicdomain/mark/1.0/	CC Public Domain mark
  https://creativecommons.org/licenses/by/4.0	CC-BY Attribution
  https://creativecommons.org/licenses/by-sa/4.0	CC-BY-SA Attribution-ShareAlike
  https://creativecommons.org/licenses/by-nd/4.0	CC-BY-ND Attribution-NoDerivatives
  https://creativecommons.org/licenses/by-nc/4.0	CC-BY-NC Attribution-NonCommercial
  https://creativecommons.org/licenses/by-nc-sa/4.0	CC-BY-NC-SA Attribution-NonCommercial-ShareAlike
  https://creativecommons.org/licenses/by-nc-nd/4.0	CC-BY-NC-ND Attribution-NonCommercial-NoDerivatives

  Access restriction (<accessCondition type="restriction on access">)
  

  Value stored in MODS	Statement meaning	Note
  public access	Public Access
  ut eid only	UT EID only	Not yet supported by Collections portal
  password protected	Password protected	Not yet supported by Collections portal
  metadata only	Metadata only	For assets where only metadata is published to the Collections Portal, it is advised to add a general note informing users why the asset is not accessible online. Template text for a note is available here: Metadata text templates
  private	Private	Not yet supported by Collections portal

  
  

• Page:
  Source Collection — MULTILINGUAL
  

  MODS Element name: <relatedItem type="source" displayLabel="Source collection" usage="primary">

  Short definition: Primary physical or digital collection the asset originated from. Distinct from Digital Collection.

  Input guidelines: Input name and identifiers of a primary physical or digital collection context from which the asset originated. If you enter information about a primary digital collection as Source Collection, do not duplicate this information in the Digital Collection fields/elements.

  Recommended for digitized assets, especially those intended for public access. Collection names and identifiers should be as standardized as possible. Follow your unit/collection guidelines per Supervisor/Collection Owner. Enter URI, PID, and local identifiers when available.

  The title entered for Source Collection is used to generate a search facet in the Collections portal.

  Use consistent spelling for the Source Collection Title, as spelling variants or typos will result in separate facets being generated.

  Source Collection information is not required, but it is highly recommended to enter at least the title of a Source Collection. Consider supplying a collection name to facilitate browsing if now established collection name exists. Information in this field/element is currently the only structured information allowing to browse assets by their collection context in the Collections portal.

• Page:
  Subject: Cartographics — REPEATABLE
  

  MODS Element name: <subject><cartographics>

  Short definition: Cartographic (maps or charts) data indicating spatial coverage.

  Input guidelines: Fill out all cartographic subelements or leave all blank. Use to record scale (e.g. 1:25,000), projection, and/or coordinates. You may record: "not drawn to scale", "scales differ", or "no projection statement" in these fields.

  Do not enter scales for non-cartographic materials in this subelement.

  Add scales for non-cartographic materials in a Note filed of type "scale" instead.

• Page:
  Subject: Geographic Code — REPEATABLE
  

  MODS Element name: <subject><geographicCode>

  Short definition: A geographic area code associated with a resource.

  Input guidelines: A geographic code that represents the same entity as a term in the Geographic Term form field. Enter appropriate Alpha-3 code from the directory of ISO-3166 standard country codes.
  

• Page:
  Subject: Geographic Term — REPEATABLE MULTILINGUAL
  

  MODS Element name: <subject><geographic>

  Short definition: General geographic term that represents the primary topic on which the resource is focused.

  Input guidelines: One geographic term must be designated as primary for display/browse and/or citation purposes. Indicate the language of the geographic term by entering the appropriate three-letter language code from ISO-639-3 language codes. At least one English ("eng") entry is required.

• Page:
  Subject: Hierarchical Geographic Terms — REPEATABLE MULTILINGUAL
  

  MODS Element name: <subject><hierarchicalGeographic>

  Short definition: A geographic name given in a hierarchical form relating to the resource.

  Input guidelines: Use geographic name terms that are as specific as necessary or appropriate. First order political divisions may have different terms depending on the country. It is recommended to provide geographic terms that fall above the most specific term in the hierarchy (i.e. referring to larger geographic entities), to avoid ambiguity and to facilitate search and browsing.

  In general, use the term(s) most commonly used in the original language or its translation for a geographic entity. Form fields in a fieldset must be input in the same language.

  The following hierarchy levels are currently available in the DAMS:

  • country: Name of a country, i.e. a political entity considered a country.
  • region: Includes regions that have status as a jurisdiction, as well as regions incorporating more than one first level jurisdiction (e.g. Middle East).
  • state: Includes first order political divisions called states within a country, e.g. in U.S., Argentina, Italy. Use also for French départements.
  • territory: Name of a geographical area belonging to or under the jurisdiction of a governmental authority.
  • county: Name of the largest local administrative unit in various countries.
  • city: Name of an inhabited place incorporated as a city, town, etc.
  • city section: Name of a smaller unit within a populated place, e.g., neighborhood, city or local park, street, street address, zip/postal code, census tract number, or district.
  • area: Names of non-jurisdictional geographic entities. Use area for continents, islands (a tract of land surrounded by water and smaller than a continent but not itself a separate country), and extraterrestrial areas (any extraterrestrial entity or space, including solar systems, galaxies, star systems, planets and geographic features of individual planets). Area may be used for terms that do not fit neatly into other designations in this hierarchy.

  The Place Name facet on the start page of the Collections portal is generated from entries in the Subject: Geographic Term form field/<geographic> element.

  If you want to create a Place Name facet for an asset you are describing, copy one or more terms from the hierarchical description into the Geographic Term field/element.

• Page:
  Subject: Temporal Coverage — REPEATABLE MULTILINGUAL
  

  MODS Element name: <subject><temporal>

  Short definition: The time period, date, or date range the content of the resource is about.

  Input guidelines: Temporal Coverage may be expressed as a controlled subject term or as a structured date. Enter a named time period (Elizabethan), date (YYYY-MM-DD), or date range (YYYY/YYYY, YYYY-YYYY, YYYY to YYYY). Recommended authorities are AAT, LCSH and PeriodO. Input dates in structured format YYYY-MM-DD. If only part of a date is known, enter year and month only (YYYY-MM) or year only (YYYY). To record time intervals, preferably append a forward slash ('/') to the start date of the interval, followed by the end date of the interval, without spaces between dates and separator (example: 2012-05-29/2012-05-31).
  

• Page:
  Subject: Topic — REQUIRED REPEATABLE MULTILINGUAL
  

  MODS Element name: <subject><topic>

  Short definition: Topic the described resource is about.

  Input guidelines: At least one English topic term required. Use authority control if appropriate. If you do not use a controlled vocabulary, check the Topic facet on the Collections portal to avoid spelling variants for uncontrolled terms. Follow your unit/collection guidelines.
  

• Page:
  Title — REQUIRED REPEATABLE MULTILINGUAL
  

  MODS Element: <titleInfo>

  Short definition: Name given to the resource to be described.

  Input guidelines: At least one Title with language attribute is required. Designate a primary title, even if only one title is entered. Variants of a Titles can be added to an asset's metadata, e.g. a translated title, alternative titles or uniform (authority-controlled) title forms. If entering additional titles, pay close attention to fields Title Type, Primary Title, and Authority. Input the title as it appears on the piece. Refer to content standards like CCO, RDA, DACS, or DCRM(x). For objects that don't have a title on the piece, provide a concise title that will assist end users in deciding whether to investigate a resource further. Otherwise, "primary title not available" will display in the DAMS. The subtitle may be included as part of the title or in an optional subtitle field to store and display the information as a separate element.

  Title type is optional but recommended if applicable:

  • Uniform title: A title or form of title that is chosen to identify a work and is an authorized access point representing the work.   For uniform titles, indicate authority NAF or VIAF in the authority field.

  • Alternative title: Varying forms of title associated with the item, whether or not the title is on the piece.

  • Translated title: A title that has been translated into a different language. 

  Indicate the language of the title by entering the appropriate three-letter language code from ISO-639-2 language codes.
  

• Page:
  Type of Resource — REQUIRED
  

  MODS Element name: <typeOfResource>

  Short definition: A term that specifies the characteristics and general type of content of the resource.

  Input guidelines: Specify the characteristics and general type of content of the resource (original resource, not digitized version). Information on the Type of Resource is about the original item. For example, in the case of a digitized photograph, Type of Resource information would apply to the analog original; in born-digital materials, it would apply to the original digital format. This element includes a high-level type that categorizes the material in a general way using an enumerated list of values. More specific typing is done in the information on Genre.

  Select one of the available values for resource type and indicate if the content is a manuscript or not. Manuscripts are locally defined as unpublished, single instance textual materials, notated music, and cartographic materials. Manuscripts can be handwritten, typed (typescript), or computer printout materials intended to exist as a single instance. Follow your unit/collection guidelines per Supervisor/Collection Owner.

  Per MODS specification, the following values are available for typeOfResource:

  • text – Resources that are basically textual in nature.
  • cartographic – Includes maps, atlases, globes, digital maps, and other cartographic items.
  • notated music – Graphic, non-realized representations of musical works, both in printed and digitized manifestations that represent the four components of musical sound: pitch, duration, timbre, and loudness.
  • sound recording – Used when a mixture of musical and nonmusical sound recordings occurs in a resource or when a user does not want to or cannot make a distinction between musical and nonmusical.
  • sound recording-musical – Used when a resource is predominately a musical sound recording.
  • sound recording-nonmusical – Used when the sound recording is nonmusical in nature.
  • still image – Includes two-dimensional images and slides and transparencies.
  • moving image – Includes motion pictures and videorecordings, as well as television programs, digital video, and animated computer graphics—but not slides and transparencies. It does not include moving images that are primarily computer programs, such as computer games or computer-oriented multimedia; these are included in "software, multimedia".
  • three dimensional object – Includes man-made objects such as models, sculptures, clothing, and toys, as well as naturally occurring objects such as specimens mounted for viewing.
  • software, multimedia – Appropriate for any electronic resource without a significant aspect that indicates one of the other <typeOfResource> categories. It includes: software, numeric data, computer-oriented multimedia, and online systems and services.
  • mixed material – Indicates that there are significant materials in two or more forms that are usually related by virtue of their having been accumulated by or about a person or body. Mixed material includes archival fonds and manuscript collections of mixed forms of materials, such as text, photographs, and sound recordings.
• Page:
  UTLDAMS Digital Collection (autogenerated) — AUTOGENERATED
  

  MODS Element name: <relatedItem type="host" displayLabel="UTLDAMS Digital Collection">

  Short definition: Parent collection in the DAMS to which the asset belongs. Distinct from Source Collection and Digital Collection.

  Input guidelines: System-generated value created upon ingest.

  Do not remove, alter or overwrite a relatedItem element with displayLabel UTLDAMS Digital Collection or any of its subelements. Do not use the combination of type="host" and displayLabel="UTLDAMS Digital Collection"  for relateItem elements when preparing your own metadata outside of the DAMS.

  Removing, altering or overwriting the relatedItem element with displayLabel UTLDAMS Digital Collection or any of its subelements will cause the DAMS to malfunction.

Collection Level

• Page:
  Contributor (Collections) — see Contributor(s)
• Page:
  Description (Collections) — see Description
• Page:
  Identifier (Collections) — see Identifier

  For DAMS Collections, you can enter Identifiers of type URI, PID or local.

• Page:
  Identifier (Collections) (autogenerated) — see Identifier (autogenerated)

  Upon creating a new Collection in the DAMS, the system will automatically add identifiers of type utldamsPID and utldamsURI.

• Page:
  MODS Language of Cataloging (Collections) — see MODS Language of Cataloging
• Page:
  MODS Origin Statement(s) (Collections) — see MODS Record Origin Statements
• Page:
  MODS Record Content Source(s) (Collections) — see MODS Record Content Source
• Page:
  MODS Record Creation Date (Collections) (autogenerated) — see MODS Record Creation Date (autogenerated)
• Page:
  Repository (Collections) — see Repository

  A digital Collection in the DAMS can hold digitally reformatted versions of objects from multiple physical locations/repositories. Therefore the Repository statement in a Collection's metadata is repeatable.

• Page:
  Source Collection (Collections) — see Source Collection

  A digital Collection in the DAMS can hold digitally reformatted versions of objects from multiple (primary) source collection contexts. Therefore the Source Collection statement in a Collection's metadata is repeatable.

• Page:
  Title (Collections) — see Title

  The Title statement of a DAMS Collection is not repeatable.

• Page:
  Type of Resource (Collections) — see Type of Resource

  When adding a Collection to the DAMS, the MODS XML element typeOfResource in the Collection metadata will automatically receive a collection="yes" attribute.

• Page:
  UTLDAMS Digital Collection (Collections) (autogenerated) — see UTLDAMS Digital Collection (autogenerated)