Contents

Definition

Type of event in the history of the object

Other possible database element names

Type of event

Text/URI

Text and/or URI

Repeatable

No, only one Event type per event

Obligation level

Mandatory

Recording notes

For specifying the event type, the use of the event type vocabulary from the LIDO terminology is recommended. A German and an English preferred term as well as a persistent URI are provided for each event type.

(lightbulb)CARE: If nothing more is known about the provenance and date of an object beyond its access to the collection, an appropriate event type should be selected. Gaps in knowledge of the object's history should always be disclosed (e. g. by entering "not documented" or "not known to us" in the "person/entity", "date", "place" data elements). Uncertainties or attributions, e.g. from the surviving collection entry documentation, should be contextualised in a separate data element "Event description" (in LIDO: <lido:eventDescriptionSet>/<descriptiveNoteValue>).

Terminology recommendations

LIDO terminology (for eventType)

Examples

Expression in LIDO v1.0

<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:event>
     </lido:eventSet>
 </lido:eventWrap>

Expression in LIDO v1.1

<lido:eventWrap>
	<lido:eventSet>
		<lido:event>
			<lido:eventType>
				<skos:Concept rdf:about="http://terminology.lido-schema.org/lido00007">
					<skos:prefLabel xml:lang="de">Herstellung</skos:prefLabel>
					<skos:prefLabel xml:lang="en">Production</skos:prefLabel>
				</skos:Concept>
			</lido:eventType>
		</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 applicableNot applicableNot applicable

German Digital Library LIDO application profile (DDB-LIDO)

<eventType> / <conceptID>

Text (controlled vocabulary) and URINo

Conditionally mandatory

Recommended

Mandatory if <eventWrap> exists.

The event type cannot be repeated within an event. Any number of events can be assigned to an object.

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 a “relevant” person (with details of their role) and specifying a “time of origin”.

Depending on the context, this is “production”, “find” or “collecting”.

DFG Practical Guidelines on Digitisation: LIDO core metadata

Event

lido:eventSet/lido:event/lido:eventType

Text (controlled vocabulary) and URINoMandatory if available
Europeana Data Model (EDM)

../edm:Event/edm:hasType

Text and/or URIYesNot mandatoryEuropeana not (yet) uses <edm:Event>. This report recommends the introduction of <edm:Event>.
EODEM application profile

Object Production Group

/lido:eventType/lido:conceptID

/lido:eventType/lido:term

Text (controlled vocabulary) and/or URI

No

Mandatory

EODEM includes a production event (Object Production Group).

digiCULT

(Data element name is determined by the event type)

Text (controlled vocabulary) and URINoRecommended
museum-digital(Data element name is determined by the event type)Text (controlled vocabulary) and URINoRecommended

Museum-digital database provides its own vocabulary for event types: https://event-types.museum-digital.org/.

ID data element

mds0009

  • No labels