Storyline: Search data in metadata

Owned by Health-RI
Aug 23, 2024
3 min read

DATE: 23-08-2024 STATUS: ADOPTED

 

This article describes the storyline search data in metadata.

A data user can use the researcher portal to search for data that fits the research question. The search can become specific by using filters, and questions can be asked to the data holder by means of a direct line. In the case of public data, a dataset is readily available for research. In the case of non-public data, the data usage can start a follow-up process: requesting data.

See https://health-ri.atlassian.net/wiki/spaces/HA/pages/164497955 for the collaboration diagram of this storyline

Comments

  •  The choice for the use of , “diamond” (or junctions in ArchiMate) needs to be tightened up later. Perhaps the information layer is not suitable for showing these "choices", but we can show this in the application layer.

  • Surveillance should take place based on searches. In the past, it has already been shown that a very extensive search option on (combinations of) data can already lead to results that in themselves lead to in-depth insight into the collected data, whereby even publication of new insights based on access to only the catalog / portal becomes possible.

  • Feasibility studies are not (yet) included in this storyline at the time of writing.

Precondition

  • There is a catalogue that regularly and/or triggered by a search retrieves the latest state of affairs from the affiliated data providers (FAIR data point registers and/or FAIR data points).

  • The data user has a motivation to look for data

    • A research proposal is made for which it is necessary to find out which data can be used

    • There is already a research proposal for which useful data is being sought.

Process model

  1. The data guide gives the data user a list of metadata of datasets. Within this list, multiple data categories are available (think of different data types, institutes, and research areas).

  2. The data guide can apply filters for the data user to the search to make the results as relevant as possible for the desired research.

  3. When inspecting a specific dataset (from the result list) further, there are three possibilities: the dataset is either publicly accessible or requires authentication to check the (implicit) authorization of the data user or requires an (explicit authorization by means of) approved request from the data user.

    1. If the dataset is publicly accessible, the dataset can be downloaded directly.

    2. If (part of) the metadata of the dataset is not publicly accessible but can be made available as a data user belonging to implicitly authorized users or user groups, the data user must authenticate and that part of the metadata of the dataset is then available.

    3. If (part of) the metadata of the dataset is not publicly accessible and can only be made available to data users after an approved request.

  4. With successful identification, authentication and correct authorization, the data user can view more metadata of the dataset.

  5. The data user can ask detailed questions directly to the data provider of a dataset, which can answer these questions.

  6. The data user can choose to start a request for the dataset (by means of Storyline: Request data ).

Postcondition

  • The data user has found a number of datasets that

    • or are publicly available and can be picked up immediately

    • or must be requested from the data holder

Process diagram “search data in metadata”