-
code state: 390fb39dd3ac909ed699a12ef9d01b2d5a75a65a
Q 9. "What approach does the software take to versioning?" probably best relates to "R3. Software meets domain-relevant community standards." …
tom-h updated
11 months ago
-
Hopefully useful capture of some of the points raised.
## Introduction to Profiling
- [ ] Disseminate setup instructions before course, perhaps bundle up the various files that users will downlo…
-
1. Documenting Packages
- Why document? (tie it in with FAIR4RS principles; findability, etc)
- Documenting functions with `roxygen2`
- Using vignettes for, e.g., tutorials
- [Di…
-
[New guidelines](https://doi.org/10.1038/s41597-022-01710-x) for how FAIR (Findable, Accessible, Interoperable, Reproducible) applies to research software should be incorporated into the toolbox.
-
### New Resource Request
FAIR Principles for Research Software (FAIR4RS Principles)
### Resource Title
FAIR Principles for Research Software (FAIR4RS Principles)
### Resource URL
https:…
-
### New Resource Request
FAIR Principles for research software
### Resource Title
Introducing the FAIR Principles for research software
### Resource URL
https://doi.org/10.1038/s41597-…
-
### New Resource Request
Resources on FAIR software
### Resource Title
Ten quick tips for building FAIR workflows
### Resource URL
https://doi.org/10.1371/journal.pcbi.1011369
### Resource Descr…
-
### New Resource Request
Practical example showing practices that implement FAIR Principles for Research Software (FAIR4RS).
### Resource Title
FAIR multi-omics analysis workflow
### Resource UR…
-
I would like to share some more thoughts and observations from a complete read of the competencies paper:
- [x] 1.) Software Re-Use (SRU) is listed as a research skill, but it is actually one of t…
-
From GoogleDoc by Andreas Wagner:
I tried to find it in this paper and in the mentioned "Defining Research Software", but it seems to be only mentioned in passing or implicitly, maybe it's worth a fo…