glam/schemas/20251121/linkml/modules/classes/CMS.yaml
kempersc f622450304 Add new slots and update existing ones for heritage ontology
- Introduced new slots for administrative context, CMS categories, detected CMS, product version, co-funding requirements, co-organizers, collection access, collection dates, characteristics, class definitions, Dutch context, example locations, names, notes, and Wikidata IDs.
- Enhanced existing slots such as has_or_had_organizer and offers_or_offered_access to align with RiC-O naming conventions and improve temporal semantics.
- Migrated and restructured descriptions for clarity and consistency across various slots, ensuring alignment with Schema.org and other ontological standards.
- Implemented multivalued and inlined options for several slots to accommodate complex data structures.
- Updated annotations and examples to reflect the latest usage scenarios and best practices in the heritage sector.
2026-01-19 16:05:32 +01:00

142 lines
4.6 KiB
YAML

id: https://nde.nl/ontology/hc/class/CMS
name: cms_class
title: CMS Class
prefixes:
linkml: https://w3id.org/linkml/
hc: https://nde.nl/ontology/hc/
schema: http://schema.org/
prov: http://www.w3.org/ns/prov#
doap: http://usefulinc.com/ns/doap#
imports:
- linkml:types
- ../slots/has_or_had_label
- ../slots/has_or_had_version
- ../slots/has_or_had_type
- ./CMSType
default_prefix: hc
classes:
CMS:
class_uri: schema:SoftwareApplication
description: |
A detected Content Management System (CMS) on a digital platform.
**Purpose**: Represents a CMS instance detected through automated discovery
or manual identification. Used when a platform is_or_was_based_on a CMS.
**Distinction from CollectionManagementSystem**:
- **CMS**: Lightweight detection record (what CMS was found)
- **CollectionManagementSystem**: Full institutional CMS deployment profile
(configuration, collections managed, custodian relationships)
**Detection Methods** (from original cms_detected documentation):
- HTTP response headers (X-Powered-By, Server)
- HTML meta tags (generator)
- URL patterns (e.g., /providence/, /omeka/)
- JavaScript libraries or framework signatures
- Admin panel detection
**Use Cases**:
1. "What CMS powers this auxiliary platform?" → Check is_or_was_based_on
2. Technical survey: Identify platforms by CMS type
3. Migration planning: Prioritize platforms by CMS technology
**Example**:
```yaml
AuxiliaryDigitalPlatform:
platform_name: Heritage Blog
is_or_was_based_on:
- cms_name: WordPress
cms_version: "6.4.2"
cms_type: CustomCMS
detected_at: "2026-01-19T12:00:00Z"
detection_method: HTTP_HEADER
```
**Migration Note**: Created 2026-01-19 per slot_fixes.yaml (Rule 53).
Supports migration from boolean cms_detected to structured CMS reference.
exact_mappings:
- schema:SoftwareApplication
close_mappings:
- doap:Project
slots:
- cms_name
- has_or_had_version
- has_or_had_type
- detected_at
- detection_method
slot_usage:
cms_name:
description: Name of the detected CMS (e.g., WordPress, Drupal, Omeka)
range: string
required: true
examples:
- value: WordPress
description: WordPress CMS
- value: Omeka S
description: Omeka S digital collections platform
- value: CollectiveAccess
description: CollectiveAccess museum CMS
has_or_had_version:
description: Detected version of the CMS
range: string
required: false
examples:
- value: "6.4.2"
description: WordPress version
- value: "4.0.1"
description: Omeka S version
has_or_had_type:
description: CMS type classification (maps to CMSType hierarchy)
range: CMSType
required: false
examples:
- value: MuseumCMS
description: Museum-focused CMS
- value: ArchiveCMS
description: Archive-focused CMS
detected_at:
description: ISO 8601 timestamp when CMS was detected
range: datetime
required: false
examples:
- value: "2026-01-19T12:00:00Z"
description: Detection timestamp
detection_method:
description: Method used to detect the CMS
range: string
required: false
examples:
- value: HTTP_HEADER
description: Detected via X-Powered-By header
- value: META_TAG
description: Detected via HTML generator meta tag
- value: URL_PATTERN
description: Detected via URL structure
- value: MANUAL
description: Manually identified
annotations:
custodian_types: '["D"]'
custodian_types_rationale: Digital platforms (D) are the primary users of CMS detection
specificity_score: 0.70
specificity_rationale: Specific to digital platform CMS detection context
slots:
cms_name:
slot_uri: schema:name
description: Name of the Content Management System
range: string
exact_mappings:
- schema:name
- doap:name
detected_at:
slot_uri: prov:generatedAtTime
description: Timestamp when the CMS was detected
range: datetime
exact_mappings:
- prov:generatedAtTime
detection_method:
slot_uri: prov:wasGeneratedBy
description: Method used to detect the CMS (HTTP_HEADER, META_TAG, URL_PATTERN, MANUAL)
range: string