Short Description
FAIR (meta)data requires globally unique and persistent identifiers (principle F1). Such identifiers remove ambiguity in the meaning of your data by assigning a unique identifier to every element of metadata and every concept/measurement in your dataset [GOFAIR_F1]. In this context, an identifier consists of an internet link, such as a URL, which can be resolved. Identifiers can help both humans and computers interpreting your data.
...
Furthermore, many specialised identifier services exist, which can help map from one identifier to another. BridgeDB, for example, is a framework to map identifiers between various biological databases and related resources [BRIDGEDB]. It provides mappings for genes, proteins, metabolites, metabolic reactions, diseases, complexes and publications.
How to
[FAIRInAction]: Select the identifier scheme
...
Persistent URLs: http://www.purlz.org
Digital Object Identifier: http://www.doi.org
Archival Resource Key: https://escholarship.org/uc/item/9p9863nc
Research Resource Identifiers: https://scicrunch.org/resources
Identifiers for funding organisations (see F3 & R1): https://www.crossref.org/services/funder-registry/
Identifiers for the world’s research organisations (see F3 & R1): https://www.grid.ac
Expertise requirements for this step
This section could describe the expertise required. Perhaps the Build Your Team step could then be an aggregation of all the “Expertise requirements for this step” steps that someone needs to fulfil his/her FAIRification goals.
Practical Examples from the Community
This section should show the step applied in a real project. Links to demonstrator projects.
Training
Add links to training resources relevant for this step. Since the training aspect is still under development, currently many steps have “Relevant training will be added in the future if available.”