Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

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.  

Existing identifiers can be reused, or new identifiers can be created (minted) if necessary. Often locally unique identifiers are used, which can be transformed into globally unique identifiers using namespaces [FCB016].  

Equivalence between identifiers are presented in mappings. Such a mapping can, for example, be a tsv file with two columns, one per dataset, with each row representing two equivalent concepts, or can adhere to the Simple Standard for Sharing Ontology Mapping standard [SSSOM]. 

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. 

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.  

How to 

FAIRPlus: Select the identifier scheme 

  • Identifier Minting: How to create unique, persistent and resolvable identifiers  

    • FCB006: Unique, persistent identifiers 

    • FCB007: InChI and SMILES identifiers for chemical structures 

    • FCB008: Minting identifiers with Minid 

    • FCB077: Creating resolvable identifiers 

  • Reusing community identifiers: How to reuse existing identifiers in a dataset 

    • FCB016: Interlinking data from different sources 

    • FCB017: Identifier mapping with BridgeDb 

 

BridgeDB (API, Tutorials and Workflows, Documentation): https://www.bridgedb.org/  

 

[GOFAIR_F1] Example services that supply globally unique and persistent identifiers: 

Practical Examples from the Community 

This section should show the step applied in a real project. Links to demonstrator projects. 

Further reading & References 

[FAIRopoly] FAIRopoly https://www.ejprarediseases.org/fairopoly/ 

[Generic] A Generic Workflow for the Data FAIRification Process: https://direct.mit.edu/dint/article/2/1-2/56/9988/A-Generic-Workflow-for-the-Data-FAIRification  

[Elixir] https://faircookbook.elixir-europe.org/content/recipes/introduction/fairification-process.html  

[Elixir2] A framework for FAIRification processes: https://faircookbook.elixir-europe.org/content/recipes/introduction/metadata-fair.html  

[GOFAIR] https://www.go-fair.org/fair-principles/f2-data-described-rich-metadata/ 

[RDMkit] https://rdmkit.elixir-europe.org/machine_actionability.html 

 

[GOFAIR_F1] https://www.go-fair.org/fair-principles/f1-meta-data-assigned-globally-unique-persistent-identifiers/  

[SSSOM] https://github.com/mapping-commons/sssom 

[BRIDGEDB] https://www.bridgedb.org/  

Authors / Contributors 

Experts whom you can contact for further information 

 

  • No labels