...
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>).
...
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