| Warning | ||
|---|---|---|
| Expand | ||
| ||
|
Abstract
| Excerpt | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
MODS Element name: <subject><temporal><subject><geographicCode> Short definition: The time period, date, or date range the content of the resource is aboutA geographic area code associated with a resource. Input guidelines: Temporal Coverage may be expressed A geographic code that represents the same entity 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
...
term in the Geographic Term form field. Enter appropriate Alpha-3 code from the directory of ISO-3166 standard country codes. |
Definition
A geographic area code associated with a resource.
DAMS input form fields
...
(Geographic Code)
| DAMS form field name | form field type | required | MODS element | Collections Portal display | notes | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Coverage Period, Date, or Date RangeSubject - Geographic Code | text field | no | subject/temporal | Time Period Covered | Coverage Language (if Period) | text field | no | subject[@lang]/temporal (attribute of subject) | N/A | If Coverage information is a named period, enter the appropriate three-letter language code from ISO-639-2b language codes. Default is "eng" (English)geographicCode | Geographic Code | Enter appropriate Alpha-3 code from the directory of ISO-3166 standard country codes. |
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
...
value:
If Coverage information is a named period, enter the appropriate three-letter language code.
...
No attributes are currently implemented in the DAMS for <subject> when used with the <geographicCode> subelement.
Subelements
The following subelements of
...
<subject> are used in the DAMS:
- geographicCode
- (temporal)
- (topic)
- (geographic)
- (hierarchicalGeographic)
- (cartographics)
...
Subelement
...
<subject><geographicCode>
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
...
Enter appropriate Alpha-3 code from the ISO-3166 standard country codes.
Attributes
Attribute name | Details | XPath syntax examples |
|---|---|---|
| authority | value:
| subject/geographicCode[@authority="iso3166"] |
Subelements
No subelements for
...
<geographicCode>.
XML Examples
| Code Block | ||||
|---|---|---|---|---|
|
...
<subject> <geographicCode authority="iso3166">GRL</geographicCode> </subject> |
Mappings
Dublin Core
Depending on the direction of mapping necessary, check
...
Currently, no data from <geographicCode> subelements is mapped to DC elements.
MARC 21
...
See http://www.loc.gov/standards/mods/mods-mapping.html. The following specific guidelines apply for the DAMS:
| MARC 21 field | Mapping condition | MODS element | Notes |
|---|
...
| 043$a |
...
| N/ |
...
| A | Do not |
...
map from MARC subfield 043$a. MARC codes for geographic area are not implemented in the DAMS MODS. | |||
| 043$c | subject/geographicCode | Data transformation required. Map the Alpha-2 code from MARC subfield 043$c to the corresponding Alpha-3 code from the directory of ISO-3166 standard country codes. |
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/ |
...
| geographicCode | mods_subject_ |
...
| geographicCode | mods_subject_ |
...
| geographicCode |