@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/dg-strategy-scorecard-trace/C2> a edu:Question ;
    rdfs:label "C2 (2 points)"@en ;
    dcterms:license <https://creativecommons.org/licenses/by/4.0/> ;
    schema:hasPart <https://knobit.org/id/register/data-governance#DG-650>,
        <https://knobit.org/id/register/data-governance#DG-651> ;
    schema:identifier "C2" ;
    schema:position 2 ;
    schema:text "What the metrics measure, 1 each. (a) GM-102 'Reconciliation controls run on schedule' is filed as an outcome but measures whether a control ran: kind set to control, with SG-101's outcome left to GM-101 and GM-103 (calling it an activity metric earns half). (b) GM-104 'Data incidents reported' is lower-is-better, but the count rises both when credit risk data gets worse and when staff report more honestly (the Q3 rise follows the August awareness campaign): its direction set to none (volume only) or the metric retired, and a metric with a readable direction proposed for SG-101 (for example incidents open past their resolution date, or repeat incidents, lower is better) - not flipped to higher-is-better, and not left lower-is-better, which punishes reporting."@en .

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

<https://knobit.org/id/register/data-governance#DG-650> rdfs:label "dg-strategy-scorecard-trace C2: GM-102 measures that a control ran, filed as an outcome"@en .

<https://knobit.org/id/register/data-governance#DG-651> rdfs:label "dg-strategy-scorecard-trace C2: GM-104 incident count has no readable direction, replaced"@en .

