Date (Recommended)
Date value as supplied by data provider(e.g. 1940-02-20; 1940-02; 1940; February 20, 1940)
| Property | Value |
|---|---|
| Label | Date |
| DPLA Property | dc:date |
| Description | Date value as supplied by data provider |
| Example | 1940-02-20; 1940-02; 1940; February 20, 1940 |
| Repeatable | Yes |
| Controlled Vocab / Syntax | ISO 8601 (W3CDTF) |
| DC 1.1 Mapping | dc:date |
| MARC Mapping | 260 subfield c (Date of publication, distribution, etc.) or subfield g (Date of manufacture); 264 subfield c |
| Notes | Date may be used to express temporal information at any level of granularity. Recommended best practice is to use an encoding scheme. Date refinements are generally useful in situations where more than one date is needed, and the difference between the dates may be important to users. |
| 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. |