Educational simple game to train metadata mapping, in the context of Health-RI. It helps participants practice real-world metadata alignment, understand modeling challenges, and reflect on data completeness and schema design. This version of the game was used in the Health-RI FAIR Data Stewards Basics Course 2025.
Objective: Reconstruct a structured metadata model by matching example dataset information to the Health-RI metadata schema using Class, Property, Value, and Missing cards.
No help from computers or phones is allowed!
- Divide participants into groups.
- Give each group a printout of the Health-RI metadata schema and a printout of an example dataset’s metadata (included in the print version cards).
- Explain the objective clearly. For example:
“The goal is to correctly match dataset metadata to the schema using the right cards. Ambiguity may occur — that’s part of the learning!” - Distribute the decks of cards to each group (the same deck for all groups). See print version cards.
- Explain the different card types and their meanings (see Card Types).
- Optional: Keep a reference of card types visible during gameplay.
- Encourage collaboration in the final minutes if the game is not competitive.
- The game ends when all teams finish their mappings or the time runs out.
Optional: Competition element may be added. In this case, the game ends when the first group that creates a correct mapping. The mapping is checked by the game facilitator. If correct, the winner is announced and the game is finished, if not correct, the game continues until one group gets to the correct mapping.
-
Class card
This card represents an rdfs:Class resource type from the Health-RI metadata schema. See the Health-RI metadata documentation for more information about the Main and Supporting classes. -
Property card
This card represents an rdf:Property resource type from the Health-RI metadata schema. It is important to place the properties to their correct class. Participants need to find out which property belongs to which class with the help of the diagram print out. -
Value card
This card contains a metadata value from the example dataset. Each Value card should be placed under the appropriate Property card, using both the example metadata and schema as guides. -
Missing card
This card represent the missing card in the metadata schema. The participants can use this card if they cannot find the correct value for a property, to mimic missing information that would in real life situation still need to be collected, or if there is no fitting property for a certain value, to mimic missing fields in the model that would still need to be modelled.
The cards in the game represent elements of a structured metadata model. The objective is to connect them in a way that reflects the Health-RI metadata schema. Each complete mapping should form chains like this:
[Class card] → [Property card] → [Value card or Missing card]
This mimics a semantic triple in RDF, where:
- The Class card represents the entity or subject (e.g.,
Dataset
,Agent
) - The Property card represents an attribute or relation of that class (e.g.,
title
,description
) - The Value card contains an actual metadata value from the example dataset (e.g.,
"Brain MRI"
) - The Missing card is used when a value is missing in the example metadata.
If the example metadata includes:
- Title:
"MRI Scan of the head"
- Version:
"1.1"
You would form the following structure:
- [dcat:Dataset]
- → [dct:title] → "MRI Scan of the head"
- → [dcat:version] → "1.1"
Where:
[dcat:Dataset]
is a Class card[dct:title]
and[dcat:version]
are Property cards"MRI Scan of the head"
and"1.1"
are Value cards
- Analyze all cards.
- Recreate the metadata model with
Class
andProperty
cards. - Review the example metadata.
- Assign
Value
cards to the correct properties. - Use
Missing
cards where no matching value exists. - The game ends when a group finishes mapping all cards (some
Missing
cards may remain).
- Each Property card must be matched with its correct Class card using the Health-RI schema printout.
- Each Value card must be placed under the correct Property card based on the example metadata.
- Use Missing cards when a value is expected but not present in the dataset.
- If the example metadata includes a value that is not represented in the schema, use Missing cards for a property — this is an opportunity to identify potential schema extensions.
- Some Property cards may be valid for multiple Class cards. Use schema references or group discussion to determine the correct mapping.
- The process may involve ambiguity or disagreement — resolving these collaboratively is part of the learning experience.
- There are more elements in the example metadata than in the model and
- There are more elements in the model than in the example metadata
- Correct dataset, metadata schema and values matching
- Correct use of "Missing" cards
- Sometimes you don't have all the elements of the model - they become elements for you to collect,
- Sometimes not all items you have are modelled - they become model requirements,
- Some elements can be confusing and not straightforward - refer to documentation,
- Mapping can be straightforward, but can also be ambiguous regarding interpretation. Seek community/data stewards help!
Inspired by Play-a-LOD
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.