Includes but is not limited to: an abstract, a table of contents, or a free-text account of described resource (e.g. Bill Moss posed with Tina Turner and Eddie Castleberry, the program director of WVKO.)
|Description||Includes but is not limited to: an abstract, a table of contents, or a free-text account of described resource|
|Example||Bill Moss posed with Tina Turner and Eddie Castleberry, the program director of WVKO.|
|DC 1.1 Mapping||dc:description|
|MARC Mapping||500-599, except 506, 530, 540, 546; 300 if relevant/appropriate|
|Notes||Since the Description field is a potentially rich source of indexable terms, care should be taken to provide this element when possible. Best practice recommendation for this element is to use full sentences, as description is often used to present information to users to assist in their selection of appropriate resources from a set of search results.|
|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.|