Abstract
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.
Definition
A geographic name given in a hierarchical form relating to the resource.
DAMS input form fields
Hierarchical Geographic Term(s)
| DAMS form field name | form field type | required | MODS element | Collections Portal display | notes |
|---|---|---|---|---|---|
| Country | text field | no | subject/hierarchicalGeographic/country | Geographic Coverage | Name of a country, i.e. a political entity considered a country. |
| Region | text field | no | subject/hierarchicalGeographic/region | Geographic Coverage | Includes regions that have status as a jurisdiction, as well as regions incorporating more than one first level jurisdiction (e.g. Middle East). |
| State | text field | no | subject/hierarchicalGeographic/state | Geographic Coverage | Includes first order political divisions called states within a country, e.g. in U.S., Argentina, Italy. Use also for French départements. |
| Territory | text field | no | subject/hierarchicalGeographic/territory | Geographic Coverage | Name of a geographical area belonging to or under the jurisdiction of a governmental authority. |
| County | text field | no | subject/hierarchicalGeographic/county | Geographic Coverage | Name of the largest local administrative unit in various countries. |
| City | text field | no | subject/hierarchicalGeographic/city | Geographic Coverage | Name of an inhabited place incorporated as a city, town, etc. |
| City Section | text field | no | subject/hierarchicalGeographic/citySection | Geographic Coverage | 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 | text field | no | subject/hierarchicalGeographic/area | Geographic Coverage | 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. |
| Language of Subject-Hierarchical Geographic Terms | text field | no | subject[@lang]/hierarchicalGeographic | N/A | Enter the appropriate three-letter language code from ISO-639-2b language codes. Default is "eng" (English). |
MODS Element description
Element <subject>
http://www.loc.gov/standards/mods/userguide/subject.html
Guidelines for use
<subject> is a container element that contains subelements relating to the subject aspect of the resource.
Attributes
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
Mappings
Dublin Core
Depending on the direction of mapping necessary, check
- DC to MODS: https://www.loc.gov/standards/mods/dcsimple-mods.html
- MODS to DC: http://www.loc.gov/standards/mods/mods-dcsimple.html
MARC 21
see http://www.loc.gov/standards/mods/mods-mapping.html.
| MARC 21 field | Mapping condition | MODS element | Notes |
|---|---|---|---|
| * | subject/temporal | Do 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 element | Mapping condition | Solr DAMS | Solr Collections Portal | Notes |
|---|---|---|---|---|
| subject/temporal | mods_subject_temporal | mods_subject_temporal |