/
Metroline Step: Use ontologies in the data model

Metroline Step: Use ontologies in the data model

status: On Hold On 17-9-2024 it was decided to put this page on hold and focus on describing the petal process first. When that part is finished, parts of the information (see e.g. step 4) will be generalised for this page.

‘Start with a great quote from, for example, a paper, between single quotes, in italic.' (source as a hyperlink between parenthesis)

In layman’s terms (Jip en Janneke), add an easy to follow summary, using around three sentences.

Short description 

Isn’t this part of the “Create or reuse a semantic (meta)data model” step?

Skipping for now…

[FAIRopoly]

This step aims at assigning machine-readable terms from existing ontologies to metadata and CDEs. Uniform Resource Identifiers (URIs) should be used to identify and refer to each term without ambiguity.

Domain ontologies are used to describe data that is specific to a particular domain. For example, use ncit:sex from National Cancer Institute Thesaurus (NCIT) to describe the “sex” data element, and ncit:male to describe the “male” value of “sex” element.

The deliverable should be documented bindings of appropriate terms to metadata and data elements so that their semantics can be expressed in a machine-readable fashion.

Why is this step important 

Explain why this step is an important step in the FAIRification process.

How to

The How to section should:

  • be split into easy to follow steps;

    • Step 1 - Title of the step

    • Step 2 - Title of the step

    • etc.

  • help the reader to complete the step;

  • aspire to be readable for everyone, but, depending on the topic, may require specialised knowledge;

  • be a general, widely applicable approach;

  • if possible / applicable, add (links to) the solution necessary for onboarding in the Health-RI National Catalogue;

  • aim to be practical and simple, while keeping in mind: if I would come to this page looking for a solution to this problem, would this How-to actually help me solve this problem;

  • contain references to solutions such as those provided by FAIR Cookbook, RMDkit, Turing way and FAIR Sharing;

  • contain custom recipes/best-practices written by/together with experts from the field if necessary. 

Expertise requirements for this step 

Describes the expertise that may be necessary for this step. Should be based on the expertise described in the Metroline: Build the team step.

Practical examples from the community 

Examples of how this step is applied in a project (link to demonstrator projects).  

Training

If you have great suggestions for training material, add links to these resources here. Since the training aspect is still under development, currently many steps have “Relevant training will be added soon.”

Suggestions

This page is currently on hold. Learn more about the contributors here and explore the development process here. If you have any suggestions, visit our How to contribute page to get in touch.

Related content

Metroline Step: Create or reuse a semantic (meta)data model
Metroline Step: Create or reuse a semantic (meta)data model
More like this
Metroline Step: Apply (meta)data model
Metroline Step: Apply (meta)data model
More like this
Metroline Step: Transform and expose FAIR (meta)data
Metroline Step: Transform and expose FAIR (meta)data
More like this
Metroline Step: Analyse data semantics
Metroline Step: Analyse data semantics
More like this
Metroline Step: Define FAIRification objectives
Metroline Step: Define FAIRification objectives
More like this
Metroline Step: Assess availability of your metadata
Metroline Step: Assess availability of your metadata
Read with this