...
This step is mainly about understanding what users and stakeholders from your domain need to quickly discover or preselect 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’sCQs, see below Examples step 2 ) to approach this from a user-centered perspective. From these stories or QC’s CQs key metadata elements (requirements) can be extracted. Analyzing these requirements helps to decide which are the most important for creating domain specific metadata fields.
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 understand the domain’s user’s needneeds, so that in next steps this can be effectively incorporated in the modeling.
...