glam/schemas/20251121/linkml/modules/classes/ProfileData.yaml
kempersc 2f44857028 Refactor LinkML schemas and slots for consistency and clarity
- Updated imports in FindingAid.yaml to remove unnecessary entries and added new slots for arrangement level and provenance path.
- Replaced 'full_name' with 'has_or_had_label' in LegalName.yaml and ProfileData.yaml for uniformity.
- Enhanced slot definitions in various YAML files, including ceases_or_ceased_through, has_or_had_arrangement_level, has_or_had_assessment, and others, to include metadata and improve structure.
- Removed the script fix_linkml_metadata.py as it is no longer needed.
- Added new script fix_specific_dead_links.py to handle specific mapping updates for extraction metadata and full name fields across multiple YAML files.
2026-01-29 18:17:47 +01:00

94 lines
3.5 KiB
YAML

id: https://nde.nl/ontology/hc/classes/ProfileData
name: ProfileData
title: ProfileData
prefixes:
linkml: https://w3id.org/linkml/
hc: https://nde.nl/ontology/hc/
schema: http://schema.org/
prov: http://www.w3.org/ns/prov#
xsd: http://www.w3.org/2001/XMLSchema#
pico: https://personsincontext.org/model#
foaf: http://xmlns.com/foaf/0.1/
imports:
- linkml:types
- ./CareerEntry
- ./CertificationEntry
- ./CurrentPosition
- ./Education
- ./HeritageExperienceEntry
- ./MediaAppearanceEntry
- ./PublicationEntry
default_range: string
classes:
ProfileData:
description: "Core profile information for a person, containing extracted biographical data such as name, career history, education, skills, and professional summary. This represents observed/extracted data ABOUT a person from a source document (e.g., LinkedIn profile), not the person entity itself.\nOntology mapping rationale: - class_uri is pico:PersonObservation because this represents observed biographical\n data extracted from a source, following the PiCo pattern of separating observations\n from person reconstructions\n- close_mappings includes foaf:PersonalProfileDocument as this is essentially\n profile document content (though not RDF-specific)\n- related_mappings includes schema:Person because the data describes a person,\n and prov:Entity because the profile data participates in provenance chains"
class_uri: pico:PersonObservation
close_mappings:
- foaf:PersonalProfileDocument
related_mappings:
- schema:Person
- prov:Entity
attributes:
has_or_had_label:
range: string
description: Person's full name
has_or_had_title:
range: string
description: Professional has_or_had_title/title
location:
range: string
description: Location
about:
range: string
description: Professional summary
current_position:
range: CurrentPosition
description: Current job position
skill:
range: string
multivalued: true
inlined_as_list: true
description: Professional skills
has_or_had_language:
range: string
multivalued: true
inlined_as_list: true
description: Languages known
specifies_or_specified:
range: Education
multivalued: true
inlined_as_list: true
description: Educational background. MIGRATED from education per Rule 53 (2026-01-25).
certifications:
range: CertificationEntry
multivalued: true
inlined_as_list: true
description: Professional certifications
career_history:
range: CareerEntry
multivalued: true
inlined_as_list: true
description: Complete career history
heritage_relevant_experience:
range: HeritageExperienceEntry
multivalued: true
inlined_as_list: true
description: Heritage sector experience
publications:
range: PublicationEntry
multivalued: true
inlined_as_list: true
description: Academic/professional publications
media_appearances:
range: MediaAppearanceEntry
multivalued: true
inlined_as_list: true
description: Media appearances
professional_summary:
range: string
description: Professional summary
annotations:
specificity_score: 0.1
specificity_rationale: Generic utility class/slot created during migration
custodian_types: "['*']"
custodian_types_rationale: Universal utility concept