Person Meta_Dates

by

Overview

The Person Meta Dates view provides a structured temporal layer for the Person domain, representing key date-based attributes associated with a canonical PERSON_UID.

It captures assignment-related validity and lifecycle dates in a consistent CDM meta format, enabling controlled and interpretable time-based analysis of person-level context.

This view complements:

  • person.core_details → identity
  • person.meta_codes → classification
  • person.meta_dates → time context

Purpose

  • Provide date-based context for person-linked attributes
  • Support business-applicable temporal interpretation of person context
  • Standardise date attributes using the CDM meta structure
  • Enable consistent alignment across reporting periods
  • Support controlled reporting without exposing full workforce lifecycle logic

Key Features

1. Structured Date Model

Each date is represented as a row using:

  • META_TYPE → logical grouping (e.g. ASSIGNMENT)
  • ATTRIBUTE → date type (e.g. START_DATE, END_DATE)
  • CODE_VALUE → ISO date (YYYY-MM-DD)
  • VALUE_METADATA → JSON payload containing the date

This aligns with the CDM meta pattern and ensures consistency across domains.

2. Assignment Context Dates

The view provides assignment-related temporal attributes:

  • START_DATE → derived assignment start
  • END_DATE → derived assignment end (null when open-ended)
  • VALID_FROM → source validity start
  • VALID_TO → source validity end (normalised for open-ended values)

These dates describe the validity of assignment context linked to a person, not the full workforce lifecycle.

3. Normalised Date Handling

Date values are standardised to ensure consistency:

  • All dates formatted as YYYY-MM-DD
  • Open-ended dates (9999-12-31, 2099-12-31) treated as null
  • Consistent parsing and casting applied across all records

This ensures compatibility across:

  • reporting tools
  • JSON outputs
  • cross-domain joins

4. Identity-Linked Temporal Context

All records are linked through:

  • OBJECT_SEQ → (COMPANY_ID, PERSON_UID)

This ensures:

  • alignment with canonical person identity
  • consistency across Person domain views

5. Flexible Temporal Usage

The structure supports:

  • current-state interpretation
  • historical validity (where retained)
  • business-aligned filtering

This allows consumers to apply time logic without re-engineering source data.

Design Principles

Identity-Led Temporal Context

  • Dates describe person-linked context, not workforce ownership
  • Focus is on interpreting identity in time

Controlled Scope

  • Includes only dates necessary to support:
    • identity interpretation
    • assignment context understanding
  • Avoids expansion into full workforce lifecycle modelling

Separation from Employee Domain

  • Workforce lifecycle dates (employment start, leaving, contract periods) are owned by: ➤ employee.meta_dates
  • Person dates provide supporting context, not operational authority

Long-Form Meta Structure

  • Dates stored as rows rather than columns
  • Enables extensibility and consistent modelling

Design Position: Assignment Dates in Person

Assignment-related dates are included in the Person domain to support specific reporting requirements where a business-applicable date context is required alongside identity.

These dates represent:

  • the validity of the person-context relationship
  • a business interpretation layer of assignment timing

They do not represent:

  • authoritative workforce lifecycle
  • employment contract timelines
  • resource availability or planning

The authoritative source for assignment and employment dates remains:

➡️ employee.meta_dates

Usage Guidance

Use this view when:

  • interpreting validity periods of person-linked context
  • aligning person attributes to business-relevant dates
  • supporting governed or restricted reporting
  • understanding when a person-context relationship is active

Use employee.meta_dates when:

  • analysing workforce lifecycle
  • reporting employment start/end
  • supporting resource planning or utilisation
  • requiring authoritative assignment or employment timelines

Do NOT use this view for:

  • primary workforce lifecycle reporting
  • employment-based timeline analysis
  • resource planning or availability modelling

Relationship to Other Views

person.core_details

Provides the canonical person identity

person.meta_codes

Provides classification and contextual attributes

employee.meta_dates

Provides authoritative workforce lifecycle dates

util.identity_personid

Provides identity resolution and PERSON_UID mapping

Summary

person.meta_dates_UKS provides a controlled temporal layer for the Person domain, enabling consistent interpretation of assignment-related validity periods while maintaining a clear boundary from workforce lifecycle modelling.

It ensures:

  • Person domain retains identity and contextual meaning
  • Employee domain retains ownership of workforce timelines

Leave a Comment