Open WIN Community issueshttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues2024-02-18T13:45:55+00:00https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/1Add documentation on open access publishing2024-02-18T13:45:55+00:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukAdd documentation on open access publishingYing-Qiu ZhengYing-Qiu Zhenghttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/48[documentation] guide on CRediT2023-02-23T14:14:01+00:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.uk[documentation] guide on CRediT## I'm submitting a ...
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
Here some draft notes on using CRediT for acknowledging author contributions.
The below needs to be re-written for a general audi...## I'm submitting a ...
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
Here some draft notes on using CRediT for acknowledging author contributions.
The below needs to be re-written for a general audience and published somewhere.
## Draft CRediT guide
The [CRediT framework](https://casrai.org/credit/) is a useful tool for acknowledging different types of author contributions. This may be particularly relevant if you are publishing non-traditional research outputs, such as data and code.
Using CRediT, you can identify *anyone* who has contributed to the work which went into the object you are publishing, and assign them to any of the roles listed (people can have multiple roles). You can then use [tenzing](https://martonbalazskovacs.shinyapps.io/tenzing/) to create an authorship statement which you add to zenodo. Example of a CRediT statement on [this zenodo entry](https://zenodo.org/record/5826183#.Yo5THC2ZPs0).
As a general rule I’m always super-inclusive on authorship. I don’t think it harms the output to show that the work/efforts of many people made it possible.https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/6Readability - action findings of accessibility report2023-02-27T10:15:43+00:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukReadability - action findings of accessibility reportJuju FarsJuju Farshttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/44[website] import h2mri2023-04-27T23:05:17+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.uk[website] import h2mri## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
In 2018-2020, Cass wrote a guide on open science MRI data collection and analysis bes...## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
In 2018-2020, Cass wrote a guide on open science MRI data collection and analysis best practices for [PERL](https://www.google.com/search?client=safari&rls=en&q=oxford+perl&ie=UTF-8&oe=UTF-8). There is some content which could be usefully incorporated into the Community Pages.
## Action to take
Import relevant sections of [https://git.fmrib.ox.ac.uk/cassag/h2mri](https://git.fmrib.ox.ac.uk/cassag/h2mri).
To be considered:
- [x] What "chapters" to include?
- [ ] Where should they go? Analysis? Separate pages on RDM?
- [ ] move the code from git.fmrib...cassag/h2mri to a community repository (perhaps open-science/analysis?
- [ ] flag the known issues with the code! 1) singularity container should not be in there repo (people should pull it using a stated path to the container repo); 2) conda packages should not be in the repo, people should pull them!