Summary of Requirements for <subject>
The DLF/Aquifer Implementation Guidelines for Shareable MODS Records require, when applicable, the use of at least one <subject> element in a record. Values for <subject> indicate what content is found within or represented by the work, and typically answer such questions as who, what, where, and when. These guidelines highly recommend the use of subject values from a controlled list and the designation of this list in the authority attribute. Parsing subject values into subelements, rather than placing them in <subject><topic> strings, is not required but is highly recommended, when possible. Repeat distinct, multiple subjects in separate <subject> fields. (page 53)
Per the Levels of Adoption Document Level 2: at least one <subject> element is required
Per the Levels of Adoption Document Level 3: More specific <subject> subelements (geographic places, etc.) over <subject>/<topic>
Per the Levels of Adoption Document Level 4: @authority attributes in general
The <subject> page allows you to build detailed subject headings according to the MODS standard.
The Workbook, however, does not check whether the subelements are properly applied.
This is the responsibility of the cataloger.
For guidance on building MODS subject tags, refer to
LOC MODS USERGUIDE.
and to the
DLF Aquifer Guidlines for MODS Shareable Records.
Click on the Add One Subject Block button to add another set of subject input tags.
|