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

219 lines
11 KiB
YAML

id: https://nde.nl/ontology/hc/class/PersonObservation
name: PersonObservation
title: Person Observation (Staff Role Context)
prefixes:
linkml: https://w3id.org/linkml/
hc: https://nde.nl/ontology/hc/
schema: http://schema.org/
pico: https://personsincontext.org/model#
pnv: https://w3id.org/pnv#
crm: http://www.cidoc-crm.org/cidoc-crm/
foaf: http://xmlns.com/foaf/0.1/
prov: http://www.w3.org/ns/prov#
dcterms: http://purl.org/dc/terms/
sdo: https://schema.org/
imports:
- linkml:types
- ../slots/id
- ../slots/person_name
- ../slots/has_person_name
- ../slots/has_or_had_date_of_birth
- ./BirthDate
- ../slots/has_or_had_place_of_birth
- ./BirthPlace
- ../slots/is_deceased
- ./DeceasedStatus
- ../slots/has_or_had_age
- ../classes/Age
- ../slots/occupation
- ../slots/religion
- ../slots/has_or_had_label
- ../slots/identifies_or_identified_as
- ./Gender
- ../slots/pronoun
- ../slots/staff_role
- ../slots/role_title
- ../slots/is_or_was_affiliated_with
- ./OrganizationUnit
- ../slots/role_start_date
- ../slots/role_end_date
- ../slots/observation_source
- ../slots/has_or_had_provenance
- ../slots/is_or_was_affected_by_event
- ../slots/has_or_had_expertise_in
- ./ExpertiseArea
- ../slots/refers_to_person
- ../slots/has_or_had_web_claim
- ../slots/linkedin_profile_path
- ../slots/linkedin_profile_url
- ../slots/has_or_had_provenance
- ../slots/created
- ../slots/modified
- ./PersonWebClaim
- ./PersonName
- ./ExtractionMetadata
- ./Person
- ../slots/specificity_annotation
- ../slots/has_or_had_score
- ./OrganizationalChangeEvent
- ./OrganizationalStructure
- ./SpecificityAnnotation
- ./StaffRole
- ./TemplateSpecificityScore
- ./TemplateSpecificityType
- ./TemplateSpecificityTypes
- ./TimeSpan
classes:
PersonObservation:
class_uri: pico:PersonObservation
description: "An observation of a person serving in a staff role at a heritage custodian institution,\nas documented in a specific source at a specific point in time.\n\n**PiCo Pattern Adaptation**:\nThe PiCo (Persons in Context) ontology distinguishes between:\n- **PersonObservation**: Data about a person as found in a source (evidence-based)\n- **PersonReconstruction**: Aggregated identity from multiple observations (inferred)\n\nFor heritage custodian staff tracking, we adapt this pattern:\n- **PersonObservation**: Staff role as documented in institutional sources\n (annual reports, org charts, staff directories, archival records)\n- Focus on ROLES and AFFILIATIONS rather than biographical details\n- Temporal validity tracks employment period in specific position\n\n**Key Distinction from General Person Data**:\nThis class models INSTITUTIONAL ROLES, not complete biographical data:\n- Emphasis: Role, title, unit affiliation, employment dates\n- NOT: Full biographical reconstruction\
\ (birth, death, family, etc.)\n- Sources: Institutional records (not vital records, census, etc.)\n- PiCo: `pico:PersonObservation` (primary - person data from sources)\n- Schema.org: `schema:Person` (for person identity)\n- Schema.org: `schema:Role` (for organizational role)\n- CIDOC-CRM: `crm:E21_Person` (person as cultural heritage actor)\n- PROV-O: `prov:Agent` (person as responsible agent)\n- FOAF: `foaf:Person` (person in social network)\n\n**Hub Architecture Integration**:\n- PersonObservation refers to Person hub via `refers_to_person` (PICO pattern)\n- PersonObservation refers to OrganizationUnit via `is_or_was_affiliated_with`\n- OrganizationalStructure refers back via `staff_members` (bidirectional)\n- PersonObservation affected by OrganizationalChangeEvent via `affected_by_event`\n- Person hub links to Event via `participated_in_events`\n- Temporal alignment: employment dates vs. organizational unit validity\n\n**Use Cases**:\n1. **Staff directories**: Document current\
\ and historical staff roles\n2. **Organizational provenance**: Track who managed departments/collections\n3. **Workforce history**: Analyze staffing patterns over time\n4. **Expertise tracking**: Find conservators, curators by specialization\n5. **Reorganization impact**: Track staff transitions during structural changes\n\n**Example - Conservation Staff**:\n\n```yaml\nPersonObservation:\n person_name: \"Dr. Jane Smith\"\n staff_role: CONSERVATOR\n role_title: \"Senior Paintings Conservator\"\n is_or_was_affiliated_with: \".../org-unit/rm-conservation-division\"\n role_start_date: \"2013-03-01\"\n role_end_date: null # Still employed\n observation_source:\n source_type: \"Staff directory\"\n source_uri: \"https://rijksmuseum.nl/staff/jane-smith\"\n observation_date: \"2024-11-22\"\n```\n\n**Example - Staff Through Organizational Change**:\n\n```yaml\n# Before merger (2013-02-28)\nPersonObservation:\n person_name: \"Dr. Jane Smith\"\n staff_role: CONSERVATOR\n role_title:\
\ \"Head, Paintings Conservation Department\"\n is_or_was_affiliated_with: \".../org-unit/rm-paintings-conservation\"\n role_start_date: \"2010-01-01\"\n role_end_date: \"2013-02-28\"\n\n# After merger (2013-03-01)\nPersonObservation:\n person_name: \"Dr. Jane Smith\"\n staff_role: CONSERVATOR\n role_title: \"Deputy Director, Conservation Division\"\n is_or_was_affiliated_with: \".../org-unit/rm-conservation-division\"\n role_start_date: \"2013-03-01\"\n role_end_date: null\n affected_by_event: \".../event/rm-conservation-merger-2013\"\n```\n"
exact_mappings:
- pico:PersonObservation
close_mappings:
- schema:Person
- schema:Role
- crm:E21_Person
- foaf:Person
- prov:Agent
slots:
- is_or_was_affected_by_event
- has_or_had_age
slot_usage:
has_or_had_age:
range: string
description: Age of the person (structured or simple value).
required: false
occupation:
range: string
multivalued: true
required: false
religion:
range: string
required: false
identifies_or_identified_as:
description: 'Gender identity or social classification of the person.
MIGRATED from gender_identity per slot_fixes.yaml (Rule 53, 2026-01-26).
Uses Gender class.
'
range: Gender
inlined: true
required: false
examples:
- value:
has_or_had_label: Female
description: Female gender identity
- value:
has_or_had_label: Male
description: Male gender identity
pronoun:
range: string
required: false
staff_role:
range: StaffRole
required: true
role_title:
range: string
required: false
is_or_was_affiliated_with:
range: OrganizationUnit
required: false
description: 'The organizational unit this person is/was affiliated with.
MIGRATED from unit_affiliation per slot_fixes.yaml (Rule 53, 2026-01-15).
'
role_start_date:
range: date
required: false
role_end_date:
range: date
required: false
observation_source:
range: string
required: false
description: Simple text reference to source (use has_or_had_provenance for structured data)
has_or_had_provenance:
range: Provenance
inlined: true
required: false
description: 'Extraction provenance metadata.
MIGRATED from extraction_metadata per Rule 53 (2026-01-26).
'
is_or_was_affected_by_event:
range: OrganizationalChangeEvent
required: false
has_or_had_expertise_in:
range: ExpertiseArea
multivalued: true
inlined: true
required: false
description: 'Area of expertise.
MIGRATED from expertise_area (2026-01-26).
'
has_or_had_web_claim:
range: PersonWebClaim
multivalued: true
required: false
inlined: true
inlined_as_list: true
linkedin_profile_path:
range: string
required: false
linkedin_profile_url:
range: uri
required: false
created:
range: datetime
modified:
range: datetime
comments:
- PiCo PersonObservation pattern adapted for institutional staff role tracking
- Focus on ROLES and AFFILIATIONS within heritage organizations
- NOT general biographical reconstruction (PiCo PersonReconstruction is separate concept)
- refers_to_person links observation to Person hub (core PICO pattern)
- Multiple observations from different sources can refer to same Person hub
- Temporal validity enables tracking staff through organizational changes
- "Bidirectional links: staff \u2192 unit (is_or_was_affiliated_with), unit \u2192 staff (staff_members)"
- "Person hub \u2192 Event via participated_in_events enables career event tracking"
- 'Rule 26 compliance: web_claims slot enables verifiable provenance for person data'
- LinkedIn data stored separately in person/entity/ files (Rule 12, Rule 20)
examples:
- value: 'id: https://nde.nl/ontology/hc/person-obs/nl-nh-ams-m-rm/jane-smith/conservator-2013
person_name: Dr. Jane Smith
refers_to_person: https://nde.nl/ontology/hc/person/jane-smith
staff_role: CONSERVATOR
role_title: Deputy Director, Conservation Division
is_or_was_affiliated_with: https://nde.nl/ontology/hc/org-unit/rm-conservation-division
role_start_date: ''2013-03-01''
role_end_date: null
affected_by_event: https://nde.nl/ontology/hc/event/rm-conservation-merger-2013
'
description: Conservator promoted during department merger, linked to Person hub
- value: "id: https://nde.nl/ontology/hc/person-obs/nl-nh-ams-m-rm/taco-dibbits/director-2016\nperson_name: Taco Dibbits\nrefers_to_person: https://nde.nl/ontology/hc/person/taco-dibbits\nstaff_role: DIRECTOR\nrole_title: General Director\nrole_start_date: '2016-09-01'\nrole_end_date: null\nlinkedin_profile_url: https://www.linkedin.com/in/taco-dibbits\nlinkedin_profile_path: data/custodian/person/entity/taco-dibbits_20250115T103000Z.json\nhas_or_had_web_claim:\n- person_claim_type: full_name\n person_claim_value: Taco Dibbits\n source_url: https://www.rijksmuseum.nl/en/about-us/organisation\n person_xpath: /html/body/main/section[2]/div[1]/h2\n retrieved_on: '2025-01-15T10:30:00Z'\n retrieval_agent: firecrawl\n person_xpath_match_score: 1.0\n- person_claim_type: role_title\n person_claim_value: General Director\n source_url: https://www.rijksmuseum.nl/en/about-us/organisation\n person_xpath: /html/body/main/section[2]/div[1]/p[1]\n retrieved_on: '2025-01-15T10:30:00Z'\n retrieval_agent:\
\ firecrawl\n person_xpath_match_score: 1.0\n"
description: Museum director with Person hub link and full web claim provenance (Rule 26 compliant)
annotations:
specificity_score: 0.1
specificity_rationale: Generic utility class/slot created during migration
custodian_types:
- '*'
custodian_types_rationale: Universal utility concept