Court Geometry
Schema Reference — Staging
Complete schema docs for staging tier (396 schemas)
Generated schema contract
Use staging reference to verify cleanup before transforms
This is the half-court contract: normalized columns, typed data, and load-ready keys before star-schema transforms begin. Use it to verify cleanup choices without reading transform code first.
confirm renamed fields, typing, and foreign-key hints in the warehouse-ready layer
staging blocks often reveal the intended join anchors for downstream models
regenerate from schema metadata instead of hand-editing
Compare to the raw contract only when needed
Staging is already cleaned up, so use raw reference only to answer what changed rather than rereading both pages in full.
Focus on renamed identifiers and typed columns
Those are usually the signals that matter most when you are planning joins or debugging transform assumptions.
Follow dependencies once the shape is clear
Switch to lineage or relationships when the next question is about impact radius or join strategy.
Next possession
Translate staging cleanup into join intent
Staging contracts show the half-court set: renamed columns, normalized types, and load-ready keys. Use these pages to move from cleanup details into joins, dependencies, and reader-facing naming.
Relationships
Turn normalized keys into concrete join lanes across player, team, game, and event analysis.
Table Lineage
Trace which staging tables feed the downstream dimensions, facts, and aggregates you care about.
Field Reference
Use the naming guide when staging cleanup introduced warehouse-style field conventions.
Schema Reference — Staging
This tier contains 396 schemas.
Progressive scan
Open only the generated family and contract you need
The full board is still here, but it now stays grouped until you open a family or filter to the exact table you need.
Companion cuts
Turn staging contracts into join and dependency reasoning
These curated pages help once the cleanup is confirmed and the next question becomes how that staged data behaves downstream.
Translate cleaned keys into relationship lanes
Use the join playbook when staging identifiers are clear and the next step is SQL shape.
Trace which facts and dimensions inherit this stage
Best next stop when a staging change might ripple through multiple downstream outputs.
Decode warehouse-friendly field names
Use the field guide when cleanup improved the name but not the full semantic picture.
