Definition
Element set for describing an event in the history of the object
Yes, the element set is repeatable.
Mandatory
Events in object history can provide information about the production, creation, discovery, etc. of an object. An event provides information about what happened (event type), who was involved (person/entity), where (place) and when (date) it took place. Each event must have at least one "who", "where" or "when". At least one event in the history of the object must be described. If no such information is available for an object, at least one period of time during which the item was created or entered the collection should be given to form an event. Any number of events can be given for each object.
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/corporate body”, “Date”, “Place”). Uncertainties or attributions that originate, for example, from the surviving collection entry documentation should be contextualized in a separate data element “Event description” (in LIDO: <lido:eventDescriptionSet>/<descriptiveNoteValue>).
<lido:eventWrap>
<lido:eventSet>
<lido:event>
<lido:eventType>
<lido:conceptID lido:type="http://terminology.lido-schema.org/lido00099">http://terminology.lido-schema.org/lido00007</lido:conceptID>
<lido:term xml:lang="de">Herstellung</lido:term>
<lido:term xml:lang="en">Production</lido:term>
</lido:eventType>
<lido:eventActor>
<lido:actorInRole>
<lido:actor>
<lido:actorID lido:type="http://terminology.lido-schema.org/lido00099">https://d-nb.info/gnd/24495-8</lido:actorID>
<lido:nameActorSet>
<lido:appellationValue>Nixdorf Computer AG</lido:appellationValue>
</lido:nameActorSet>
</lido:actor>
</lido:actorInRole>
</lido:eventActor>
<lido:eventDate>
<lido:date>
<lido:earliestDate>1983</lido:earliestDate>
<lido:latestDate>1983</lido:latestDate>
</lido:date>
</lido:eventDate>
<lido:eventPlace>
<lido:place>
<lido:placeID lido:type="http://terminology.lido-schema.org/lido00099">https://sws.geonames.org/2855745</lido:placeID>
<lido:namePlaceSet>
<lido:appellationValue>Paderborn</lido:appellationValue>
</lido:namePlaceSet>
</lido:place>
</lido:eventPlace>
</lido:event>
</lido:eventSet>
</lido:eventWrap> |
Standard | Element name | Text/URI | Repeatable | Obligation level | Comment |
|---|---|---|---|---|---|
German Digital Library: Requirements for data provided | (No match) | Not applicable | Not applicable | Not applicable | |
| Not applicable | Ja (<eventSet>) | Conditionally mandatory Recommended | Mandatory if sub-elements exist. | ||
| DFG Basic Data Record | (No match, see comment) | Not applicable | Not applicable | Recommended (see comment) | The German Research Foundation recommends documenting a central “relevant” event by specifying a location, naming “relevant” persons (with details of their role) and specifying a “time of origin”. |
| DFG Practical Guidelines on Digitisation: LIDO core metadata | Event lido:eventSet/lido:event | Not applicable | Yes | Mandatory if available | |
| Europeana Data Model (EDM) | (<edm:Event>) | Not applicable | Yes | Not mandatory | Europeana not (yet) uses <edm:Event>. This report recommends the introduction of <edm:Event>. |
| EODEM application profile | Object Production Group /lido:eventWrap/lido:eventSet/lido:event | Not applicable | No | Mandatory | EODEM includes a production event (Object Production Group). |
| digiCULT | Ereignis [eng.: Event] | Not applicable | Yes | Recommended | |
| museum-digital | Event | Not applicable | No | Recommended |