# ConditionState - State/condition at a point in time # Created 2026-01-22 per slot_fixes.yaml revision for condition_after/condition_before (Rule 53) # # CIDOC-CRM: E3 Condition State - describes the physical condition of objects # Used with final_of_the_final (post-event) and initial_of_the_initial (pre-event) # id: https://nde.nl/ontology/hc/class/ConditionState name: ConditionState title: Condition State prefixes: linkml: https://w3id.org/linkml/ hc: https://nde.nl/ontology/hc/ crm: http://www.cidoc-crm.org/cidoc-crm/ schema: http://schema.org/ imports: - linkml:types - ./ConditionType - ./ConditionTypes - ../slots/has_or_had_type - ../slots/has_or_had_description - ./Description default_prefix: hc classes: ConditionState: class_uri: crm:E3_Condition_State description: | The physical or preservation state of an object at a specific point in time. Maps to CIDOC-CRM E3 Condition State, which describes "the physical condition of an object at a specific time, typically relevant for conservation." **USE CASES**: 1. **Conservation Records**: Before/after treatment states - `initial_of_the_initial`: Pre-treatment condition - `final_of_the_final`: Post-treatment condition 2. **Condition Assessments**: Periodic condition surveys 3. **Loan Records**: Condition at departure/return **RELATION TO ConditionType**: - Uses `has_or_had_type` with `ConditionType` subclasses for classification - E.g., ExcellentCondition, GoodCondition, FairCondition, PoorCondition, CriticalCondition **TEMPORAL SEMANTICS**: - Each ConditionState instance represents a snapshot at a moment in time - Multiple states can be tracked for the same object over time **Migration (2026-01-22)**: - `condition_after` → `final_of_the_final` + `ConditionState` - `condition_before` → `initial_of_the_initial` + `ConditionState` - Per slot_fixes.yaml (Rule 53) exact_mappings: - crm:E3_Condition_State close_mappings: - schema:OfferItemCondition slots: - has_or_had_type - has_or_had_description slot_usage: has_or_had_type: range: ConditionType description: | Classification of this condition state (e.g., ExcellentCondition, GoodCondition). Uses ConditionType taxonomy from ConditionTypes.yaml. examples: - value: GoodCondition description: Object in good physical condition - value: PoorCondition description: Object requires conservation attention has_or_had_description: range: Description description: | Detailed textual description of the condition state. May include observations, measurements, damage descriptions. examples: - value: description_text: "Minor foxing on page margins, binding intact" description: Book condition description attributes: state_date: description: Date when this condition state was observed/recorded range: date assessed_by: description: Person or entity who assessed the condition range: string annotations: custodian_types: '["M", "A", "L", "R"]' custodian_types_rationale: "Primarily used by museums, archives, libraries, research centers with physical collections." specificity_score: 0.6 specificity_rationale: "Moderately specific - used in conservation and preservation contexts." examples: - value: has_or_had_type: GoodCondition has_or_had_description: description_text: "Object stabilized after treatment. Surface cleaned, minor losses filled." state_date: "2026-01-15" assessed_by: "Conservation Department" description: Post-conservation condition state - value: has_or_had_type: PoorCondition has_or_had_description: description_text: "Significant foxing, loose binding, torn pages 45-48." state_date: "2025-12-01" assessed_by: "Jane Smith, Conservator" description: Pre-treatment condition state - value: has_or_had_type: FairCondition has_or_had_description: description_text: "Minor wear consistent with age, no active deterioration." state_date: "2026-01-20" description: Routine condition assessment