Description

 Click here to show Table of Contents...

Abstract

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.

Definition

Used to record a succinct summary of some aspect of the content of the resource.

DAMS input form fields

Description(s)

DAMS form field nameform field typerequiredMODS elementCollections Portal displaynotes
Descriptiontext fieldyesabstractDescription

Multiple description texts will be concatenated for display on the Collections portal. The different entries are separated by the pipe symbol (|).

Description languagetext fieldyesabstract[@lang]N/AEnter the appropriate three-letter language code from ISO-639-3 language codes. Default is 'eng' for English. At least one English entry must be present.

MODS Element description

Element <abstract>

http://www.loc.gov/standards/mods/userguide/abstract.html

Guidelines for use

Used to record a succinct summary of some aspect of the content of the resource. 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.

Attributes


Element Parts

Details

XPath syntax examples

lang

values:

Enter ISO-639-3 language code

(3 letters).

abstract[@lang="eng"]
displayLabel

value:

  • Description

Automatically generated upon manual ingest. Currently, no other value is supported in the DAMS.

abstract[@displayLabel="Description"]

Subelements

There are no subelements for <abstract>.

XML Examples

<abstract lang="eng" displayLabel="Description">Describes the results of an ongoing evaluation of State activity relating to 
improvement of criminal records. Activities reviewed include upgrading of accuracy and completeness of records, automation, implementation of positive identification procedures and procedures for responding to firearm background check inquiries.</abstract>

Mappings

Dublin Core

Depending on the direction of mapping necessary, check

The following specific guidelines apply for the DAMS:

Dublin Core fieldMapping conditionMODS elementNotes
dc:description
abstract

Approximate mapping.

Depending on the exact content, dc:description might also map to MODS elements note or tableOfContents (not implemented in the DAMS).

MARC 21

see http://www.loc.gov/standards/mods/mods-mapping.html#abstract. The following specific guidelines apply for the DAMS:

MARC 21 fieldMapping conditionMODS elementNotes
505
abstract

Formatted content, e.g. a table of contents.

Map MARC 505 field content to abstract, as MODS element tableOfContents is not implemented in the DAMS.

The displayLabel attribute always has value "Description".

520
abstract

Map MARC 520 field content to abstract, as MODS element tableOfContents is not implemented in the DAMS.

The displayLabel attribute always has value "Description".

880
abstract

Map MARC 880 field content to abstract, as MODS element tableOfContents is not implemented in the DAMS.

The displayLabel attribute always has value "Description".

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
abstract
mods_abstractmods_abstract

Multiple description texts will be concatenated for display on the Collections portal. The different entries are separated by the pipe symbol (|).