@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/mm-requirements-use-cases/I3> a edu:Question ;
    rdfs:label "I3 (1.5 points)"@en ;
    dcterms:license <https://creativecommons.org/licenses/by/4.0/> ;
    schema:hasPart <https://knobit.org/id/register/metadata-management#MD-166>,
        <https://knobit.org/id/register/metadata-management#MD-167>,
        <https://knobit.org/id/register/metadata-management#MD-168> ;
    schema:identifier "I3" ;
    schema:position 6 ;
    schema:text "People, measures and risks, 0.5 each. (a) sponsor is a business executive role from the roles table (Chief Operating Officer, Chief Risk Officer or Chief Data Officer) and curation_effort allocates curators' and stewards' time (not spare time), with training or communication before go-live. (b) metrics measure the metadata against its use - use cases answerable at their freshness, steward or curator coverage, load success, confirmed candidates or metadata quality, catalogue use - not only counts of objects harvested and systems scanned. (c) risks name at least two risks of poor metadata beyond licence cost, from those this draft shows: a supervisory finding in the COREP inspection, a change deployed with the wrong impact, curated metadata decaying without curators, wrong personal data classes, stale core banking columns."@en .

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

<https://knobit.org/id/register/metadata-management#MD-166> rdfs:label "mm-requirements-use-cases I3a: a business sponsor and allocated, trained curation effort"@en .

<https://knobit.org/id/register/metadata-management#MD-167> rdfs:label "mm-requirements-use-cases I3b: metrics of metadata against its use, not counts of objects harvested"@en .

<https://knobit.org/id/register/metadata-management#MD-168> rdfs:label "mm-requirements-use-cases I3c: the risks of poor metadata the draft shows, beyond licence cost"@en .

