I2 (2 points)
https://knobit.org/id/task/mm-requirements-use-cases/I2
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/I2 |
| rdfs:label | I2 (2 points) en |
| schema:hasPart | mm-requirements-use-cases I2a: a hybrid metadata architecture, with the live lake metastore as its reason |
| schema:hasPart | mm-requirements-use-cases I2b: strategy scope from the use cases, not from what the licence can reach |
| schema:hasPart | mm-requirements-use-cases I2c: the principle that metadata is the catalogue team's job replaced by business accountability |
| schema:hasPart | mm-requirements-use-cases I2d: phases that start with stakeholder interviews and a source assessment and implement by priority |
| schema:identifier | I2 |
| schema:position | 5 |
| schema:text | The strategy's architecture, scope, principles and plan, 0.5 each. (a) architecture hybrid, with the reason: a central repository for the harvested and curated metadata, and the lake metastore queried live because its metadata changes faster than a once-a-day scan can copy. (b) scope starts from the use cases - metadata is captured where a use case justifies its capture cost and staleness - not from every system the licence can reach. (c) The principle that metadata is the catalogue team's job is replaced by business accountability - stewards and curators in the business, the catalogue team running the harvesting and the tool - and the two clean principles are kept. (d) The phases begin by confirming the use cases with their users (stakeholder interviews) and assessing the existing metadata sources, design the future architecture, and implement in phases by use case priority - not scan everything, then go live for all. en |