Schema Migration Fixes: - Fix YAML import indentation in ~650 slot files (linkml:types and enum imports) - Rename slot reference: has_or_had_holds_record_set_type → hold_or_held_record_set_type (70+ archive class files, main schema, manifest.json) - Fix ProvenanceBlock.yaml: remove invalid any_of range, use string with multivalued - Fix has_or_had_provenance.yaml: remove nested template_specificity from annotations Validation Status: - 0 errors (was multiple import/reference errors) - 30 warnings (missing descriptions on inline slots, intentional SCREAMING_CASE names) Files changed: ~3,850 (slots, classes, main schema, manifest)
40 lines
911 B
YAML
40 lines
911 B
YAML
id: https://nde.nl/ontology/hc/slot/powers_platform
|
|
name: powers_platform_slot
|
|
title: Powers Platform Slot
|
|
prefixes:
|
|
linkml: https://w3id.org/linkml/
|
|
hc: https://nde.nl/ontology/hc/
|
|
imports:
|
|
- linkml:types
|
|
- ../classes/DigitalPlatform
|
|
default_prefix: hc
|
|
slots:
|
|
powers_platform:
|
|
description: 'DigitalPlatform(s) powered by this CMS deployment.
|
|
|
|
|
|
CIDOC-CRM: P33_used_specific_technique - the CMS is the technique/procedure
|
|
|
|
used to power the digital platform.
|
|
|
|
|
|
**BIDIRECTIONAL RELATIONSHIP**:
|
|
|
|
- Forward: CollectionManagementSystem → DigitalPlatform (powers_platform)
|
|
|
|
- Reverse: DigitalPlatform → CollectionManagementSystem (powered_by_cms)
|
|
|
|
|
|
One CMS deployment may power multiple platforms:
|
|
|
|
- Public website
|
|
|
|
- Staff intranet
|
|
|
|
- Mobile app backend
|
|
|
|
- API service
|
|
|
|
'
|
|
range: DigitalPlatform
|
|
slot_uri: hc:powersPlatform
|