Responsible person

Mandatory event element

The Responsible person element is one of the elements that must be documented for all event records. For this reason, the field appears in several sections.

Section: Condition assessment

Section: Examination

Section: Sampling

Section: Conservation concept

Section: Risk assessment

---

Terminology

info

In order to make the different subject contexts explicit in the names of the metadata elements, the schema assigns a unique identifier to each person involved in their respective roles.

URIs of the Conservation Metadata Terminology:

Responsible person (condition assessment): https://www.w3id.org/conservation/terms/metadata/HRO94F

Examining person: https://www.w3id.org/conservation/terms/metadata/G7F25F

Sampling person: https://www.w3id.org/conservation/terms/metadata/C8CG15

Responsible person (conservation intervention): https://www.w3id.org/conservation/terms/metadata/C79561

Responsible person (risk assessment): https://www.w3id.org/conservation/terms/metadata/CCCC7G

Possible alternative field names in database systems:

• Responsible conservator
• Person responsible for implementation
• Responsibility
• Carried out by

Definition

info

Identification of the person who carried out the relevant action or who is responsible for it.

---

Modelling

Level of obligation

Mandatory

The Responsible Person element is mandatory, as without this information, the traceability and accountability of the relevant action cannot be guaranteed. In most cases, the quality of the results and their documentation depends directly on the expertise and experience of the person carrying out the work. Providing this information makes it possible to get in touch in the event of queries or ambiguities and to validate the assessment.

---

Field value

Text / URI

The data value for this element should be recorded in a structured and machine-readable format. First names and surnames can be entered in a free-text field or, ideally, selected from a controlled list of relevant colleagues; in addition, a machine-readable identifier (e.g. , , ISNI) can also be stored. This enables unambiguous identification and improves interoperability across different databases and systems.

---

Repeatable

Nein

For each event, exactly one person must be named as the person primarily responsible; therefore, this element cannot be repeated. Additional participants could be added via an optional field.

---

Distinguishing between internal recording and public dissemination

For the purposes of internal documentation, the person responsible should be recorded by their full name to ensure that responsibilities are clearly defined, particularly in larger organisations with many conservators. When publishing data on online portals and infrastructures, a decision must be made on a case-by-case basis as to whether the person can or wishes to be named in the context of academic authorship. If, for reasons of data protection, real names are not to be published, the parent organisation may be listed as responsible in this instance. For documentation purposes, it is therefore advisable to record both pieces of information as standard. This distinction ensures that responsibility is clearly documented internally, whilst the privacy of those involved remains protected externally.

Example

• Responsible person (internally): Kristina Fischer

• Responsible person (externally): LEIZA, Conservation Lab

---

Equivalents in other schemas

Schema	Element name	Level of obligation
MDS v1.1	Person/Körperschaft	Conditional mandatory
Spectrum 5.1	Procedure manager & Condition check/assessor & Conservation authoriser & Person information	not specified