Definition
Date (precise date or time period) when the event in the object history occurred
Other possible database element names
Date / Period
Times
Date of production
Date of origin
Text/URI
Text (Date format; ISO 8601 requested)
Repeatable
No
Obligation level
At least one event in the history of the object is mandatory.
In addition to the Event type, each event must have at least one "who", "where" or "when".
Recording notes
Date entries are made in standardized format (preferably ISO 8601).
Time spans are specified in two separate data elements. The first data element contains the earliest possible or known date and the second data element contains the latest possible or known date on which the event in the history of the object occurred.
Date information can also be entered in free text form (for uncertain information, periods/epochs, etc.). This is recorded in a separate data field (in LIDO: <lido:displayDate> for verbal information or <lido:periodName> for periods/epochs respectively).
CARE: Knowledge gaps in the object's history should always be disclosed (e.g. by stating “not documented” or “not known to us” in the data elements “Person/entity”, “Date”, “Location”). Uncertainties or attributions that originate from the surviving documentation of the collection entry, for example, should be contextualized in a separate data element “Event description” (in LIDO: <lido:eventDescriptionSet>/<descriptiveNoteValue>).
Format recommendation
Extended Date/Time Format (EDTF)
Examples
1801/1900
1969-07-21/1969-08-15
-377/-299
1983/1987
1983
1596/1605
Expression in LIDO (v1.0 and v1.1)
<lido:eventWrap> <lido:eventSet> <lido:event> <lido:eventDate> <lido:date> <lido:earliestDate>1983</lido:earliestDate> <lido:latestDate>1983</lido:latestDate> </lido:date> </lido:eventDate> </lido:event> </lido:eventSet> </lido:eventWrap>
Comparison with relevant standards and database models
Standard | Element name | Text/URI | Repeatable | Obligation level | Comment |
|---|---|---|---|---|---|
German Digital Library: Metadata requirements for data provision | (No match) | Not applicable | Not applicable | Not applicable | |
Text | No | Conditionally mandatory | Mandatory if sub-elements exist. | ||
| DFG Basic Data Record | Source Object Time of Origin | Text | Not specified | Recommended | |
| DFG Practical Guidelines on Digitisation: LIDO core metadata | Time period of event <eventDate> | Text | No | Mandatory, if available | The DFG Practical Guidelines on Digitisation require additional date information in text form where such information is available, in which any inaccuracies can be expressed. The LIDO element <eventDate>/<displayDate> is used for this purpose. |
| Europeana Data Model (EDM) | Text and/or URI | Ja | Not mandatory | ||
| EODEM application profile | Earliest Production Date und Latest Production Date /lido:eventDate/lido:date/lido:earliestDate und /lido:latestDate | Text | No | Not mandatory | |
| digiCULT | Datierung (eventDate) [engl.: Date (eventDate)] | Text | No | Recommended | |
| museum-digital | When? | Text | No | Recommended |
ID data element
mds0011