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) general (default): Input notes intended for public display on front end and not accommodated by other elements or note types. Template note available for assets where only metadata is published to the Collections Portal and for redacted assets. Notes not displayed on the Collections portal (internal)
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"] |
Subelements
No subelements for <note>.
XML Examples
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
The following specific guidelines apply for the DAMS:
Dublin Core field | Mapping condition | MODS element | Notes |
---|---|---|---|
dc:description | MODS to DC | note | Currently all information from <note> elements is mapped to dc:description, including note types intended for internal use. |
MARC 21
Map notes from MARC 21 fields 5XX to <note> elements with an appropriate type from the set of types available in the DAMS (citation, condition, date captured, date issued, date other, description, file path, general, merged, origin, scale, utlGeoDataID). Cf. the following examples:MARC 21 field Mapping condition MODS element Notes 033 MARC indicator 2 has value 0 note[@type="date captured"] Approximate mapping. 500 note[@type="general"] Approximate mapping. Depending on the type of material described by the catalog record, other note types might be appropriate (e.g. when dealing with material cataloged according to DCRM, copy-specific descriptive information might be recorded in MARC field 500). 507 note[@type="scale"] 524 note[@type="citation"] Approximate mapping. 541 note[@type="origin"] Map together with information from MARC field 561, if available. 561 note[@type="origin"] Map together with information from MARC field 541, if available.
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 |
---|---|---|---|---|
note[@type="general"] | mods_note_type_general | mods_note_type_general | ||
note[@type="citation"] | mods_note_type_citation | mods_note_type_citation | ||
note[@type="condition"] | mods_note_type_condition | mods_note_type_condition | ||
note[@type="date captured"] | mods_note_type_date_captured | mods_note_type_date_captured | ||
note[@type="other date"] | mods_note_type_other_date | mods_note_type_other_date | ||
note[@type="origin"] | mods_note_type_origin | mods_note_type_origin | ||
note[@type="scale"] | mods_note_type_scale | mods_note_type_scale |