BONSAMURAIS / BONSAMURAIS/reproducibility

Monitor other working groups for FAIR principles

Open
#8 2 comments 0 reactions 0 assignees View on GitHub
During Hackathon
Dominant language
No language data
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

The FAIR principles for "Findable, Accessible, Interoperable, Reusable" data products are as follows:

**To be Findable:**
- [ ] F1. (meta)data are assigned a globally unique and persistent identifier
- [ ] F2. data are described with rich metadata (defined by R1 below)
- [ ] F3. metadata clearly and explicitly include the identifier of the data it describes
- [ ] F4. (meta)data are registered or indexed in a searchable resource
**To be Accessible:**
- [ ] A1. (meta)data are retrievable by their identifier using a standardized communications protocol
- [ ] A1.1 the protocol is open, free, and universally implementable
- [ ] A1.2 the protocol allows for an authentication and authorization procedure, where necessary
- [ ] A2. metadata are accessible, even when the data are no longer available
**To be Interoperable:**
- [ ] I1. (meta)data use a formal, accessible, shared, and broadly applicable language for knowledge representation.
- [ ] I2. (meta)data use vocabularies that follow FAIR principles
- [ ] I3. (meta)data include qualified references to other (meta)data
**To be Reusable:**
- [ ] R1. meta(data) are richly described with a plurality of accurate and relevant attributes
- [ ] R1.1. (meta)data are released with a clear and accessible data usage license
- [ ] R1.2. (meta)data are associated with detailed provenance
- [ ] R1.3. (meta)data meet domain-relevant community standards

We need to select a subset of these objectives to (a) define in the context of the hackathon and (b) ensure the other groups are attaining them.

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or entry points are mentioned. Start with the FAIR checklist in this issue and the hackathon context; define the subset of objectives and a way to verify that other working groups meet them.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.