glam/schemas/20251121/linkml/modules/classes/ConversionRate.yaml
kempersc fc405445c6 Refactor and update schema definitions
- Removed obsolete slots: `has_or_had_custodian_observation`, `provider`, and `specificity_annotation`.
- Updated `has_or_had_score` slot to use `SpecificityScore` class and modified its description and examples.
- Added new slots: `end_seconds`, `end_time`, `has_archive_path`, `has_or_had_custodian_name`, `protocol_name`, and `protocol_version`.
- Introduced a script `check_annotation_types.py` to validate the presence and structure of `custodian_types` in YAML files.
- Added a script `update_specificity.py` to automate updates related to `SpecificityAnnotation` to `SpecificityScore`.
2026-02-01 19:55:38 +01:00

78 lines
3.1 KiB
YAML

id: https://nde.nl/ontology/hc/classes/ConversionRate
name: ConversionRate
title: ConversionRate
prefixes:
linkml: https://w3id.org/linkml/
hc: https://nde.nl/ontology/hc/
schema: http://schema.org/
xsd: http://www.w3.org/2001/XMLSchema#
imports:
- linkml:types
- ../slots/has_or_had_type
- ../slots/temporal_extent
default_range: string
classes:
ConversionRate:
description: 'Structured representation of a conversion rate metric for heritage
institutions.
**WHY A DEDICATED CLASS?**
Conversion rates are more than simple floats - they need: - **Type**: What kind
of conversion (visitor-to-purchase, visitor-to-member) - **Value**: The actual
percentage (0.35 = 35%) - **Time Period**: When this rate was measured - **Context**:
Comparison benchmarks, notes
**SLOT_FIXES.YAML REVISION** (lines 1646-1669): - Branch 1: has_or_had_type
→ ConversionRateType/ConversionRateTypes - Branch 2: temporal_extent → TimeSpan
(measurement period)
**USE CASES**: - Gift shop performance: 35% visitor-to-purchase conversion -
Membership drives: 5% visitor-to-member conversion - Digital engagement: 3%
website-to-visit conversion
**ONTOLOGY MAPPING**: - class_uri: schema:QuantitativeValue (numeric measurement)
- Uses schema:interactionStatistic for behavioral metrics'
class_uri: schema:QuantitativeValue
exact_mappings:
- schema:QuantitativeValue
close_mappings:
- schema:interactionStatistic
slots:
- has_or_had_type
- temporal_extent
- rate_value
slot_usage:
has_or_had_type:
range: uriorcurie
inlined: true
examples:
- value: "has_or_had_type:\n has_or_had_label: \"Visitor to Purchase\"\n\
\ source_population: \"museum visitors\"\n target_action: \"made gift\
\ shop purchase\"\n"
temporal_extent:
range: TimeSpan
inlined: true
examples:
- value: "temporal_extent:\n begin_of_the_begin: \"2024-01-01\"\n end_of_the_end:\
\ \"2024-12-31\"\n"
annotations:
custodian_types: '["*"]'
custodian_types_rationale: Conversion rates applicable to all custodian types
with retail or engagement.
custodian_types_primary: '*'
specificity_score: 0.45
specificity_rationale: Moderate specificity - relevant to custodians tracking
performance metrics.
examples:
- value: "ConversionRate:\n rate_value: 0.35\n has_or_had_type:\n has_or_had_label:\
\ \"Visitor to Purchase\"\n temporal_extent:\n begin_of_the_begin: \"\
2024-01-01\"\n end_of_the_end: \"2024-12-31\"\n"
- value: "ConversionRate:\n rate_value: 0.05\n has_or_had_type:\n has_or_had_label:\
\ \"Visitor to Member\"\n temporal_extent:\n begin_of_the_begin: \"2024-06-01\"\
\n end_of_the_end: \"2024-08-31\"\n"
comments:
- Created from slot_fixes.yaml migration (2026-01-14)
- Replaces simple float visitor_conversion_rate slot
- Supports multiple conversion types with industry benchmarks
- Temporal extent enables trend analysis over time