kempersc/glam
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
glam/frontend/public/schemas/20251121/linkml/modules/classes/Activity.yaml
kempersc 9342919c79 Add archived slot definitions for various attributes 
- Introduced dual_class_role, emic_name, employer_linkedin_url, employer_name, employment_dates_raw, employment_end_date, employment_start_date, end_date, end_seconds, end_time, ended_at_time, endowment_draw, engagement_rate, enriched_date, enrichment_metadata_whatsapp, enrichment_method_whatsapp, exhibition_timespan, has_timespan, policy_effective_from, policy_effective_to, start_date, can_or_could_be_retrieved_from, documents_or_documented, has_or_had_contributor, has_or_had_drawer, has_or_had_email, has_or_had_endowment_draw, has_or_had_engagement_metric, has_or_had_metadata, has_or_had_summary, is_or_was_employed_by, and is_or_was_expired_at slots.
- Each slot includes detailed descriptions, ranges, and mappings to ensure compliance with ontology standards.
2026-01-26 17:32:24 +01:00

280 lines
10 KiB
YAML
Raw Blame History

# Activity - Base class for all heritage domain activities
#
# This is the main Activity class that uses generic slots for:
# - Identifier (has_activity_identifier)
# - Type (has_or_had_activity_type → ActivityType)
# - Description (has_activity_description)
# - Label (has_activity_name)
# - Timespan (has_timespan → TimeSpan)
# - Succession (is_or_was_succeeded_by, preceding_activity)
#
# Generation date: 2026-01-13
# Rule compliance: 38, 39, 42, 43, 48
id: https://nde.nl/ontology/hc/class/Activity
name: Activity
title: Activity Class
prefixes:
linkml: https://w3id.org/linkml/
hc: https://nde.nl/ontology/hc/
crm: http://www.cidoc-crm.org/cidoc-crm/
rico: https://www.ica.org/standards/RiC/ontology#
prov: http://www.w3.org/ns/prov#
schema: http://schema.org/
dcterms: http://purl.org/dc/terms/
aat: http://vocab.getty.edu/aat/
skos: http://www.w3.org/2004/02/skos/core#
default_prefix: hc
imports:
- linkml:types
- ../metadata
- ./TimeSpan
- ./ActivityType
- ./ActivityTypes
- ../slots/has_activity_identifier
- ../slots/has_activity_name
- ../slots/has_activity_description
- ../slots/has_or_had_activity_type
# MIGRATED 2026-01-26: has_timespan/start_date/end_date → temporal_extent (Rule 53)
- ../slots/temporal_extent
- ../slots/is_or_was_succeeded_by
- ../slots/preceding_activity
- ../slots/status
- ../slots/note
- ../slots/specificity_annotation
- ../slots/has_or_had_score # was: template_specificity - migrated per Rule 53 (2026-01-17)
- ./SpecificityAnnotation
- ./TemplateSpecificityScore # was: TemplateSpecificityScores - migrated per Rule 53 (2026-01-17)
- ./TemplateSpecificityType
- ./TemplateSpecificityTypes
classes:
Activity:
class_uri: prov:Activity
description: |
Base class for activities performed by heritage custodians.
**DEFINITION**:
An Activity represents a discrete or ongoing action undertaken by a heritage
custodian. This is the base class for all activity instances in the ontology.
**ONTOLOGICAL ALIGNMENT**:
| Ontology | Class | Use Case |
|----------|-------|----------|
| PROV-O | prov:Activity | Primary - provenance tracking |
| CIDOC-CRM | crm:E7_Activity | Cultural heritage domain |
| RiC-O | rico:Activity | Archival activities |
| Schema.org | schema:Action | Web semantics |
**KEY RELATIONSHIPS**:
```
Activity
│
├── has_or_had_activity_type → ActivityType (classification)
│ └── CurationActivityType, ConservationActivityType, etc.
│
├── has_timespan → TimeSpan (temporal extent)
│ └── start_date, end_date, fuzzy bounds
│
├── is_or_was_succeeded_by → Activity (succession)
│
└── preceding_activity → Activity (inverse succession)
```
**SPECIALIZATION**:
This base class is extended by domain-specific activity classes:
- CurationActivity - Collection management (existing, to be refactored)
- ConservationActivity - Preservation work
- ExhibitionActivity - Exhibition planning and execution
- DigitizationActivity - Digital transformation projects
**PROVENANCE (PROV-O)**:
Activities generate provenance information:
- `prov:Activity` - The activity itself
- `prov:wasAssociatedWith` - Responsible agents
- `prov:used` - Entities processed
- `prov:generated` - Entities created
- `prov:atTime` - Temporal extent
exact_mappings:
- prov:Activity
close_mappings:
- crm:E7_Activity
- rico:Activity
- schema:Action
related_mappings:
- aat:300054277 # activities (functions)
slots:
- has_activity_identifier
- has_activity_name
- has_activity_description
- has_or_had_activity_type
# MIGRATED 2026-01-26: has_timespan/start_date/end_date → temporal_extent
- temporal_extent
- is_or_was_succeeded_by
- preceding_activity
- status
- note
- specificity_annotation
- has_or_had_score # was: template_specificity - migrated per Rule 53 (2026-01-17)
slot_usage:
has_activity_identifier:
range: uriorcurie
required: true
identifier: true
description: |
Unique identifier for this activity instance.
Format: URI following NDE Heritage Custodian ontology conventions.
Pattern: `https://nde.nl/ontology/hc/activity/{custodian-slug}-{type}-{year}-{sequence}`
examples:
- value: https://nde.nl/ontology/hc/activity/rijksmuseum-inventory-2025-001
description: "2025 inventory at Rijksmuseum"
- value: https://nde.nl/ontology/hc/activity/nationaal-archief-digitization-voc-2024
description: "VOC digitization project at Nationaal Archief"
has_activity_name:
range: string
required: true
description: Human-readable name for this activity.
examples:
- value: "2025 Annual Collection Inventory"
description: "Recurring annual inventory"
- value: "VOC Archives Digitization Project Phase 2"
description: "Multi-year digitization project"
has_activity_description:
range: string
required: false
description: Detailed description of the activity scope and objectives.
examples:
- value: |
Annual physical inventory of the Dutch Masters collection,
covering approximately 450 paintings. Spot-check methodology
with 20% sample verified against catalog records.
description: "Inventory activity description"
has_or_had_activity_type:
range: ActivityType
required: true
multivalued: true
description: |
The type classification(s) for this activity.
Values are ActivityType subclasses from ActivityTypes.yaml.
examples:
- value: CurationActivityType
description: "Curation activity"
- value: "[DigitizationActivityType, ResearchActivityType]"
description: "Combined digitization and research project"
temporal_extent:
range: TimeSpan
required: false
inlined: true
description: |
Temporal extent of this activity.
Replaces has_timespan, start_date, end_date.
Uses CIDOC-CRM four-point temporal model for fuzzy bounds.
examples:
- value:
begin_of_the_begin: "2025-01-15"
end_of_the_end: "2025-03-31"
description: "Q1 2025 activity period"
is_or_was_succeeded_by:
range: Activity
multivalued: true
inlined: false
description: Activity/activities that follow this one.
examples:
- value: https://nde.nl/ontology/hc/activity/conservation-treatment-2025
description: "Conservation follows condition survey"
preceding_activity:
range: Activity
inlined: false
description: Activity that preceded this one.
examples:
- value: https://nde.nl/ontology/hc/activity/condition-survey-2024
description: "Condition survey informed this conservation treatment"
status:
range: string
required: false
description: Current status of the activity.
examples:
- value: "IN_PROGRESS"
description: "Activity currently underway"
- value: "COMPLETED"
description: "Activity finished"
- value: "PLANNED"
description: "Activity scheduled for future"
note:
range: string
multivalued: true
description: Additional notes about the activity.
annotations:
specificity_score: "0.50"
specificity_rationale: "Moderately specific - Activity is a core domain concept but broadly applicable across all heritage custodian types."
has_or_had_score: # was: template_specificity - migrated per Rule 53 (2026-01-17)
# NOTE: slot_usage may need manual review for range/description updates '{"collection_discovery": 0.65, "organizational_change": 0.55, "general_heritage": 0.50}'
comments:
- "Base class for all heritage domain activities"
- "Extended by CurationActivity, ConservationActivity, etc."
- "Uses generic slots: has_activity_identifier, has_or_had_activity_type, has_timespan"
- "PROV-O primary alignment for provenance tracking"
- "Supports activity chaining via is_or_was_succeeded_by/preceding_activity"
see_also:
- https://www.w3.org/TR/prov-o/
- http://www.cidoc-crm.org/html/cidoc_crm_v7.1.3.html#E7
- https://www.ica.org/standards/RiC/ontology
examples:
- value:
has_activity_identifier: https://nde.nl/ontology/hc/activity/rijksmuseum-inventory-2025-001
has_activity_name: "2025 Annual Collection Inventory - Dutch Masters"
has_or_had_activity_type:
- CurationActivityType
has_activity_description: |
Annual physical inventory of the Dutch Masters collection
(Gallery of Honour and adjacent galleries). Spot-check methodology
with 20% sample verification against CMS records.
temporal_extent:
begin_of_the_begin: "2025-01-15"
end_of_the_end: "2025-03-31"
status: "IN_PROGRESS"
description: "Inventory activity at Rijksmuseum"
- value:
has_activity_identifier: https://nde.nl/ontology/hc/activity/kb-digitization-medieval-2024
has_activity_name: "Medieval Manuscripts Digitization Project"
has_or_had_activity_type:
- DigitizationActivityType
- ResearchActivityType
has_activity_description: |
High-resolution digitization of 342 medieval manuscripts with
HTR processing and metadata enhancement. IIIF-compliant output.
temporal_extent:
begin_of_the_begin: "2024-03-01"
end_of_the_end: "2025-12-31"
status: "IN_PROGRESS"
preceding_activity: https://nde.nl/ontology/hc/activity/kb-condition-survey-2023
description: "Digitization and research project at KB"
Reference in a new issue View git blame Copy permalink