| Status | ||||
|---|---|---|---|---|
|
Short description
Collecting and analyzing the main requirements of your domain involves different methods of gathering the requirements to identify key metadata elements that will improve dataset accessibility and usability. This step is mainly about understanding what users and stakeholders from your domain need to quickly discover data(sets) of their interest in a catalogue. These requirements can be formulated in the form of small user stories and/or competency questions (QC’s, see below) to approach this from a user-centered perspective. From these stories or QC’s key metadata elements (requirements) can be extracted. Analyzing these requirements helps to decide which are the most important for creating domain specific metadata fields. Prioritizing helps to focus on what is essential, making the metadata schema aligned with the domain’s needs.
Note that all kind of domain metadata schemas, information models, ontologies and vocabularies may exist already. Analyzing this is part of the next step. The current step is important to align this existing information, and the modeling part, with the domain’s (user) needs.
Deliverables
Deliverable | Description |
|---|---|
Requirements document | A comprehensive document outlining the metadata requirements gathered from stakeholders, in the form of competency questions. |
Scope statement | A clear statement defining the scope and boundaries of the metadata schema. |