Commit 5041af4c authored by Cassandra Gould van Praag's avatar Cassandra Gould van Praag
Browse files

add contribs, zenodo and ebrains

parent 1fb1740b
......@@ -22,9 +22,17 @@ Before sharing your data on any of these platforms, we suggest you:
2. [Deidentify](../can-i#deidentification) your data
3. Curate your [metadata](../can-i#metadata)
After these stages have been considered, one or a combination of these platforms may be appropriate for sharing your data.
After these stages have been considered, one or a combination of the below [repositories](#repositories) may be appropriate for sharing your data.
## Open Science Foundation (OSF)
## Contributor attribution
Before you publish your data you should have an open and honest conversation about who has contributed to the data collection and processing, and agree how these individuals will be recognised and attributed for their work. This need not be the same list of individuals who are authors on any manuscript which references your data, indeed this can be a valuable opportunity to recognise the contributions of those who do not traditionally receive authorship on journal manuscripts (for example project managers, software engineers or data stewards).
Consider creating a [Contributor Roles Taxonomy - CRediT]( statement and sharing this with your published data. [Tenzing]( is a useful tool for collecting contributor information and generating the CRediT statement.
Aim to include the [ORCID]( of all your contributors in your published metadata, so contributions can be traced back to the individual.
## Repositories
### Open Science Foundation (OSF)
Tabular or text data (for example behavioural results or derived region of interest values) data can be shared very effectively from the [Open Science Foundation (OSF)]( OSF has built in utilities for version control, reviewer only access links, generating a digital object identifier (doi) and licence, so your data can be cited and separately from any other output. You can also grant different levels of authoring access and identify biblographic contributors which will be included in the auto-generated citation template.
**OSF is not suitable for sharing data which requires managed access on a large scale. Individuals can be granted access, but large groups (for example "anyone with an ORICD") cannot be added in bulk.**
......@@ -35,15 +43,25 @@ Take a look at this recording from the WIN Graduate program to learn more about
<div style="padding:56.25% 0 0 0;position:relative;"><iframe src="" allow="autoplay; fullscreen; picture-in-picture" allowfullscreen frameborder="0" style="position:absolute;top:0;left:0;width:100%;height:100%;"></iframe></div>
### Zenodo
[Zenodo]( is excellent for many sorts of data, although there are file size limits.
Coming soon
{: .label .label-yellow }
## NeuroVault
### NeuroVault
[NeuroVault]( is an accessible resource for collecting and distributing statistical maps of the brain (any brain data that is stored in a 3D NIFTI format). This could include group level contrasts or participant level contrasts in group (or MNI) space. It is a simple tool for adding some additional transparency to your publication.
Data shared on NeuroVault can be given a persistent url identifier, but not a digital object identifier.
You should also be satisfied with the licence conditions of adding your data to NeuroVault, particularly that it can be reused for any purpose (including commercial) and that you will not receive attribution for re-use of your data.
## OpenNeuro
Coming soon
{: .label .label-yellow }
### OpenNeuro
[OpenNeuro]( is a well known public MRI data sharing platform. It is developed and hosted in the USA, and as such it does not make provisions for data handling as required by GDPR.
**If you would like to use OpenNeuro, we suggest you only share data in group space (for example MNI space) and not participant or native space, which remains identifiable. Be sure not to share the transform files which would enable group space data to be reverted to individual participant space.**
......@@ -54,21 +72,21 @@ You should also be satisfied with the licence conditions of adding your data to
Each version of a dataset added to OpenNeuro is assigned a unique DOI
The Open Data Working Group is building a searchable, user friendly [XNAT]( database to store MRI, EEG and MEG scan data directly from the scanners. The database also has the capability to store other research data alongside the scans to create a research dataset. Image conversion tools are integrated into the database to convert raw image files to standard formats and the community standard [Brain Imaging Data Structure (BIDS)]( file structures.
The XNAT system will provide managed access at the level prescribed by the researcher (for example fully open, verified researchers only, or by email invitation). You will also be able to specify details such as required authorship, prohibition from attempts to re-identify participants, and any other terms of reuse you require.
Data shared on XNAT will be given a DOI and explicit citation text.
### How to use
#### How to use
[WIN XNAT]( (accessible from the university network or VPN) is currently under development.
While the XNAT system is in development, we suggest you use the below wording in your data availability statement in journal submissions:
> "Deidentified data will be made available on the WIN Open Data server. This is currently in development. Register here to find out when materials are available for download: []("
### For external researchers
#### For external researchers
External users will be able to search the database for resources which individual teams have chosen to make openly available. These may be deposited to support publications as supplementary methods material, or they may form the main body of research in data papers.
[Sign up to the win-open-data mailing list]( to receive updates on new data shared to the WIN XNAT server or new features. This mailing list will be "broadcast only" with messages sent from WIN XNAT administrators. You can unsubscribe at any point. Enquiries about external access to WIN XNAT should be directed to
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment