all works
case study / 03

Federated metadata governance across 200+ entities, translated into two repeatable workflows.

I helped design two connected systems: a Universal Lineage Standard for cases where connector scans miss lineage, and a Metadata Handling Logic for cleaning, retaining, or excluding scanned metadata — with human-in-the-loop exception review built in for both.

01two systems i helped design

One for lineage. One for metadata. Both repeatable.

Each workflow slots into the existing federated catalog environment without imposing new tooling. Every decision is traceable through a registry, and only true edge cases reach human reviewers.

Workflow / Auniversal lineage standard

When the scan misses lineage — fall back to a standardised pipeline.

Pulls lineage from multiple technical catalogs, standardises the format, validates it, and pushes it into the business catalog through one consistent API path.

click expand for the full Universal Lineage Standard — fallback when native scans miss lineage
then
Workflow / Bmetadata handling logic

Post-scan workflow — what to map, retain, exclude, and review.

Raw scans don't all belong in the governed catalog. This workflow evaluates each field against the standard, branches into four handling paths, logs every decision, and only sends edge cases to a human reviewer.

click expand for the full Metadata Handling Logic — post-scan enforcement orchestration