C1 (3 points)
https://knobit.org/id/task/dq-rule-derivation/C1
Also as Turtle · JSON-LD · RDF/XML
| dcterms:license | https://creativecommons.org/licenses/by/4.0/ |
|---|---|
| owl:sameAs | https://bitbucket.org/reffa/ontology/id/task/dq-rule-derivation/C1 |
| rdfs:label | C1 (3 points) en |
| schema:hasPart | dq-rule-derivation C1a: stored available balance checked against ledger less holds |
| schema:hasPart | dq-rule-derivation C1b: summary table recomputed and its missing as-of date reported |
| schema:hasPart | dq-rule-derivation C1c: rate snapshot at opening left without a consistency check |
| schema:hasPart | dq-rule-derivation C1d: residency copied onto the account with nothing keeping it equal |
| schema:hasPart | dq-rule-derivation C1e: copied residency made a controlled denormalisation |
| schema:identifier | C1 |
| schema:position | 1 |
| schema:text | Stored derived and copied values, the physical model's own DQ obligations: (a) 0.5 - BR-206: available_balance_amount is stored beside ledger_balance_amount and hold_amount, so a row consistency check compares it with ledger_balance_amount - hold_amount (or the column is replaced by a computed one, with the check kept until then); (b) 1 - BR-207: AGG_CUSTOMER_COVERAGE is a stored summary reloaded nightly, so a set check recomputes covered_amount_eur from the balances at the FX rate valid on the balance date and returns the customers that differ (0.5), and the table's missing as-of date is reported - nothing says which balance date it holds, so a failed reload passes yesterday's figures off as today's (0.5); (c) 0.5 - DIM_DEPOSIT_ACCOUNT.interest_rate_at_opening gets no consistency check, as a snapshot meant to differ from interest_rate; earned only together with (a) or (b); (d) 0.5 - holder_residency_country is reported as a copy with nothing keeping it equal to DIM_CUSTOMER.residency_country_code: a customer who moves gets a new customer version and the account row keeps the old country unless the account itself changes; (e) 0.5 - the copy is made controlled: a consistency check compares it with the first holder's current customer version, and a physical finding names the mechanism that refreshes it, or replaces it with a view. en |