search

FAIR-Data-EG / consultation

A call for contributions to the report of the FAIR Data Expert Group
Other
16 stars 3 forks source link

FAIR Data needs FAIR tooling that is lightweight and ubiquitous #30

Open CaroleGoble opened 6 years ago

CaroleGoble commented 6 years ago

[//]: # "==Do not write above this line== Instructions for posting issues: (1) Review what is already there. Perhaps a comment to an existing issue would be more appropriate than opening a new one? (2) Write your post below using Markdown (as per https://guides.github.com/features/mastering-markdown/ ) or just plain text. (3) Don't worry about these introductory lines - you can leave or delete them, as they won't display anyway (you can check this via Preview). (4) Hit the 'Submit new issue' button. ==Write below this line==" FAIR principles are all very well, but without the TOOLS for FAIR then its not possible to adopt. To make a "app eco system" of FAIR tools we need very small number of lightweight protocols and conventions, with real and adoptable, sustainable tooling. This is not the time for monolithic systems. Scruffy, lightweight, easy and ubiquitous ALWAYS beats out fancy, heavyweight, tricky and limited in my experience.

CaroleGoble commented 6 years ago

We need FAIR on-Ramps to lift the burden on all data providers, including long tail – Tools, governance, methods of working, costs – Leveraging reality of practice (spreadsheets are ubiquitous and a great ramp) – Leverage commercial and commodity Off the Shelf infrastructures (Bioschemas, Docker...) – FAIR as a side-effect, removing friction

We should NOT build specialist bespoke infrastructures that are impossible to sustain. And we should not waste public money on such where few researchers or data providers really use it.

People are RAMPS too – FAIR curators. We had to do a great deal of curating to make data FAIR for the FAIRDOMHub.org.

LeifLaaksonen commented 6 years ago

How do you define now the difference between a tool and the (e-)infrastructure? I would have defined it rather from the (e-)infrastructure that includes a set of tools. However, there are still open questions as do we talk about a subset of an infrastructure or are we talking about (future) potential aggregations of infrastructures we currently are not even aware of?