glam/schemas/20251121/linkml/modules/classes/DeploymentEvent.yaml
2026-02-08 19:22:13 +01:00

123 lines
No EOL
4.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
- ../slots/20260202_matang/has_description
- ../slots/20260202_matang/has_score
- ../slots/20260202_matang/new/refers_to_custodian
- ../slots/20260202_matang/temporal_extent
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.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
└── 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_description
- has_score
slot_usage:
temporal_extent:
range: TimeSpan
inlined: true
required: true
examples:
- value:
begin_of_the_begin: "2015-06-01"
end_of_the_end: "2015-06-01"
- value:
begin_of_the_begin: "2015-01-01"
end_of_the_end: "2015-06-30"
refers_to_custodian:
range: Custodian
required: false
examples:
- value: https://nde.nl/ontology/hc/nl-nh-ams-m-rm-q190804
has_description:
# range: string
inlined: false # Fixed invalid inline for primitive type
required: false
examples:
- value:
has_text: "Migrated from legacy system to Adlib v7.4. Data migration completed in phases over Q2 2015."
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_description:
has_text: "Initial deployment of Adlib CMS at Rijksmuseum"
- 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_description:
has_text: "Upgrade to MAIS-Flexis v3.0. Migration included archival descriptions from 2010-2019."