Abstract

REPEATABLE

MODS Element name: <note>

Short definition: General textual information relating to a resource.

Input guidelines: Select one of the pre-specified note types from the dropdown field. 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).
  
• UTL GeoData ID (utlGeoDataID): Enter GeoData ID for content that might also be ingested into the GeoData portal. See detailed instructions on adding map content.

Definition

General textual information relating to a resource.

DAMS input form fields

Note(s)

MODS Element description

Element <note>

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

Guidelines for use

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.

Attributes

Subelements

No subelements for <note>.

XML Examples

<note type="condition">Records are heavily foxed</note>

<note type="date captured">1998-08-17</note>

<note type="general">The digitization of this asset was funded by the International Association of Xylophages.</note>

<note type="merged">merged from 3 partial scans</note>

<note type="origin">Beinecke Library copy inscribed by Langston Hughes on t.p.: "Especially for Louise Bennett with admiration, Sincerely, Langston, New York, Oct. 8, 1954"</note>

<note type="utlGeoDataID">archiveorcollection__subcollection__seriesname_seriesid__scale__oclc__datasetname</note>

Mappings

Dublin Core