General textual information relating to a resource.

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

Use one of the pre-specified values for the note type attribute. The following note types are currently available:

Notes displayed on the Collections portal (public)

• citation: Input standardized citations that may be valuable for users. Note that Collections portal will automatically generate some citation formats.

• condition: Input statement about the original asset's condition. Apply content standards like RDA, DCRM or DACS to record information about an item's condition.

• date captured: Input capture/recording/digitization dates. Input only the date in structured format YYYY-MM-DD. To record time intervals, 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). If only part of a date is known, enter year and month only (YYYY-MM) or year only (YYYY).

• date other: Input other dates of interest. Input only the date in structured format YYYY-MM-DD. To record time intervals, 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). If only part of a date is known, enter year and month only (YYYY-MM) or year only (YYYY).

• general (default): Input notes intended for public display on front end and not accommodated by other elements or note types.

  Template note text available for assets where only metadata is published to the Collections Portal and for redacted assets: Metadata text templates

• origin: Input details about asset origin/provenance not adequately captured elsewhere. Apply content standards like RDA, DCRM or DACS to record information about origin/provenance.

• scale: Input scale for non-cartographic resources (as opposed to values in Subject-Cartographics fields).

Notes not displayed on the Collections portal (internal)

• description: Input descriptive information not intended/suitable for public display. Enter descriptive information intended for the public in the Description form field.

• date issued: Input publication/dissemination dates. Input only the date in structured format YYYY-MM-DD. To record time intervals, 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). If only part of a date is known, enter year and month only (YYYY-MM) or year only (YYYY).

• file path: Input file reference to aid location of related files in separate storage systems.

  It is best practice to reference the tape vault location of the original presentation grade file ingested into the DAMS.

• merged: Input indication that asset is the result of merging various parts into one (e.g., piecemeal scans of oversize material).

• utlGeoDataID: Enter GeoData ID for content that might also be ingested into the GeoData portal. See detailed instructions on adding map content.

No subelements for <note>.

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

The following specific guidelines apply for the DAMS:

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.