Person Meta_Codes

by

Overview

The Person Meta Codes view provides a governed and curated attribute layer for the Person domain, representing identity, linkage, restricted classification, and limited mirrored assignment context for each canonical PERSON_UID.

This view extends person.core_details by introducing structured attributes using the CDM meta pattern, enabling controlled person-based reporting and cross-system identity linkage.

It is designed to support identity-led and governed reporting, not general workforce or organisational analysis.

Purpose

  • Provide a standardised attribute model for the Person domain
  • Support canonical identity reporting using PERSON_UID
  • Enable secure linkage between person and source-system identifiers
  • Expose restricted or sensitive attributes in a controlled format
  • Provide a limited mirrored view of assignment context where required
  • Maintain clear separation from the Employee domain

Key Features

1. Structured Meta Model

Each attribute is represented as a row using:

  • META_TYPE → logical grouping (e.g. ASSIGNMENT, PAYROLL)
  • ATTRIBUTE → attribute name
  • CODE_VALUE → standardised value
  • VALUE_METADATA → JSON payload with descriptive context

This ensures consistency with the broader CDM meta framework.

2. Identity-Centric Attributes

Provides key identity and linkage attributes, including:

  • PERSON_ID
  • PAYROLL_ID
  • EMP_NO

These support:

  • identity reconciliation
  • cross-system linking
  • controlled reporting

3. Controlled Assignment Context (Mirrored)

Includes a limited subset of current assignment attributes, such as:

  • status
  • location
  • organisation code and level
  • assignment pattern
  • line manager
  • HR business partner

This information is included to:

  • support interpretation of the person record
  • enable controlled reporting scenarios

However:

These attributes are mirrored context only, not the authoritative workforce model.

4. Payroll & Personal Classification

Includes controlled person-level attributes such as:

  • year of birth (YoB)
  • gender
  • citizenship
  • position code

These are provided to support:

  • governed HR reporting
  • classification and segmentation

5. Cross-System Identity Linking

Links person records to operational identifiers through:

  • PERSON_ID
  • EMP_NO
  • PAYROLL_ID

This enables:

  • consistent joins across domains
  • reconciliation between Person and Employee datasets

6. Current-State Filtering

Assignment-related attributes are constrained to:

  • current records (VALID_FROM / VALID_TO)
  • primary assignments

This ensures the view reflects the most relevant “as of now” context without requiring consumers to manage effective dating.

Design Principles

Identity-Led Domain

  • The Person domain describes the individual as a human identity
  • Focus is on identity, linkage, and controlled classification

Controlled Mirroring

  • Assignment attributes are included as a deliberate, limited subset
  • Purpose is contextual understanding, not operational reporting

Separation from Employee Domain

  • employee.meta_codes is the authoritative source for:
    • workforce structure
    • assignment
    • organisation
    • line management
  • Person should not evolve into a duplicate workforce model

Long-Form Meta Structure

  • Attributes stored as rows, not columns
  • Supports extensibility and consistent modelling

Governed Exposure

  • Designed for controlled and restricted reporting scenarios
  • Minimises exposure of raw HR data

Usage Guidance

Use this view when:

  • resolving canonical person identity (PERSON_UID)
  • linking individuals across systems
  • supporting restricted or governed people reporting
  • accessing identity or payroll-linked attributes
  • applying limited contextual understanding of a person’s organisational position

Use employee.meta_codes when:

  • analysing workforce structure
  • reporting on organisation or assignment
  • working with line management or job context
  • supporting operational or planning use cases

Do NOT use this view for:

  • primary organisational hierarchy reporting
  • general workforce reporting
  • full assignment or job analysis

Relationship to Other Views

person.core_details

Provides the canonical person object and identity foundation

util.identity_personid

Provides identity resolution and PERSON_UID mapping

employee.meta_codes

Provides the authoritative workforce and assignment attribute model

person.meta_dates

Provides temporal context for the Person domain

Summary

person.meta_codes provides a controlled, identity-focused attribute layer for the Person domain.

It combines:

  • identity linkage
  • restricted classification
  • limited assignment context

to support secure and consistent person-level reporting.

The view maintains a clear boundary:

  • Person → identity and governed attributes
  • Employee → workforce and operational reporting

Leave a Comment