Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Expand
titleClick here to show Table of Contents...

Table of Contents

...

Excerpt

Status
colourBlue
titleRepeatable
 
Status
colourGreen
titleMultilingual

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).

Definition

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

...

DAMS form field nameform field typerequiredMODS elementCollections Portal displaynotes
Coverage Period, Date, or Date Rangetext fieldnosubject/temporalTime Period Covered
Info

Information entered here feeds the browsing facet "Time Period Covered" in the Collections portal. Consider checking the existing facet terms to avoid spelling variants: https://collections.lib.utexas.edu/catalog/facet/mods_subject_temporal_ms

Coverage Language (if Period)text fieldno

subject[@lang]/temporal

(attribute of subject)

N/AIf Coverage information is a named period, enter the appropriate three-letter language code from ISO-639-2b language codes. Default is "eng" (English).

MODS Element description

Element <subject>

...


Attribute name

Details

XPath syntax examples

lang

value:

If Coverage information is a named period, enter the appropriate three-letter language code.

subject[@lang]

Subelements

The following subelements of <subject>are used in the DAMS:

  • temporal
  • (topic)
  • (geographic)
  • (hierarchicalGeographic)
  • (cartographics)
  • (geographicCode)

Subelement <subject><temporal>

Guidelines for use

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).

Attributes

No attributes for <temporal> are currently implemented in the DAMS.

Subelements

No subelements for <temporal>.

XML Examples

Code Block
languagexml
collapsetrue
<subject lang="eng">
	<temporal>1918-06-29</temporal>
</subject>

<subject lang="eng">
	<temporal>Elizabethan</temporal>
</subject>
<subject lang="spa">
	<temporal>Isabelino</temporal>
</subject>

Mappings

Dublin Core

Depending on the direction of mapping necessary, check

MARC 21

Multiexcerpt
MultiExcerptNamemarc-subject-temporal

see http://www.loc.gov/standards/mods/mods-mapping.html#subject.

MARC 21 fieldMapping conditionMODS elementNotes
*
subject/temporalDo not use the temporal[@encoding] attribute when mapping temporal coverage information.

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.

MODS elementMapping conditionSolr DAMSSolr Collections PortalNotes
subject/temporal
mods_subject_temporalmods_subject_temporal