Skip to main content

Condition Description

Section: Condition Assessment


Terminology​

URI in the Conservation Metadata Terminology: https://www.w3id.org/conservation/terms/metadata/AC1786

Possible alternative field names in database systems:

  • Condition report
  • Condition summary
  • Condition documentation
  • Object condition
  • Condition findings

Definition​

info

This element is a parent element that groups together several related sub-elements. It does not record a data value itself. Together, the sub-elements form the textual and structured condition documentation, including the key findings. These comprise observed condition characteristics and types of damage as well as relevant environmental conditions that may have affected the condition.


Modelling​

Obligation​

Mandatory

This element is mandatory, as every condition assessment must include a description of the object's condition. Which sub-elements are mandatory is specified for each individual sub-element.


Field Value​

No data value

This element serves solely to group its sub-elements and does not contain any data values of its own. It has its own URI so that it can be referenced unambiguously.


Repeatable​

No

Each Condition Assessment section contains exactly one condition description. It describes the condition of the object at the point in time to which the condition assessment refers. For each additional point in time, a separate Condition Assessment section is created.


Sub-elements​

ElementObligation
Physical ConditionMandatory
Damage PhenomenaMandatory
Previous Environmental ConditionsRecommended
Conservation HistoryRecommended

Notes​

note

The condition description brings together all information on the condition of an object that is established during a condition assessment. It always refers to the point in time of that condition assessment, which is clearly identified by the element Assessment Date.

Grouping the information in this way keeps the condition information together and allows it to be assigned unambiguously to a point in time. This makes the documentation consistent and traceable, and allows it to be compared directly across repeated condition assessments.

The sub-elements combine a detailed free-text description with recommended structured information. This keeps the documentation comprehensible and sufficiently detailed for human readers, while also making it machine-readable for digital systems. Depending on the discipline, the condition description can and should be extended with further elements of specific relevance.


Equivalents in Other Schemas​

SchemaElement nameObligation
MDS v1.1No equivalentNot applicable
Spectrum 5.1Outcome of condition check/technical assessmentNot applicable