Explains impact-based severity of data quality issues
https://knobit.org/id/knobit/Q-651
Also as Turtle · JSON-LD · RDF/XML · AI benchmark on Skilirium
| Context functions | Object understanding |
|---|---|
| Knobit creation methods | AI generated |
| Knobit creation methods | AI generated, AI edited |
| Knobit types | Knowledge |
| LCG purposes | Assessing the learner's knowledge or skill state |
| LCG purposes | Opening up a learning outcome |
| action verb | Explains en |
| assessment criterion | Answers a written question on the data quality issue severity correctly en |
| assessment criterion | Answers a written question on the issue severity correctly en |
| assessment method | Written question en |
| conforms to profile | https://oppekava.edu.ee/a/Knobitite_kirjeldamise_ja_seostamise_reeglid#LCG-KNOBIT-0.1 |
| dcterms:identifier | G-553 |
| dcterms:identifier | Q-651 |
| dcterms:license | https://creativecommons.org/licenses/by/4.0/ |
| dcterms:source | Practice the stage 5 reference and review checklist rest on en |
| dcterms:source | Practice the stage 6 reference and review checklist rest on en |
| expected result | Severity follows a stated impact - regulatory, financial, customers, reports - not the volume of complaints. en |
| expected result | Severity levels are defined by impact in the issue policy before any issue is rated (a misstated regulatory return or customer payout, a misstated board KPI, an operational inconvenience); each issue records its impact in words and, where possible, numbers (DMBOK2 ch. 13, 2.7.3). en |
| owl:sameAs | https://bitbucket.org/reffa/ontology/id/knobit/data-governance/05-issue-management/G-553 |
| rdfs:label | Explains impact-based severity of data quality issues en |
| rdfs:label | Explains severity by impact en |
| schema:creativeWorkStatus | accepted |
| schema:isPartOf | Data governance (DAMA-DMBOK2) |
| schema:isPartOf | Data quality management (DAMA-DMBOK2) |
| skos:definition | Severity follows a stated impact - regulatory, financial, customers, reports - not the volume of complaints. en |
| skos:definition | Severity levels are defined by impact in the issue policy before any issue is rated (a misstated regulatory return or customer payout, a misstated board KPI, an operational inconvenience); each issue records its impact in words and, where possible, numbers (DMBOK2 ch. 13, 2.7.3). en |
| skos:prefLabel | Explains impact-based severity of data quality issues en |
| skos:prefLabel | Explains severity by impact en |
| target object | data quality issue severity en |
| target object | issue severity en |
Used by
| applies knowledge | Recognises an issue severity with no impact |
|---|---|
| applies knowledge | Recognises a data quality issue severity set by the reporter |
| applies knowledge | Recognises an issue on a critical data element with no impact stated |
| depends on knobit | Explains resolution targets and escalation of data quality issues |
| includes knobit | Routes governance issues to the lowest level with authority and closes them by verified decisions |
| includes knobit | Manages data quality issues by impact through to verified closure |
| includes knobit | Engage in issue management |
| includes knobit | Identify and prioritise potential improvements |
| includes knobit | Develop operational procedures for managing data issues |
| requires knobit | Manage and escalate governance issues |
| requires knobit | Manage data quality issues |