Subject (Recommended)
Topic of described resource(e.g. Dogs; Airplanes; Rhodes, James A. (James Allen), 1909-2001)
Property | Value |
---|---|
Label | Subject |
DPLA Property | dcterms:subject |
Description | Topic of described resource |
Example | Dogs; Airplanes; Rhodes, James A. (James Allen), 1909-2001 |
Refines | dc:subject |
Repeatable | Yes |
Controlled Vocab / Syntax | LCSH ; AAT |
DC 1.1 Mapping | dc:subject |
MARC Mapping | 650, 600, 610, 653 |
Notes | Recommended best practice is to select a value from a controlled vocabulary or formal classification scheme. Select subject keywords from the Title or Description information, or from within a text resource. If the subject of the item is a person or an organization, use the same form of the name as you would if the person or organization were a Creator or Contributor. Use uncoordinated values if possible (or attempt to for new collections), for example: Subject: Soldiers Subject: Ohio Subject: Correspondence instead of Subject: Soldiers -- Ohio -- Correspondence |
Index of Properties | |
---|---|
Label | The unique name used in the Metadata Application Profile. |
Status | Status labels for elements can include Required, Recommended, and Optional. |
Description | Brief description of the element. |
Refines | The Dublin Core metadata field of which the described term is a sub-property. |
Repeatable | ‘YES’ means that a field may be used multiple times in an item record. ‘NO’ means that a field can onlt be used once in an item record. |
Controlled Vocab/Syntax | Recommended vocabulary for element, if available. (For data quality and consistency) |
DC 1.1 Mapping | The Dublin Core element to which the metadata field name maps. |
MARC Mapping | The MARC field to which the Dublin Core metadata is crosswalked. |
Notes | Applicable notes for the element. |
Example | Examples of best practices for the described field. |