@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix edu: <https://knobit.org/def/> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix schema: <https://schema.org/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

<https://knobit.org/id/task/dq-root-cause/C3> a edu:Question ;
    rdfs:label "C3 (2 points)"@en ;
    dcterms:license <https://creativecommons.org/licenses/by/4.0/> ;
    schema:hasPart <https://knobit.org/id/register/data-quality#QI-554>,
        <https://knobit.org/id/register/data-quality#QI-555> ;
    schema:identifier "C3" ;
    schema:position 3 ;
    schema:text "The migration claimed for OB-004 as well, 1 each. (a) CA-003 no longer claims OB-004: its failures began in July, before wave 1 (18 August), at a steady 790-820 a month, and fall on migrated and non-migrated customers alike (1,160 and 1,290); CRM-MAP-14 copies date_of_birth unchanged. (b) OB-004 gets a cause of its own mechanism: the partner API sends birthDate as MM-DD-YYYY (contract annex 3) and the onboarding service parses it as DD-MM-YYYY, so partner customers born on day 1-12 get day and month swapped (all 2,420 partner failures) and those born on day 13-31 are rejected (4,050 DOB_INVALID) - fixed in the onboarding service's partner parsing (design), not by correcting rows alone."@en .

edu:Question rdfs:label "Question"@en,
        "Küsimus"@et .

<https://knobit.org/id/register/data-quality#QI-554> rdfs:label "dq-root-cause C3a: the migration cause withdrawn from OB-004, which it cannot produce"@en .

<https://knobit.org/id/register/data-quality#QI-555> rdfs:label "dq-root-cause C3b: OB-004 given its own mechanism, the partner date format parsed the wrong way"@en .