Work in progress | ||
| Expand | ||
|---|---|---|
| ||
|
Abstract
| Excerpt | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
MODS Element name: <subject><temporal><subject><topic> Short definition: The time period, date, or date range the content of the resource is aboutTopic the described 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
...
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. |
Definition
Topic the described resource is about.
DAMS input form fields
...
(Topic)
| DAMS form field name | form field type | required | MODS element | Collections Portal display | notes | ||||
|---|---|---|---|---|---|---|---|---|---|
| Coverage Period, Date, or Date RangeSubject - Topic Term | text field | noyes | subject/temporal | Time Period Covered | Coverage Language (if Period)topic | Topic |
| ||
| Topic Term Language | text field | noyes | subject[@lang]/temporaltopic (attribute of subject) | N/A | If Coverage information is a named periodAt least one English ("eng") topic term required. For additional terms, 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 periodAt least one English ("eng") topic term required. For additional terms, enter the appropriate three-letter language code from ISO-639-2b language codes. | subject[@lang] |
Subelements
The following subelements of <subject>are used in the DAMS:
- temporaltopic
- (topictemporal)
- (geographic)
- (hierarchicalGeographic)
- (cartographics)
- (geographicCode)
Subelement
<subject><temporal><subject><topic>
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)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.Attributes
No attributes for <temporal> are currently implemented in the DAMS.
Subelements
No subelements for
...
<topic>.
XML Examples
| Code Block | ||||
|---|---|---|---|---|
| ||||
<subject lang="eng">
|
...
<topic>Xeriscaping</topic> </subject> |
...
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
| Multiexcerpt | ||
|---|---|---|
| ||
|
|
|
|
|
|
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/topic | mods_subject_temporal | mods_subject_temporal | ||
| subject/topic | mods_subject_temporal | display_topic_ms | Used to create facets on the Collections portal start page. The Solr field display_topic is generated by capitalizing the first letter of the first word for each topic value. |