Metadata management (DAMA-DMBOK2)

https://knobit.org/id/register/metadata-management

LCG purposes	Assessing the learner's knowledge or skill state
LCG purposes	Opening up a learning outcome
LCG purposes	Selecting an assessment task or learning activity
conforms to profile	https://oppekava.edu.ee/a/Knobitite_kirjeldamise_ja_seostamise_reeglid#LCG-KNOBIT-0.1
dcterms:description	Recognising defects in metadata deliverables - requirements and strategy, metamodel, business glossary, catalogue entries, column-level lineage and change impact analysis - so that metadata can answer its users' questions all the way to the end: the competence the metadata-management skill applies, and that skill-tests assesses. en
dcterms:identifier	SCOPE-1
dcterms:license	https://creativecommons.org/licenses/by/4.0/
dcterms:rights	Copyright 2026 Peep Küngas. Licensed under CC BY 4.0.
dcterms:title	Metadata management (DAMA-DMBOK2) en
owl:sameAs	https://bitbucket.org/reffa/ontology/skills/metadata-management
schema:license	https://creativecommons.org/licenses/by/4.0/
skos:note	audience: Metadata managers, data stewards, catalogue curators, data architects, and AI models assessed by skill-tests en
skos:note	domain: Data management, metadata management (DAMA-DMBOK2 chapter 12) en
skos:note	level: CDMP Practitioner: the Metadata Management specialist exam (DAMA International) en

Items and references

mm-requirements-use-cases C1a: a use case with no needs (UC-104) given document metadata from the document management system edu:Question

https://knobit.org/id/register/metadata-management#MD-150

dcterms:identifier	MD-150
rdfs:label	mm-requirements-use-cases C1a: a use case with no needs (UC-104) given document metadata from the document management system en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C1 (3 points)
solvable with	set of Recognises a metadata use case with no metadata serving it, Explains metadata for unstructured data

mm-requirements-use-cases C1b: load run and row count with no source (UC-105) given an operational source, the scheduler run log edu:Question

https://knobit.org/id/register/metadata-management#MD-151

dcterms:identifier	MD-151
rdfs:label	mm-requirements-use-cases C1b: load run and row count with no source (UC-105) given an operational source, the scheduler run log en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C1 (3 points)
solvable with	set of Recognises a needed metadata type with no source

mm-requirements-use-cases C1c: report view counts harvested for no use case (MX-106) retired or given a use case edu:Question

https://knobit.org/id/register/metadata-management#MD-152

dcterms:identifier	MD-152
rdfs:label	mm-requirements-use-cases C1c: report view counts harvested for no use case (MX-106) retired or given a use case en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C1 (3 points)
solvable with	set of Recognises metadata collected for no use case

mm-requirements-use-cases C2a: same-day lineage from a quarterly wiki (UC-101, MX-102) replaced by SQL parsing on deployment edu:Question

https://knobit.org/id/register/metadata-management#MD-153

dcterms:identifier	MD-153
rdfs:label	mm-requirements-use-cases C2a: same-day lineage from a quarterly wiki (UC-101, MX-102) replaced by SQL parsing on deployment en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C2 (3 points)
solvable with	set of Recognises a metadata freshness the capture method cannot meet

mm-requirements-use-cases C2b: classifier-inferred personal data classes published as approved (MX-107) made candidates until confirmed edu:Question

https://knobit.org/id/register/metadata-management#MD-154

dcterms:identifier	MD-154
rdfs:label	mm-requirements-use-cases C2b: classifier-inferred personal data classes published as approved (MX-107) made candidates until confirmed en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C2 (3 points)
solvable with	set of Recognises inferred metadata published as approved

mm-requirements-use-cases C2c: curated workbook steps with a vacant curator (MX-104) given a curator who holds the role edu:Question

https://knobit.org/id/register/metadata-management#MD-155

dcterms:identifier	MD-155
rdfs:label	mm-requirements-use-cases C2c: curated workbook steps with a vacant curator (MX-104) given a curator who holds the role en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C2 (3 points)
solvable with	set of Recognises curated metadata with no curator

mm-requirements-use-cases C3a: a use case with no user (UC-106) given the role that acts on the answer edu:Question

https://knobit.org/id/register/metadata-management#MD-156

dcterms:identifier	MD-156
rdfs:label	mm-requirements-use-cases C3a: a use case with no user (UC-106) given the role that acts on the answer en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C3 (2 points)
solvable with	set of Recognises a metadata use case with no user

mm-requirements-use-cases C3b: a home page tile driven by the licence (UC-109) retired or rewritten as a question with a business driver edu:Question

https://knobit.org/id/register/metadata-management#MD-157

dcterms:identifier	MD-157
rdfs:label	mm-requirements-use-cases C3b: a home page tile driven by the licence (UC-109) retired or rewritten as a question with a business driver en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C3 (2 points)
solvable with	set of Explains use-case-driven metadata requirements, Explains the business drivers of metadata management

mm-requirements-use-cases I1a: lake files needed within minutes (UC-108) served from the ingest metastore, not a weekly file scan edu:Question

https://knobit.org/id/register/metadata-management#MD-158

dcterms:identifier	MD-158
rdfs:label	mm-requirements-use-cases I1a: lake files needed within minutes (UC-108) served from the ingest metastore, not a weekly file scan en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I1 (2 points)
solvable with	set of Explains metadata for big data ingest

mm-requirements-use-cases I1b: attribute definitions retyped from the modelling tool (MX-110) harvested from its repository or XMI edu:Question

https://knobit.org/id/register/metadata-management#MD-159

dcterms:identifier	MD-159
rdfs:label	mm-requirements-use-cases I1b: attribute definitions retyped from the modelling tool (MX-110) harvested from its repository or XMI en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I1 (2 points)
solvable with	set of Explains the kinds of metadata sources, Explains metadata repository management tools
solvable with	set of Explains the kinds of metadata sources, Explains the standards used for metadata

mm-requirements-use-cases I1c: a failing core banking scan nobody noticed (MX-111) given load monitoring with an owner edu:Question

https://knobit.org/id/register/metadata-management#MD-160

dcterms:identifier	MD-160
rdfs:label	mm-requirements-use-cases I1c: a failing core banking scan nobody noticed (MX-111) given load monitoring with an owner en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I1 (2 points)
solvable with	set of Explains managing metadata stores

mm-requirements-use-cases I1d: lineage for ECB inspectors delivered in a portal they cannot reach (UC-102) handed over as a report edu:Question

https://knobit.org/id/register/metadata-management#MD-161

dcterms:identifier	MD-161
rdfs:label	mm-requirements-use-cases I1d: lineage for ECB inspectors delivered in a portal they cannot reach (UC-102) handed over as a report en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I1 (2 points)
solvable with	set of Explains delivering metadata to its users, Explains querying, reporting and analysing metadata

mm-requirements-use-cases I2a: a hybrid metadata architecture, with the live lake metastore as its reason edu:Question

https://knobit.org/id/register/metadata-management#MD-162

dcterms:identifier	MD-162
rdfs:label	mm-requirements-use-cases I2a: a hybrid metadata architecture, with the live lake metastore as its reason en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I2 (2 points)
solvable with	set of Explains the types of metadata architecture

mm-requirements-use-cases I2b: strategy scope from the use cases, not from what the licence can reach edu:Question

https://knobit.org/id/register/metadata-management#MD-163

dcterms:identifier	MD-163
rdfs:label	mm-requirements-use-cases I2b: strategy scope from the use cases, not from what the licence can reach en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I2 (2 points)
solvable with	set of Explains the scope of a metadata strategy

mm-requirements-use-cases I2c: the principle that metadata is the catalogue team's job replaced by business accountability edu:Question

https://knobit.org/id/register/metadata-management#MD-164

dcterms:identifier	MD-164
rdfs:label	mm-requirements-use-cases I2c: the principle that metadata is the catalogue team's job replaced by business accountability en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I2 (2 points)
solvable with	set of Explains the goals and principles of metadata management

mm-requirements-use-cases I2d: phases that start with stakeholder interviews and a source assessment and implement by priority edu:Question

https://knobit.org/id/register/metadata-management#MD-165

dcterms:identifier	MD-165
rdfs:label	mm-requirements-use-cases I2d: phases that start with stakeholder interviews and a source assessment and implement by priority en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I2 (2 points)
solvable with	set of Explains the steps of building a metadata strategy

mm-requirements-use-cases I3a: a business sponsor and allocated, trained curation effort edu:Question

https://knobit.org/id/register/metadata-management#MD-166

dcterms:identifier	MD-166
rdfs:label	mm-requirements-use-cases I3a: a business sponsor and allocated, trained curation effort en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I3 (1.5 points)
solvable with	set of Explains the organisational change metadata management needs

mm-requirements-use-cases I3b: metrics of metadata against its use, not counts of objects harvested edu:Question

https://knobit.org/id/register/metadata-management#MD-167

dcterms:identifier	MD-167
rdfs:label	mm-requirements-use-cases I3b: metrics of metadata against its use, not counts of objects harvested en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I3 (1.5 points)
solvable with	set of Explains metadata management metrics

mm-requirements-use-cases I3c: the risks of poor metadata the draft shows, beyond licence cost edu:Question

https://knobit.org/id/register/metadata-management#MD-168

dcterms:identifier	MD-168
rdfs:label	mm-requirements-use-cases I3c: the risks of poor metadata the draft shows, beyond licence cost en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I3 (1.5 points)
solvable with	set of Explains readiness and risk assessment for metadata management

Rules of definition edu:Question

https://knobit.org/id/register/metadata-management#MD-1801

dcterms:identifier	MD-1801
rdfs:label	Rules of definition en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:learningResourceType	multiple_choice
schema:text	Which description consists of the main parts of a definition? (a) the nearest superordinate concept and the distinguishing characteristic; (b) only the name of the concept; (c) repeating the concept; (d) only an example en
solvable with	set of Explains the rules for defining a concept

mm-metamodel C1a: business meaning moved off the column class to the term link edu:Question

https://knobit.org/id/register/metadata-management#MD-250

dcterms:identifier	MD-250
rdfs:label	mm-metamodel C1a: business meaning moved off the column class to the term link en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C1 (2 points)
solvable with	set of Recognises business meaning stored on a technical metadata class

mm-metamodel C1b: column represents one term (N:1), per the 11179-3 data element edu:Question

https://knobit.org/id/register/metadata-management#MD-251

dcterms:identifier	MD-251
rdfs:label	mm-metamodel C1b: column represents one term (N:1), per the 11179-3 data element en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C1 (2 points)
solvable with	set of Explains the ISO/IEC 11179-3 data element structure

mm-metamodel C2a: term class holds the glossary name and steward-owned definition, read-only edu:Question

https://knobit.org/id/register/metadata-management#MD-252

dcterms:identifier	MD-252
rdfs:label	mm-metamodel C2a: term class holds the glossary name and steward-owned definition, read-only en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C2 (2 points)
solvable with	set of Recognises a glossary term class unable to hold the term unchanged

mm-metamodel C2b: term class keeps id and steward and gains the trace links edu:Question

https://knobit.org/id/register/metadata-management#MD-253

dcterms:identifier	MD-253
rdfs:label	mm-metamodel C2b: term class keeps id and steward and gains the trace links en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C2 (2 points)
solvable with	set of Recognises a glossary term class unable to hold the term unchanged

mm-metamodel C3a: two classes for one table merged, the other name an alias edu:Question

https://knobit.org/id/register/metadata-management#MD-254

dcterms:identifier	MD-254
rdfs:label	mm-metamodel C3a: two classes for one table merged, the other name an alias en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C3 (2 points)
solvable with	set of Recognises two metamodel classes for one thing

mm-metamodel C3b: report-uses-column relationship given its populating sources edu:Question

https://knobit.org/id/register/metadata-management#MD-255

dcterms:identifier	MD-255
rdfs:label	mm-metamodel C3b: report-uses-column relationship given its populating sources en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C3 (2 points)
solvable with	set of Recognises a metamodel relationship no source can populate

mm-metamodel I1a: people-written report purpose given an owner edu:Question

https://knobit.org/id/register/metadata-management#MD-256

dcterms:identifier	MD-256
rdfs:label	mm-metamodel I1a: people-written report purpose given an owner en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I1 (2 points)
solvable with	set of Recognises a people-written metadata attribute with no owner

mm-metamodel I1b: class serving no use case retired or raised to stage 1 edu:Question

https://knobit.org/id/register/metadata-management#MD-257

dcterms:identifier	MD-257
rdfs:label	mm-metamodel I1b: class serving no use case retired or raised to stage 1 en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I1 (2 points)
solvable with	set of Recognises a metamodel class serving no use case

mm-metamodel I2: quality result class moved to the operational layer edu:Question

https://knobit.org/id/register/metadata-management#MD-258

dcterms:identifier	MD-258
rdfs:label	mm-metamodel I2: quality result class moved to the operational layer en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I2 (1 points)
solvable with	set of Explains metamodel layers, classes and relationships

mm-metamodel I3: manual step mapped to prov:Activity edu:Question

https://knobit.org/id/register/metadata-management#MD-259

dcterms:identifier	MD-259
rdfs:label	mm-metamodel I3: manual step mapped to prov:Activity en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I3 (1 points)
solvable with	set of Explains the PROV-O provenance model

mm-metamodel I4: shared data set split from its deliveries (dcat:Distribution) edu:Question

https://knobit.org/id/register/metadata-management#MD-260

dcterms:identifier	MD-260
rdfs:label	mm-metamodel I4: shared data set split from its deliveries (dcat:Distribution) en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I4 (1 points)
solvable with	set of Explains the DCAT 3 catalogue vocabulary

business-terms C1: homonym split into two terms edu:Question

https://knobit.org/id/register/metadata-management#MD-301

dcterms:identifier	MD-301
rdfs:label	business-terms C1: homonym split into two terms en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C1 (3 points)
solvable with	set of Recognises an ambiguous business term in a data requirement, Writes an intensional definition of a business term

business-terms C2a: too-narrow definition widened edu:Question

https://knobit.org/id/register/metadata-management#MD-302

dcterms:identifier	MD-302
rdfs:label	business-terms C2a: too-narrow definition widened en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C2 (2 points)
solvable with	set of Recognises a definition too narrow for its concept

business-terms C2b: synonym recorded, not a separate term edu:Question

https://knobit.org/id/register/metadata-management#MD-303

dcterms:identifier	MD-303
rdfs:label	business-terms C2b: synonym recorded, not a separate term en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C2 (2 points)
solvable with	set of Recognises inconsistent terminology across the register

business-terms C3: unstated bases raised, not invented edu:Question

https://knobit.org/id/register/metadata-management#MD-304

dcterms:identifier	MD-304
rdfs:label	business-terms C3: unstated bases raised, not invented en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C3 (2 points)
solvable with	set of Recognises a guess recorded as fact

business-terms I1a: definitions defined by each other fixed edu:Question

https://knobit.org/id/register/metadata-management#MD-305

dcterms:identifier	MD-305
rdfs:label	business-terms I1a: definitions defined by each other fixed en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I1 (2 points)
solvable with	set of Recognises terms defined by each other

business-terms I1b: definition restating its name fixed edu:Question

https://knobit.org/id/register/metadata-management#MD-306

dcterms:identifier	MD-306
rdfs:label	business-terms I1b: definition restating its name fixed en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I1 (2 points)
solvable with	set of Recognises a definition circular within itself

business-terms I2: negative definition rewritten positively edu:Question

https://knobit.org/id/register/metadata-management#MD-307

dcterms:identifier	MD-307
rdfs:label	business-terms I2: negative definition rewritten positively en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I2 (1 points)
solvable with	set of Recognises a negative definition, Writes an intensional definition of a business term

business-terms I3: rule and process content moved out of a definition edu:Question

https://knobit.org/id/register/metadata-management#MD-308

dcterms:identifier	MD-308
rdfs:label	business-terms I3: rule and process content moved out of a definition en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I3 (2 points)
solvable with	set of Recognises a definition carrying non-defining content

business-terms I4a: hidden definition extracted edu:Question

https://knobit.org/id/register/metadata-management#MD-309

dcterms:identifier	MD-309
rdfs:label	business-terms I4a: hidden definition extracted en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I4 (2 points)
solvable with	set of Recognises a hidden definition of a second concept

business-terms I4b: property-only basis generalised edu:Question

https://knobit.org/id/register/metadata-management#MD-310

dcterms:identifier	MD-310
rdfs:label	business-terms I4b: property-only basis generalised en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I4 (2 points)
solvable with	set of Recognises a definition too narrow for its concept

business-terms I5: incomplete list replaced by an intensional definition edu:Question

https://knobit.org/id/register/metadata-management#MD-311

dcterms:identifier	MD-311
rdfs:label	business-terms I5: incomplete list replaced by an intensional definition en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I5 (1 points)
solvable with	set of Recognises an incomplete extensional definition, Writes an intensional definition of a business term

business-terms I6: too-broad definition narrowed edu:Question

https://knobit.org/id/register/metadata-management#MD-312

dcterms:identifier	MD-312
rdfs:label	business-terms I6: too-broad definition narrowed en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I6 (1 points)
solvable with	set of Recognises a definition too broad for its concept, Writes an intensional definition of a business term

business-terms I7: definitions pass substitution edu:Question

https://knobit.org/id/register/metadata-management#MD-313

dcterms:identifier	MD-313
rdfs:label	business-terms I7: definitions pass substitution en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I7 (1 points)
solvable with	set of Recognises a definition failing the substitution test

business-terms Q1: every term traced only to requirements using it edu:Question

https://knobit.org/id/register/metadata-management#MD-314

dcterms:identifier	MD-314
rdfs:label	business-terms Q1: every term traced only to requirements using it en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	Q1 (1 points)
solvable with	set of Recognises a missing or wrong requirement trace

mm-glossary-quality C1: three terms defined in a ring found and the ring broken edu:Question

https://knobit.org/id/register/metadata-management#MD-350

dcterms:identifier	MD-350
rdfs:label	mm-glossary-quality C1: three terms defined in a ring found and the ring broken en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C1 (2 points)
solvable with	set of Recognises terms defined by each other

mm-glossary-quality C2a: lending-only interest rate generalised for deposits edu:Question

https://knobit.org/id/register/metadata-management#MD-351

dcterms:identifier	MD-351
rdfs:label	mm-glossary-quality C2a: lending-only interest rate generalised for deposits en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C2 (2 points)
solvable with	set of Recognises a general concept tied to one subject field

mm-glossary-quality C2b: genuinely card-specific term kept with its field mark edu:Question

https://knobit.org/id/register/metadata-management#MD-352

dcterms:identifier	MD-352
rdfs:label	mm-glossary-quality C2b: genuinely card-specific term kept with its field mark en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C2 (2 points)
solvable with	set of Explains subject fields and field-specific concepts

mm-glossary-quality C3a: statement line freed from current account statements edu:Question

https://knobit.org/id/register/metadata-management#MD-353

dcterms:identifier	MD-353
rdfs:label	mm-glossary-quality C3a: statement line freed from current account statements en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C3 (2 points)
solvable with	set of Recognises a part concept tied to one whole

mm-glossary-quality C3b: kind-of and part-of relations in the concept system corrected edu:Question

https://knobit.org/id/register/metadata-management#MD-354

dcterms:identifier	MD-354
rdfs:label	mm-glossary-quality C3b: kind-of and part-of relations in the concept system corrected en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C3 (2 points)
solvable with	set of Explains generic and partitive concept relations

mm-glossary-quality I1a: non-essential characteristics dropped from a too-narrow definition edu:Question

https://knobit.org/id/register/metadata-management#MD-355

dcterms:identifier	MD-355
rdfs:label	mm-glossary-quality I1a: non-essential characteristics dropped from a too-narrow definition en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I1 (2 points)
solvable with	set of Recognises a definition too narrow for its concept

mm-glossary-quality I1b: delimiting characteristic added to a too-broad definition, sound one kept edu:Question

https://knobit.org/id/register/metadata-management#MD-356

dcterms:identifier	MD-356
rdfs:label	mm-glossary-quality I1b: delimiting characteristic added to a too-broad definition, sound one kept en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I1 (2 points)
solvable with	set of Explains intensional definition by superordinate concept and delimiting characteristics, Explains essential and delimiting characteristics

mm-glossary-quality I2a: definition without a superordinate concept recast edu:Question

https://knobit.org/id/register/metadata-management#MD-357

dcterms:identifier	MD-357
rdfs:label	mm-glossary-quality I2a: definition without a superordinate concept recast en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I2 (2 points)
solvable with	set of Recognises a definition without a superordinate concept

mm-glossary-quality I2b: rate defined as a set of customers fails substitution edu:Question

https://knobit.org/id/register/metadata-management#MD-358

dcterms:identifier	MD-358
rdfs:label	mm-glossary-quality I2b: rate defined as a set of customers fails substitution en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I2 (2 points)
solvable with	set of Recognises a definition failing the substitution test

mm-glossary-quality I3a: incomplete member list replaced by an intensional definition edu:Question

https://knobit.org/id/register/metadata-management#MD-359

dcterms:identifier	MD-359
rdfs:label	mm-glossary-quality I3a: incomplete member list replaced by an intensional definition en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I3 (2 points)
solvable with	set of Recognises an incomplete extensional definition

mm-glossary-quality I3b: complete extensional definition left alone edu:Question

https://knobit.org/id/register/metadata-management#MD-360

dcterms:identifier	MD-360
rdfs:label	mm-glossary-quality I3b: complete extensional definition left alone en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I3 (2 points)
solvable with	set of Explains extensional definitions and their completeness

mm-glossary-quality I4: two names for one concept merged under the preferred term edu:Question

https://knobit.org/id/register/metadata-management#MD-361

dcterms:identifier	MD-361
rdfs:label	mm-glossary-quality I4: two names for one concept merged under the preferred term en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I4 (1 points)
solvable with	set of Explains equivalence relations and preferred terms

mm-glossary-quality I5a: compound requirement split, singular ones left edu:Question

https://knobit.org/id/register/metadata-management#MD-362

dcterms:identifier	MD-362
rdfs:label	mm-glossary-quality I5a: compound requirement split, singular ones left en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I5 (2 points)
solvable with	set of Explains singular and unambiguous requirement statements

mm-glossary-quality I5b: approved requirement without source or owner reported edu:Question

https://knobit.org/id/register/metadata-management#MD-363

dcterms:identifier	MD-363
rdfs:label	mm-glossary-quality I5b: approved requirement without source or owner reported en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I5 (2 points)
solvable with	set of Explains requirement attributes and traceability

mm-catalogue-entries C1a: column description restating its name found and rewritten from the steward's note edu:Question

https://knobit.org/id/register/metadata-management#MD-450

dcterms:identifier	MD-450
rdfs:label	mm-catalogue-entries C1a: column description restating its name found and rewritten from the steward's note en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C1 (2 points)
solvable with	set of Recognises a catalogue description restating the name

mm-catalogue-entries C1b: table description restating its name found and rewritten to say what a row is edu:Question

https://knobit.org/id/register/metadata-management#MD-451

dcterms:identifier	MD-451
rdfs:label	mm-catalogue-entries C1b: table description restating its name found and rewritten to say what a row is en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C1 (2 points)
solvable with	set of Recognises a catalogue description restating the name

mm-catalogue-entries C2a: owner named as a person who has left replaced by a role with a current holder edu:Question

https://knobit.org/id/register/metadata-management#MD-452

dcterms:identifier	MD-452
rdfs:label	mm-catalogue-entries C2a: owner named as a person who has left replaced by a role with a current holder en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C2 (2 points)
solvable with	set of Recognises a catalogue owner who has left or is not a role

mm-catalogue-entries C2b: owner role whose holder has left reported or raised, no successor invented edu:Question

https://knobit.org/id/register/metadata-management#MD-453

dcterms:identifier	MD-453
rdfs:label	mm-catalogue-entries C2b: owner role whose holder has left reported or raised, no successor invented en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C2 (2 points)
solvable with	set of Recognises a catalogue owner who has left or is not a role

mm-catalogue-entries C3a: classification disagreeing with the register row it cites replaced by data-security's level edu:Question

https://knobit.org/id/register/metadata-management#MD-454

dcterms:identifier	MD-454
rdfs:label	mm-catalogue-entries C3a: classification disagreeing with the register row it cites replaced by data-security's level en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C3 (2 points)
solvable with	set of Recognises a catalogue classification disagreeing with data-security

mm-catalogue-entries C3b: classification set in the catalogue with no source taken from the register edu:Question

https://knobit.org/id/register/metadata-management#MD-455

dcterms:identifier	MD-455
rdfs:label	mm-catalogue-entries C3b: classification set in the catalogue with no source taken from the register en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C3 (2 points)
solvable with	set of Recognises a catalogue classification disagreeing with data-security

mm-catalogue-entries I1a: entry harvested longer ago than the nightly schedule allows reported stale edu:Question

https://knobit.org/id/register/metadata-management#MD-456

dcterms:identifier	MD-456
rdfs:label	mm-catalogue-entries I1a: entry harvested longer ago than the nightly schedule allows reported stale en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I1 (1.5 points)
solvable with	set of Recognises a stale catalogue entry

mm-catalogue-entries I1b: stale entry flagged and re-harvest asked for, not repaired by hand or retired edu:Question

https://knobit.org/id/register/metadata-management#MD-457

dcterms:identifier	MD-457
rdfs:label	mm-catalogue-entries I1b: stale entry flagged and re-harvest asked for, not repaired by hand or retired en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I1 (1.5 points)
solvable with	set of Explains metadata currency against the harvest schedule

mm-catalogue-entries I2a: two entries with one physical reference reported, same-name report left alone edu:Question

https://knobit.org/id/register/metadata-management#MD-458

dcterms:identifier	MD-458
rdfs:label	mm-catalogue-entries I2a: two entries with one physical reference reported, same-name report left alone en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I2 (1.5 points)
solvable with	set of Recognises two catalogue entries for one object

mm-catalogue-entries I2b: duplicate entries merged into one entry with both sources, the other retired edu:Question

https://knobit.org/id/register/metadata-management#MD-459

dcterms:identifier	MD-459
rdfs:label	mm-catalogue-entries I2b: duplicate entries merged into one entry with both sources, the other retired en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I2 (1.5 points)
solvable with	set of Explains one catalogue entry per object

mm-catalogue-entries I3: business column with no glossary term linked, technical column left without one edu:Question

https://knobit.org/id/register/metadata-management#MD-460

dcterms:identifier	MD-460
rdfs:label	mm-catalogue-entries I3: business column with no glossary term linked, technical column left without one en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I3 (1 points)
solvable with	set of Recognises a business column with no glossary term

mm-catalogue-entries I4: manual-step entry with no location, procedure or owner completed from the owner's note edu:Question

https://knobit.org/id/register/metadata-management#MD-461

dcterms:identifier	MD-461
rdfs:label	mm-catalogue-entries I4: manual-step entry with no location, procedure or owner completed from the owner's note en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I4 (1 points)
solvable with	set of Recognises a manual-step entry nobody could find or repeat

mm-column-lineage C1: workbook re-keying drawn as a manual path, not an automated import edu:Question

https://knobit.org/id/register/metadata-management#MD-550

dcterms:identifier	MD-550
rdfs:label	mm-column-lineage C1: workbook re-keying drawn as a manual path, not an automated import en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C1 (2 points)
solvable with	set of Recognises a manual step missing from a lineage path

mm-column-lineage C2: view columns resolved to base columns with the view logic edu:Question

https://knobit.org/id/register/metadata-management#MD-551

dcterms:identifier	MD-551
rdfs:label	mm-column-lineage C2: view columns resolved to base columns with the view logic en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C2 (2 points)
solvable with	set of Recognises lineage ending at a view

mm-column-lineage C3: table-level edge to the NPL ratio replaced by column edges edu:Question

https://knobit.org/id/register/metadata-management#MD-552

dcterms:identifier	MD-552
rdfs:label	mm-column-lineage C3: table-level edge to the NPL ratio replaced by column edges en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C3 (2 points)
solvable with	set of Recognises a table-level lineage edge where column level is needed

mm-column-lineage I1a: edge from an uncatalogued column re-pointed to the staging column edu:Question

https://knobit.org/id/register/metadata-management#MD-553

dcterms:identifier	MD-553
rdfs:label	mm-column-lineage I1a: edge from an uncatalogued column re-pointed to the staging column en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I1 (2 points)
solvable with	set of Recognises a broken lineage hop

mm-column-lineage I1b: source-to-staging edge cites the mapping it implements edu:Question

https://knobit.org/id/register/metadata-management#MD-554

dcterms:identifier	MD-554
rdfs:label	mm-column-lineage I1b: source-to-staging edge cites the mapping it implements en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I1 (2 points)
solvable with	set of Recognises an integration lineage edge without its mapping

mm-column-lineage I2: placeholder logic replaced by the job logic edu:Question

https://knobit.org/id/register/metadata-management#MD-555

dcterms:identifier	MD-555
rdfs:label	mm-column-lineage I2: placeholder logic replaced by the job logic en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I2 (1 points)
solvable with	set of Recognises a lineage edge with placeholder logic

mm-impact-analysis C1: Board arrears report two hops past the view added with its owner edu:Question

https://knobit.org/id/register/metadata-management#MD-650

dcterms:identifier	MD-650
rdfs:label	mm-impact-analysis C1: Board arrears report two hops past the view added with its owner en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C1 (3 points)
solvable with	set of Recognises a downstream report missed through a view

mm-impact-analysis C2a: IFRS 9 staging workbook past the manual export added with its owner edu:Question

https://knobit.org/id/register/metadata-management#MD-651

dcterms:identifier	MD-651
rdfs:label	mm-impact-analysis C2a: IFRS 9 staging workbook past the manual export added with its owner en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C2 (2 points)
solvable with	set of Recognises an impacted object missed through a manual step

mm-impact-analysis C2b: FINREP return past the re-keying step added with its owner edu:Question

https://knobit.org/id/register/metadata-management#MD-652

dcterms:identifier	MD-652
rdfs:label	mm-impact-analysis C2b: FINREP return past the re-keying step added with its owner en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C2 (2 points)
solvable with	set of Recognises an impacted object missed through a manual step

mm-impact-analysis C3: days past due change classed semantic, effects stated per object edu:Question

https://knobit.org/id/register/metadata-management#MD-653

dcterms:identifier	MD-653
rdfs:label	mm-impact-analysis C3: days past due change classed semantic, effects stated per object en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	C3 (2 points)
solvable with	set of Recognises a semantic change assessed as a schema change

mm-impact-analysis I1a: collections feed with no owner given the register owner edu:Question

https://knobit.org/id/register/metadata-management#MD-654

dcterms:identifier	MD-654
rdfs:label	mm-impact-analysis I1a: collections feed with no owner given the register owner en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I1 (2 points)
solvable with	set of Recognises an impacted object with no owner to notify

mm-impact-analysis I1b: collections dashboard with no action given its owner's action edu:Question

https://knobit.org/id/register/metadata-management#MD-655

dcterms:identifier	MD-655
rdfs:label	mm-impact-analysis I1b: collections dashboard with no action given its owner's action en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I1 (2 points)
solvable with	set of Recognises an impacted object with no action

mm-impact-analysis I2: Mortgage LTV report outside the closure taken out edu:Question

https://knobit.org/id/register/metadata-management#MD-656

dcterms:identifier	MD-656
rdfs:label	mm-impact-analysis I2: Mortgage LTV report outside the closure taken out en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I2 (1 points)
solvable with	set of Recognises an unreached object listed in an impact analysis

mm-impact-analysis I3: authorisation conditional on the owners informed and their actions agreed edu:Question

https://knobit.org/id/register/metadata-management#MD-657

dcterms:identifier	MD-657
rdfs:label	mm-impact-analysis I3: authorisation conditional on the owners informed and their actions agreed en
schema:isPartOf	Metadata management (DAMA-DMBOK2)
schema:isPartOf	I3 (1 points)
solvable with	set of Explains change enablement for data changes

Business drivers edu:LearningOutcome

https://knobit.org/id/register/metadata-management#MV-1

dcterms:description	Why an organisation manages metadata. en
dcterms:identifier	MV-1
dcterms:source	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management, 1.1 en
includes knobit	Explains the business drivers of metadata management
rdfs:label	Business drivers en
schema:isPartOf	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management
skos:notation	1.1

Understand metadata requirements edu:LearningOutcome

https://knobit.org/id/register/metadata-management#MV-10

dcterms:description	The questions users need metadata to answer, and what that needs. en
dcterms:identifier	MV-10
dcterms:source	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management, 2.2 en
includes knobit	Recognises a metadata use case with no metadata serving it
includes knobit	Recognises a needed metadata type with no source
includes knobit	Recognises a metadata use case with no user
includes knobit	Explains use-case-driven metadata requirements
rdfs:label	Understand metadata requirements en
schema:isPartOf	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management
skos:notation	2.2

Define the metadata architecture: create the metamodel edu:LearningOutcome

https://knobit.org/id/register/metadata-management#MV-11

dcterms:description	Classes, attributes and relationships the repository holds, each populated by a source. en
dcterms:identifier	MV-11
dcterms:source	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management, 2.3.1 en
includes knobit	Recognises two metamodel classes for one thing
includes knobit	Recognises a people-written metadata attribute with no owner
includes knobit	Recognises a metamodel relationship no source can populate
includes knobit	Recognises a glossary term class unable to hold the term unchanged
includes knobit	Recognises business meaning stored on a technical metadata class
includes knobit	Recognises a metamodel class serving no use case
includes knobit	Explains metamodel layers, classes and relationships
includes knobit	Explains how a metamodel is populated from metadata sources
rdfs:label	Define the metadata architecture: create the metamodel en
schema:isPartOf	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management
skos:notation	2.3.1

Define the metadata architecture: apply metadata standards edu:LearningOutcome

https://knobit.org/id/register/metadata-management#MV-12

dcterms:description	Industry and international standards for metamodels, registries and resource description. en
dcterms:identifier	MV-12
dcterms:source	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management, 2.3.2 en
includes knobit	Explains the DCAT 3 catalogue vocabulary
includes knobit	Explains the PROV-O provenance model
includes knobit	Explains the standards used for metadata
rdfs:label	Define the metadata architecture: apply metadata standards en
schema:isPartOf	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management
skos:notation	2.3.2

Define the metadata architecture: manage metadata stores edu:LearningOutcome

https://knobit.org/id/register/metadata-management#MV-13

dcterms:description	Operating the repository: loads, schedules, currency, service levels. en
dcterms:identifier	MV-13
dcterms:source	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management, 2.3.3 en
includes knobit	Recognises a stale catalogue entry
includes knobit	Explains metadata currency against the harvest schedule
includes knobit	Explains managing metadata stores
rdfs:label	Define the metadata architecture: manage metadata stores en
schema:isPartOf	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management
skos:notation	2.3.3

Create and maintain metadata edu:LearningOutcome

https://knobit.org/id/register/metadata-management#MV-14

dcterms:description	Curating metadata of known quality: descriptions, owners, terms, status. en
dcterms:identifier	MV-14
dcterms:source	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management, 2.4 en
includes knobit	Recognises inferred metadata published as approved
includes knobit	Recognises a catalogue description restating the name
includes knobit	Recognises a catalogue owner who has left or is not a role
includes knobit	Recognises a business column with no glossary term
includes knobit	Recognises a manual-step entry nobody could find or repeat
rdfs:label	Create and maintain metadata en
schema:isPartOf	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management
skos:notation	2.4

Integrate metadata edu:LearningOutcome

https://knobit.org/id/register/metadata-management#MV-15

dcterms:description	Harvesting and consolidating metadata from many sources into one view. en
dcterms:identifier	MV-15
dcterms:source	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management, 2.4.1 en
includes knobit	Explains metadata capture methods and the freshness each can keep
includes knobit	Recognises a catalogue classification disagreeing with data-security
includes knobit	Recognises two catalogue entries for one object
includes knobit	Explains one catalogue entry per object
rdfs:label	Integrate metadata en
schema:isPartOf	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management
skos:notation	2.4.1

Distribute and deliver metadata edu:LearningOutcome

https://knobit.org/id/register/metadata-management#MV-16

dcterms:description	Getting metadata to the people and tools that use it. en
dcterms:identifier	MV-16
dcterms:source	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management, 2.4.2 en
includes knobit	Explains delivering metadata to its users
rdfs:label	Distribute and deliver metadata en
schema:isPartOf	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management
skos:notation	2.4.2

Query, report and analyse metadata edu:LearningOutcome

https://knobit.org/id/register/metadata-management#MV-17

dcterms:description	Using the repository to answer questions about data. en
dcterms:identifier	MV-17
dcterms:source	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management, 2.5 en
includes knobit	Explains querying, reporting and analysing metadata
rdfs:label	Query, report and analyse metadata en
schema:isPartOf	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management
skos:notation	2.5

Tools edu:LearningOutcome

https://knobit.org/id/register/metadata-management#MV-18

dcterms:description	Metadata repository management tools. en
dcterms:identifier	MV-18
dcterms:source	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management, 3 en
includes knobit	Explains metadata repository management tools
rdfs:label	Tools en
schema:isPartOf	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management
skos:notation	3

Techniques: data lineage edu:LearningOutcome

https://knobit.org/id/register/metadata-management#MV-19

dcterms:description	Tracing data from source to report through every hop. en
dcterms:identifier	MV-19
dcterms:source	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management, 4.1 en
includes knobit	Recognises a broken lineage hop
includes knobit	Recognises lineage ending at a view
includes knobit	Recognises a manual step missing from a lineage path
includes knobit	Recognises a lineage edge with placeholder logic
includes knobit	Recognises an integration lineage edge without its mapping
includes knobit	Recognises a table-level lineage edge where column level is needed
includes knobit	Explains data lineage as a graph of derivations
includes knobit	Explains lineage granularity
includes knobit	Explains view resolution in lineage
includes knobit	Explains BCBS 239 requirements on lineage and manual steps
includes knobit	Explains source-to-target mappings as lineage edges
rdfs:label	Techniques: data lineage en
schema:isPartOf	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management
skos:notation	4.1

Goals and principles edu:LearningOutcome

https://knobit.org/id/register/metadata-management#MV-2

dcterms:description	What metadata management aims at and the principles guiding it. en
dcterms:identifier	MV-2
dcterms:source	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management, 1.2 en
includes knobit	Explains the goals and principles of metadata management
rdfs:label	Goals and principles en
schema:isPartOf	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management
skos:notation	1.2

Techniques: impact analysis edu:LearningOutcome

https://knobit.org/id/register/metadata-management#MV-20

dcterms:description	Finding everything a change reaches and who must act. en
dcterms:identifier	MV-20
dcterms:source	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management, 4.1 en
includes knobit	Recognises a downstream report missed through a view
includes knobit	Recognises an impacted object with no owner to notify
includes knobit	Recognises an impacted object missed through a manual step
includes knobit	Recognises a semantic change assessed as a schema change
includes knobit	Recognises an impacted object with no action
includes knobit	Recognises an unreached object listed in an impact analysis
includes knobit	Explains impact analysis as the downstream closure of lineage
includes knobit	Explains the kinds of data change and their reach
includes knobit	Explains change enablement for data changes
rdfs:label	Techniques: impact analysis en
schema:isPartOf	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management
skos:notation	4.1

Techniques: metadata for big data ingest edu:LearningOutcome

https://knobit.org/id/register/metadata-management#MV-21

dcterms:description	Capturing metadata as data lands in a lake. en
dcterms:identifier	MV-21
dcterms:source	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management, 4.2 en
includes knobit	Explains metadata for big data ingest
rdfs:label	Techniques: metadata for big data ingest en
schema:isPartOf	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management
skos:notation	4.2

Implementation: readiness and risk assessment edu:LearningOutcome

https://knobit.org/id/register/metadata-management#MV-22

dcterms:description	Assessing maturity and risk before starting. en
dcterms:identifier	MV-22
dcterms:source	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management, 5.1 en
includes knobit	Explains readiness and risk assessment for metadata management
rdfs:label	Implementation: readiness and risk assessment en
schema:isPartOf	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management
skos:notation	5.1

Implementation: organisational and cultural change edu:LearningOutcome

https://knobit.org/id/register/metadata-management#MV-23

dcterms:description	Making people curate and use metadata. en
dcterms:identifier	MV-23
dcterms:source	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management, 5.2 en
includes knobit	Explains the organisational change metadata management needs
rdfs:label	Implementation: organisational and cultural change en
schema:isPartOf	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management
skos:notation	5.2

Metadata governance: process controls edu:LearningOutcome

https://knobit.org/id/register/metadata-management#MV-24

dcterms:description	Who curates and approves metadata, and the status an item has until confirmed. en
dcterms:identifier	MV-24
dcterms:source	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management, 6.1 en
includes knobit	Recognises curated metadata with no curator
includes knobit	Recognises inferred metadata published as approved
includes knobit	Explains the registration status of metadata items
includes knobit	Recognises a people-written metadata attribute with no owner
rdfs:label	Metadata governance: process controls en
schema:isPartOf	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management
skos:notation	6.1

Metadata governance: documentation of metadata solutions edu:LearningOutcome

https://knobit.org/id/register/metadata-management#MV-25

dcterms:description	An inventory of metadata sources: what each holds, how it is captured, by whom, how often. en
dcterms:identifier	MV-25
dcterms:source	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management, 6.2 en
includes knobit	Recognises a needed metadata type with no source
includes knobit	Recognises curated metadata with no curator
includes knobit	Recognises a metadata freshness the capture method cannot meet
rdfs:label	Metadata governance: documentation of metadata solutions en
schema:isPartOf	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management
skos:notation	6.2

Metadata governance: standards and guidelines edu:LearningOutcome

https://knobit.org/id/register/metadata-management#MV-26

dcterms:description	The organisation's own rules for metadata, such as how definitions are written. en
dcterms:identifier	MV-26
dcterms:source	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management, 6.3 en
includes knobit	Recognises a catalogue description restating the name
includes knobit	Explains the ISO/IEC 11179-4 rules for data definitions
includes knobit	Explains the standards used for metadata
rdfs:label	Metadata governance: standards and guidelines en
schema:isPartOf	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management
skos:notation	6.3

Metadata governance: metrics edu:LearningOutcome

https://knobit.org/id/register/metadata-management#MV-27

dcterms:description	Measuring metadata management. en
dcterms:identifier	MV-27
dcterms:source	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management, 6.4 en
includes knobit	Explains metadata management metrics
rdfs:label	Metadata governance: metrics en
schema:isPartOf	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management
skos:notation	6.4

Metadata and the types of metadata edu:LearningOutcome

https://knobit.org/id/register/metadata-management#MV-3

dcterms:description	Metadata as data about data, and the business, technical and operational kinds. en
dcterms:identifier	MV-3
dcterms:source	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management, 1.3.1-1.3.2 en
includes knobit	Explains business, technical and operational metadata
rdfs:label	Metadata and the types of metadata en
schema:isPartOf	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management
skos:notation	1.3.1-1.3.2

The ISO/IEC 11179 metadata registry standard edu:LearningOutcome

https://knobit.org/id/register/metadata-management#MV-4

dcterms:description	Registries, registered items, their structure, definitions, roles and registration status. en
dcterms:identifier	MV-4
dcterms:source	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management, 1.3.3 en
includes knobit	Explains the roles of a metadata registry
includes knobit	Explains the registration status of metadata items
includes knobit	Explains the ISO/IEC 11179-3 data element structure
includes knobit	Explains the designation, definition and steward of a registered item
includes knobit	Explains the ISO/IEC 11179-4 rules for data definitions
rdfs:label	The ISO/IEC 11179 metadata registry standard en
schema:isPartOf	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management
skos:notation	1.3.3

Metadata for unstructured data edu:LearningOutcome

https://knobit.org/id/register/metadata-management#MV-5

dcterms:description	Describing documents and content. en
dcterms:identifier	MV-5
dcterms:source	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management, 1.3.4 en
includes knobit	Explains metadata for unstructured data
rdfs:label	Metadata for unstructured data en
schema:isPartOf	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management
skos:notation	1.3.4

Sources of metadata edu:LearningOutcome

https://knobit.org/id/register/metadata-management#MV-6

dcterms:description	The tools and repositories metadata is captured from, and how. en
dcterms:identifier	MV-6
dcterms:source	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management, 1.3.5 en
includes knobit	Recognises a needed metadata type with no source
includes knobit	Explains metadata capture methods and the freshness each can keep
includes knobit	Explains the kinds of metadata sources
rdfs:label	Sources of metadata en
schema:isPartOf	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management
skos:notation	1.3.5

The business glossary as a metadata source edu:LearningOutcome

https://knobit.org/id/register/metadata-management#MV-7

dcterms:description	Business terms with definitions, stewards and links, free of circularity and hidden concepts. en
dcterms:identifier	MV-7
dcterms:source	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management, 1.3.5 en
includes knobit	Recognises an ambiguous business term in a data requirement
includes knobit	Recognises a guess recorded as fact
includes knobit	Recognises inconsistent terminology across the register
includes knobit	Recognises a missing or wrong requirement trace
includes knobit	Recognises a definition circular within itself
includes knobit	Recognises terms defined by each other
includes knobit	Recognises a negative definition
includes knobit	Recognises a definition too broad for its concept
includes knobit	Recognises a definition too narrow for its concept
includes knobit	Recognises a general concept tied to one subject field
includes knobit	Recognises a part concept tied to one whole
includes knobit	Recognises an incomplete extensional definition
includes knobit	Recognises a hidden definition of a second concept
includes knobit	Recognises a definition without a superordinate concept
includes knobit	Recognises a definition carrying non-defining content
includes knobit	Recognises a definition failing the substitution test
includes knobit	Writes an intensional definition of a business term
rdfs:label	The business glossary as a metadata source en
schema:isPartOf	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management
skos:notation	1.3.5

Types of metadata architecture edu:LearningOutcome

https://knobit.org/id/register/metadata-management#MV-8

dcterms:description	Centralised, distributed, hybrid and bi-directional. en
dcterms:identifier	MV-8
dcterms:source	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management, 1.3.6 en
includes knobit	Explains the types of metadata architecture
rdfs:label	Types of metadata architecture en
schema:isPartOf	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management
skos:notation	1.3.6

Define the metadata strategy edu:LearningOutcome

https://knobit.org/id/register/metadata-management#MV-9

dcterms:description	Scope by use case and value, and the steps to a phased plan. en
dcterms:identifier	MV-9
dcterms:source	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management, 2.1 en
includes knobit	Recognises metadata collected for no use case
includes knobit	Recognises a metadata freshness the capture method cannot meet
includes knobit	Explains the scope of a metadata strategy
includes knobit	Explains the steps of building a metadata strategy
rdfs:label	Define the metadata strategy en
schema:isPartOf	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management
skos:notation	2.1

DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management schema:CreativeWork

https://knobit.org/id/register/metadata-management#REF-1

dcterms:identifier	REF-1
dcterms:publisher	DAMA International
dcterms:title	DAMA-DMBOK: Data Management Body of Knowledge, 2nd edition (revised), chapter 12: Metadata Management en
schema:version	2nd edition, revised (DMBOK2/RE)
skos:note	target level: CDMP Practitioner: the Metadata Management specialist exam (DAMA International) en

Used by

assesses learning outcome	Retail bank data catalogue requirements - use cases, metadata sources, capture and strategy (metadata requirements anomaly skills)
schema:hasPart	C1 (3 points)
schema:hasPart	C2 (2 points)
schema:hasPart	C3 (2 points)
schema:hasPart	I1 (2 points)
schema:hasPart	I2 (1 points)
schema:hasPart	I3 (2 points)
schema:hasPart	I4 (2 points)
schema:hasPart	I5 (1 points)
schema:hasPart	I6 (1 points)
schema:hasPart	I7 (1 points)
schema:hasPart	Q1 (1 points)
schema:hasPart	C1 (2 points)
schema:hasPart	C2 (2 points)
schema:hasPart	C3 (2 points)
schema:hasPart	I1 (1.5 points)
schema:hasPart	I2 (1.5 points)
schema:hasPart	I3 (1 points)
schema:hasPart	I4 (1 points)
schema:hasPart	C1 (2 points)
schema:hasPart	C2 (2 points)
schema:hasPart	C3 (2 points)
schema:hasPart	I1 (2 points)
schema:hasPart	I2 (1 points)
schema:hasPart	C1 (2 points)
schema:hasPart	C2 (2 points)
schema:hasPart	C3 (2 points)
schema:hasPart	I1 (2 points)
schema:hasPart	I2 (2 points)
schema:hasPart	I3 (2 points)
schema:hasPart	I4 (1 points)
schema:hasPart	I5 (2 points)
schema:hasPart	C1 (3 points)
schema:hasPart	C2 (2 points)
schema:hasPart	C3 (2 points)
schema:hasPart	I1 (2 points)
schema:hasPart	I2 (1 points)
schema:hasPart	I3 (1 points)
schema:hasPart	C1 (2 points)
schema:hasPart	C2 (2 points)
schema:hasPart	C3 (2 points)
schema:hasPart	I1 (2 points)
schema:hasPart	I2 (1 points)
schema:hasPart	I3 (1 points)
schema:hasPart	I4 (1 points)
schema:hasPart	C1 (3 points)
schema:hasPart	C2 (3 points)
schema:hasPart	C3 (2 points)
schema:hasPart	I1 (2 points)
schema:hasPart	I2 (2 points)
schema:hasPart	I3 (1.5 points)
schema:isPartOf	Recognises an ambiguous business term in a data requirement
schema:isPartOf	Recognises a guess recorded as fact
schema:isPartOf	Recognises inconsistent terminology across the register
schema:isPartOf	Recognises a missing or wrong requirement trace
schema:isPartOf	Explains singular and unambiguous requirement statements
schema:isPartOf	Explains requirement attributes and traceability
schema:isPartOf	Explains intensional definition by superordinate concept and delimiting characteristics
schema:isPartOf	Explains generic and partitive concept relations
schema:isPartOf	Explains equivalence relations and preferred terms
schema:isPartOf	Explains the rules for defining a concept
schema:isPartOf	Recognises a metadata use case with no metadata serving it
schema:isPartOf	Recognises metadata collected for no use case
schema:isPartOf	Recognises a needed metadata type with no source
schema:isPartOf	Recognises curated metadata with no curator
schema:isPartOf	Recognises a metadata freshness the capture method cannot meet
schema:isPartOf	Recognises a metadata use case with no user
schema:isPartOf	Recognises inferred metadata published as approved
schema:isPartOf	Explains use-case-driven metadata requirements
schema:isPartOf	Explains business, technical and operational metadata
schema:isPartOf	Explains metadata capture methods and the freshness each can keep
schema:isPartOf	Explains the roles of a metadata registry
schema:isPartOf	Explains the registration status of metadata items
schema:isPartOf	Explains the scope of a metadata strategy
schema:isPartOf	Recognises two metamodel classes for one thing
schema:isPartOf	Recognises a people-written metadata attribute with no owner
schema:isPartOf	Recognises a metamodel relationship no source can populate
schema:isPartOf	Recognises a glossary term class unable to hold the term unchanged
schema:isPartOf	Recognises business meaning stored on a technical metadata class
schema:isPartOf	Recognises a metamodel class serving no use case
schema:isPartOf	Explains metamodel layers, classes and relationships
schema:isPartOf	Explains the ISO/IEC 11179-3 data element structure
schema:isPartOf	Explains the designation, definition and steward of a registered item
schema:isPartOf	Explains the DCAT 3 catalogue vocabulary
schema:isPartOf	Explains the PROV-O provenance model
schema:isPartOf	Explains how a metamodel is populated from metadata sources
schema:isPartOf	Recognises a definition circular within itself
schema:isPartOf	Recognises terms defined by each other
schema:isPartOf	Recognises a negative definition
schema:isPartOf	Recognises a definition too broad for its concept
schema:isPartOf	Recognises a definition too narrow for its concept
schema:isPartOf	Recognises a general concept tied to one subject field
schema:isPartOf	Recognises a part concept tied to one whole
schema:isPartOf	Recognises an incomplete extensional definition
schema:isPartOf	Recognises a hidden definition of a second concept
schema:isPartOf	Recognises a definition without a superordinate concept
schema:isPartOf	Recognises a definition carrying non-defining content
schema:isPartOf	Recognises a definition failing the substitution test
schema:isPartOf	Writes an intensional definition of a business term
schema:isPartOf	Explains the substitution principle for definitions
schema:isPartOf	Explains extensional definitions and their completeness
schema:isPartOf	Explains circularity in definitions and concept systems
schema:isPartOf	Explains essential and delimiting characteristics
schema:isPartOf	Explains subject fields and field-specific concepts
schema:isPartOf	Recognises a catalogue description restating the name
schema:isPartOf	Recognises a catalogue owner who has left or is not a role
schema:isPartOf	Recognises a catalogue classification disagreeing with data-security
schema:isPartOf	Recognises a business column with no glossary term
schema:isPartOf	Recognises a stale catalogue entry
schema:isPartOf	Recognises a manual-step entry nobody could find or repeat
schema:isPartOf	Recognises two catalogue entries for one object
schema:isPartOf	Explains the ISO/IEC 11179-4 rules for data definitions
schema:isPartOf	Explains a catalogue owner as a role with a current holder
schema:isPartOf	Explains a classification shown by reference to data-security
schema:isPartOf	Explains metadata currency against the harvest schedule
schema:isPartOf	Explains one catalogue entry per object
schema:isPartOf	Recognises a broken lineage hop
schema:isPartOf	Recognises lineage ending at a view
schema:isPartOf	Recognises a manual step missing from a lineage path
schema:isPartOf	Recognises a lineage edge with placeholder logic
schema:isPartOf	Recognises an integration lineage edge without its mapping
schema:isPartOf	Recognises a table-level lineage edge where column level is needed
schema:isPartOf	Explains data lineage as a graph of derivations
schema:isPartOf	Explains lineage granularity
schema:isPartOf	Explains view resolution in lineage
schema:isPartOf	Explains BCBS 239 requirements on lineage and manual steps
schema:isPartOf	Explains source-to-target mappings as lineage edges
schema:isPartOf	Recognises a downstream report missed through a view
schema:isPartOf	Recognises an impacted object with no owner to notify
schema:isPartOf	Recognises an impacted object missed through a manual step
schema:isPartOf	Recognises a semantic change assessed as a schema change
schema:isPartOf	Recognises an impacted object with no action
schema:isPartOf	Recognises an unreached object listed in an impact analysis
schema:isPartOf	Explains impact analysis as the downstream closure of lineage
schema:isPartOf	Explains the kinds of data change and their reach
schema:isPartOf	Explains change enablement for data changes
schema:isPartOf	Explains the business drivers of metadata management
schema:isPartOf	Explains the goals and principles of metadata management
schema:isPartOf	Explains metadata for unstructured data
schema:isPartOf	Explains the kinds of metadata sources
schema:isPartOf	Explains the types of metadata architecture
schema:isPartOf	Explains the steps of building a metadata strategy
schema:isPartOf	Explains the standards used for metadata
schema:isPartOf	Explains managing metadata stores
schema:isPartOf	Explains delivering metadata to its users
schema:isPartOf	Explains querying, reporting and analysing metadata
schema:isPartOf	Explains metadata repository management tools
schema:isPartOf	Explains metadata for big data ingest
schema:isPartOf	Explains readiness and risk assessment for metadata management
schema:isPartOf	Explains the organisational change metadata management needs
schema:isPartOf	Explains metadata management metrics