glam/schemas/20251121/linkml/modules/classes/DeploymentEvent.yaml
kempersc f7bf1cc5ae Refactor schema slots and classes
- Deleted obsolete slot definitions: statement_summary, statement_text, statement_type, status_name, supersede_articles, supersede_condition, supersede_name, temporal_dynamics, total_amount, typical_contents, use_cases, was_acquired_through, was_fetched_at, was_retrieved_at.
- Updated existing slot definitions for states_or_stated to enhance clarity and structure.
- Introduced new classes: Article, ConditionofAccess, FinancialStatementType, MaximumQuantity, Series, Summary, Type, and their respective slots to improve schema organization and usability.
- Added new slots: changes_or_changed_through, has_or_had_condition_of_access, has_or_had_heritage_type, is_or_was_part_of_series, is_or_was_retrieved_at, maximum_of_maximum to capture additional metadata and relationships.
2026-01-30 00:29:31 +01:00

149 lines
5.2 KiB
YAML

id: https://nde.nl/ontology/hc/class/DeploymentEvent
name: deployment_event_class
title: DeploymentEvent Class
prefixes:
linkml: https://w3id.org/linkml/
hc: https://nde.nl/ontology/hc/
prov: http://www.w3.org/ns/prov#
schema: http://schema.org/
crm: http://www.cidoc-crm.org/cidoc-crm/
default_prefix: hc
imports:
- linkml:types
- ./TimeSpan
- ./Custodian
- ../slots/temporal_extent
- ../slots/has_or_had_description
- ./Description
- ../slots/refers_to_custodian
- ../slots/specificity_annotation
- ../slots/has_or_had_score
- ./SpecificityAnnotation
- ./TemplateSpecificityScore
- ./TemplateSpecificityType
- ./TemplateSpecificityTypes
classes:
DeploymentEvent:
class_uri: prov:Activity
description: |
Event representing the deployment of a software system (CMS, platform) at an institution.
**Purpose**:
DeploymentEvent captures the full context of a software deployment:
- WHEN: Via temporal_extent (TimeSpan with fuzzy boundaries)
- WHERE: Via refers_to_custodian (target institution)
- WHAT: Linked from CollectionManagementSystem.is_or_was_deployed_at
- WHY: Via description (deployment rationale, notes)
**MIGRATED FROM**: `deployment_date` slot
Replaces simple date with structured event that:
- Supports fuzzy temporal bounds (TimeSpan)
- Tracks deployment at specific custodians
- Enables multiple deployment events per system
- Captures deployment context and rationale
**Ontological Alignment**:
- **Primary**: `prov:Activity` - PROV-O activity
- **Close**: `crm:E5_Event` - CIDOC-CRM event
- **Related**: `schema:Action` - Schema.org action
**Relationship to CollectionManagementSystem**:
```
CollectionManagementSystem
└── is_or_was_deployed_at → DeploymentEvent[]
├── temporal_extent → TimeSpan
├── refers_to_custodian → Custodian
└── description → Description
```
exact_mappings:
- prov:Activity
close_mappings:
- crm:E5_Event
- schema:Action
related_mappings:
- schema:InstallAction
slots:
- temporal_extent
- refers_to_custodian
- has_or_had_description
- specificity_annotation
- has_or_had_score
slot_usage:
temporal_extent:
description: |
When this deployment occurred.
Uses TimeSpan for fuzzy temporal bounds:
- Precise: Set all four bounds to same date
- Approximate: Use begin_of_the_begin/end_of_the_end range
range: TimeSpan
inlined: true
required: true
examples:
- value:
begin_of_the_begin: "2015-06-01"
end_of_the_end: "2015-06-01"
description: Precise deployment date (June 1, 2015)
- value:
begin_of_the_begin: "2015-01-01"
end_of_the_end: "2015-06-30"
description: Approximate deployment (first half of 2015)
refers_to_custodian:
description: |
The institution where this deployment occurred.
range: Custodian
required: false
examples:
- value: https://nde.nl/ontology/hc/nl-nh-ams-m-rm-q190804
description: Deployment at Rijksmuseum
has_or_had_description:
description: |
Notes about this deployment event (rationale, context, issues).
range: Description
inlined: true
required: false
examples:
- value:
has_or_had_text: "Migrated from legacy system to Adlib v7.4. Data migration completed in phases over Q2 2015."
description: Deployment notes
annotations:
custodian_types: '["*"]'
custodian_types_rationale: Deployment events applicable to all custodian types.
custodian_types_primary: null
specificity_score: 0.7
specificity_rationale: Specific to software deployment tracking.
comments:
- "MIGRATED from deployment_date per slot_fixes.yaml (Rule 53)"
- "PROV-O Activity for deployment tracking"
- "Enables multiple deployments per CMS (upgrades, re-deployments)"
- "TimeSpan allows fuzzy temporal bounds for uncertain deployment dates"
examples:
- value:
temporal_extent:
begin_of_the_begin: "2015-06-01"
end_of_the_end: "2015-06-01"
refers_to_custodian: https://nde.nl/ontology/hc/nl-nh-ams-m-rm-q190804
has_or_had_description:
has_or_had_text: "Initial deployment of Adlib CMS at Rijksmuseum"
description: Rijksmuseum Adlib deployment event
- value:
temporal_extent:
begin_of_the_begin: "2020-01-01"
end_of_the_end: "2020-03-31"
refers_to_custodian: https://nde.nl/ontology/hc/nl-zh-hag-a-na
has_or_had_description:
has_or_had_text: "Upgrade to MAIS-Flexis v3.0. Migration included archival descriptions from 2010-2019."
description: National Archives MAIS upgrade event