I3 (1.5 points)
https://knobit.org/id/task/mm-requirements-use-cases/I3
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/mm-requirements-use-cases/I3 |
| rdfs:label | I3 (1.5 points) en |
| schema:hasPart | mm-requirements-use-cases I3a: a business sponsor and allocated, trained curation effort |
| schema:hasPart | mm-requirements-use-cases I3b: metrics of metadata against its use, not counts of objects harvested |
| schema:hasPart | mm-requirements-use-cases I3c: the risks of poor metadata the draft shows, beyond licence cost |
| 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 |