glam/schemas/20251121/linkml/modules/classes/DataTierLevel.yaml

93 lines
No EOL
3.4 KiB
YAML

id: https://nde.nl/ontology/hc/class/DataTierLevel
name: data_tier_level_class
title: DataTierLevel Class
description: >-
Data quality tier classification indicating the trustworthiness and
verification status of heritage data.
The tier system reflects the provenance and verification level of information,
from authoritative official registries to algorithmically inferred data.
prefixes:
linkml: https://w3id.org/linkml/
hc: https://nde.nl/ontology/hc/
prov: http://www.w3.org/ns/prov#
dqv: http://www.w3.org/ns/dqv#
imports:
- linkml:types
- ../slots/has_or_had_code
- ../slots/has_or_had_description
- ../slots/has_or_had_label
default_prefix: hc
classes:
DataTierLevel:
class_uri: hc:DataTierLevel
description: >-
Data quality tier level classification.
**Standard Tier Levels** (from most to least authoritative):
| Tier | Short Code | Description | Examples |
|------|------------|-------------|----------|
| Tier 1 | TIER_1_AUTHORITATIVE | Official registry data | NDE CSV, ISIL registry, government databases |
| Tier 2 | TIER_2_VERIFIED | Verified external sources | Wikidata (verified), Google Maps, official websites |
| Tier 3 | TIER_3_CROWD_SOURCED | Community-contributed data | Reviews, user edits, Wikipedia |
| Tier 4 | TIER_4_INFERRED | Algorithmically extracted | Website scrape, LLM extraction, API inference |
**Usage Guidelines**:
- Always prefer higher-tier data when available
- TIER_4 data requires verification before promotion
- Data can be promoted to higher tiers after verification
- Track tier changes in provenance history
**PROV-O Alignment**: Maps to prov:qualifiedDerivation for data quality tracking.
exact_mappings:
- dqv:QualityMeasurement
close_mappings:
- prov:qualifiedDerivation
slots:
- has_or_had_label
- has_or_had_code
- has_or_had_description
slot_usage:
has_or_had_label:
# range: string
required: true
examples:
- value: "Authoritative"
- value: "Inferred"
has_or_had_code:
# range: string
required: true
pattern: "^TIER_[1-4]_[A-Z_]+$"
examples:
- value: "TIER_1_AUTHORITATIVE"
- value: "TIER_4_INFERRED"
has_or_had_description:
# range: string
required: false
examples:
- value: "Extracted from NDE CSV registry - authoritative Dutch heritage data"
- value: "Extracted via LLM from website - requires verification"
annotations:
specificity_score: 0.35
specificity_rationale: >-
Data tier levels are broadly useful across all data provenance contexts.
custodian_types: '["*"]'
custodian_types_rationale: >-
Data quality tiers apply universally to all custodian types.
examples:
- value:
has_or_had_label: "Authoritative"
has_or_had_code: "TIER_1_AUTHORITATIVE"
has_or_had_description: "Official data from NDE registry CSV"
- value:
has_or_had_label: "Verified"
has_or_had_code: "TIER_2_VERIFIED"
has_or_had_description: "Verified against institutional website"
- value:
has_or_had_label: "Inferred"
has_or_had_code: "TIER_4_INFERRED"
has_or_had_description: "Extracted via Exa search - pending verification"