Stage 7: Derive data quality rules
Knobit of Data modelling · K-705 · Skill
Recognises history kept without its constraints checked
What it means
A table with validity periods or a current-row flag, on a platform where no key can express "no two versions of one key overlap" or "exactly one current row per key", and no DQ rule checks either. Point-in-time joins then return two rows or none.
How it is assessed
Flags the deficient case and passes the acceptable one. Deficient: `dim_account` with `valid_from`/`valid_to`, unique on `(account_identifier, valid_from)` only; two overlapping versions load, and a payment on the overlap is counted twice Acceptable: Two set checks: no overlapping periods per `account_identifier`, exactly one `is_current = TRUE` per `account_identifier`; `dimension: consistency`, threshold 100 %
Builds on
- Recognises inconsistent validity periods in a versioned tableK-623 · Skill
- Explains history strategies and validity-period conventionsK-658 · Knowledge
- Explains rule enforcement mechanisms and platform enforcementK-356 · Knowledge
Needed by
- None