Note
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.
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.
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)
DAMS form field name | form field type | required | MODS element | Collections Portal display | notes |
|---|---|---|---|---|---|
Note text | text area | no | note | Depending on the note type selected, the following notes will be displayed in the Collections portal:
| |
Note type | dropdown selection
| no | note[@type] (attribute of note) | Notes with the following note types will be displayed in the Collections portal:
Notes with the following note types will not be displayed in the Collections portal:
|
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.
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.
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
Attribute name | Details | XPath syntax examples |
|---|---|---|
type | values:
| note[@type="general"] note[@type="origin"] note[@type="file path"] note[@type="utlGeoDataID"] |