¶ case file 6 of 7 · master inventory pipeline — filed 2025-06 · last verified 2026-08

status: concluded — role ended 2026-05

↳ consigned at the yard — ¶ 03 · 07:52 · waybill: the master inventory → the case file

Master Inventory Pipeline

Private proof from institutional ITSM data work: a Python and SQL pipeline that takes Workday exports and Tableau metadata — systems that disagree — and files them into one 35-field master inventory keyed by a deterministic id.

role: data integration engineer
timeframe: 2025-06 to 2026-05
stack: Python · pandas · Tableau
repo: private — institutional — Miami University IT

[ problem ] · § as found

Asset identifiers, ownership fields, Tableau metadata, Workday exports — each system keeps its own version of the truth. Reporting built on records that disagree inherits the disagreement.

constraints —

Keep institutional details private while explaining the engineering shape.
Normalize large operational datasets without losing auditability.
Create deterministic inventory identifiers across heterogeneous sources.
Produce outputs that downstream Tableau Prep flows and dashboards can trust.

fig. 1 — two systems that disagree, filed as one table. every count is the checked-in ledger’s own.

a drawn plate, at rest — not a screenshot. all three row counts and the 35-field schema are the checked-in proof ledger’s; no institutional record is shown.

[ architecture ] · § fig. 2, inked

Workday exports and Tableau metadata feed Python and SQL transforms, deterministic IDs, timestamped run artifacts, and dashboard-ready outputs.

Workday exports

Operational report inputs

metadata

Tableau metadata

Report and asset metadata

report rows

Python/SQL

Cleaning and transforms

normalized records

Unified records

Unified schema and IDs

validation exports

Run artifacts

Timestamped validation outputs

trusted dataset

Tableau Prep

Dashboard-ready inventory

fig. 2 — the system, inked. clay marks the gate: where a check can stop the run.

[ decisions ] · § as filed

d1 — use deterministic inventory ids · accepted

Cross-system reconciliation needed stable keys instead of display names or inconsistent source IDs.¹

¹ tradeoff — ID logic adds up-front modeling work but makes downstream joins and audits more reliable.

d2 — preserve timestamped run artifacts · accepted

Operational data changes over time and stakeholders need to inspect what a run produced.²

² tradeoff — Artifact storage adds cleanup overhead but improves debugging and trust.

d3 — keep the proof private but specific · accepted

The work is organizational and cannot expose raw institutional records.³

³ tradeoff — No one outside the institution can inspect the source data, so this file names the systems, constraints, and validation shape instead.

[ validation ] · § the receipts

at a glance — 3 of 6 terminate in pinned artifacts · 3 described only

validation

01claim: 3,731 Tableau rows and 6,743 Workday rows consolidated into a 10,453-row deduplicated master_inventory.csv.

method: local processed-output audit, counts onlydate: 2026-06
- artifact: checked-in proof ledger — below
[private-safe]
02claim: The 35-field unified schema generates deterministic inventory_id values from row fields.

method: source docs and configs, read in the private repodate: 2026-06
- artifact: checked-in proof ledger — below
[private-safe]
03claim: Runs write timestamped folders plus cumulative processed outputs, while raw institutional exports stay out of version control.

method: repo layout audit — audited by count onlydate: 2026-06

artifact: no linkable artifact — described only
[private-safe]
04claim: The source repo passed 3 extractor tests and critical ruff syntax/import checks in its local virtualenv during this audit.

method: local pytest + ruff rundate: 2026-06
- artifact: checked-in proof ledger — below
[private-safe]
05claim: More than one million operational records ran through the Python/SQL transforms behind OAS and Tableau reporting in this same role.

method: role scope, jun 2025 – may 2026 — institutional ITSM data integrationdate: date not recorded

artifact: no linkable artifact — described only
[local — verified on request]

outcomes

06claim: The unified schema feeds Tableau Prep and dashboard workflows without exposing institutional records.

method: the pipeline’s published boundary, describeddate: date not recorded

artifact: no linkable artifact — described only
[private-safe]

rows marked [local — verified on request] were run by me on personal or demo data · ci rows link the public run · repo pins are the exact commits verified 2026-08.

what i’m NOT claiming —

This file shows counts, schema shape, and architecture only; raw CSV rows, owners, report names, PAT values, and institutional exports stay private.
The 1M+ record transforms are role-scope work with no public artifact — verifiable in interview, not on this page.

[ ledger ] · § master inventory — processed-output ledger — checked in 2026-06

entry	value	note
tableau output	3,731	processed metadata rows
workday output	6,743	processed custom-report rows
master csv	10,453	deduped master rows
schema	35	source fields defined
local tests	3 passed	pytest, extractors
ruff check	passed	E9, F63, F7, F82 critical rules

download the raw ledger (json) ⟶

sanitized local audit summary — no raw institutional rows, owners, report names, or PAT values.

[ corrections ] · § the register

no corrections on file. when a number changes, it is amended here in public — never deleted.

[ appendix ] · § artifacts — none beyond the page

nothing to open here, deliberately — the ledger above is this file’s publishable artifact, shown in full, and the records behind it stay private.