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

« Previous Version 3 Next »

Short Description 

To be able to reach your FAIRification goals, having a team with the right skillset is important [FAIRopoly]. The composition of the team depends on the exact goals and different skills may be necessary in different phases of the of the process [Elixir]. The core of the team may be formed by one or more data stewards with expertise of the FAIRification process in general and knowledge of the local environment [Generic]. The team may, furthermore, contain (part-time) advisors with, for example domain expertise [FAIRopoly], as well as data managers, software developers, research scientists, project managers and legal support [Elixir]. 

Working Group

Why is this step important 

FAIRification is a complicated process and requires expertise from a variety of fields. Hence, assembling the right team is essential to meet your goals.  

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 

This section should help complete the step. It’s crucial that this is practical, doable and scalable. 

Depending on the type of step, this can, for example, be a reference to one or more (doable) recipes, or perhaps some form of checklist? The recipes/best-practices presented should be based on experts from the field. 

This should probably be a subpage so as not to have too much text on this page.  

References, if relevant, to FAIRCookbook, RDMKit, GOFAIR?  

Sub headers if relevant for specific domains? 

 

Generic Workflow[2]: 

Data FAIRification requires different types of expertise and should therefore be carried out in a multidisciplinary team guided by FAIR data steward(s). The different sets of expertise are on i) the data to be FAIRified and how they are managed, ii) the domain and the aims of the data resource within it, iii) architectural features of the software that is (or will be) used for managing the data, iv) access policies applicable to the resource, v) the FAIRification process (guiding and monitoring it), vi) FAIR software services and their deployment, vii) data modelling, viii) global standards applicable to the data resource, and ix) global standards for data access. A good working approach is to organize a team that contains or has access to the required expertise. The core of such a team may be formed by data stewards, with at least expertise of the local environment and of the FAIRification process in general. 

Practical Examples from the Community 

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

References & Further reading

[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] A framework for FAIRification processes: https://faircookbook.elixir-europe.org/content/recipes/introduction/metadata-fair.html  

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

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

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

Authors / Contributors 

Experts whom you can contact for further information 

  • No labels