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

add data sharing questions

parent eca46ee4
Pipeline #13458 passed with stages
in 2 minutes and 13 seconds
......@@ -8,20 +8,27 @@ nav_order: 4
# Open Data
{: .fs-9 }
How to share your data responsibly
Questions to help you plan and prepare for data sharing
{: .fs-6 .fw-300 }
---
![open-data](../../img/img-open-data-flow.png)
<!-- ![open-data](../../img/img-open-data-flow.png)
## Purpose
## Data sharing FAQ -->
The Open Data Working Group has built a searchable, user friendly [XNAT](https://www.xnat.org) 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 be integrated into the database to convert raw image files to standard formats and the community standard [Brain Imaging Data Structure (BIDS)](https://bids.neuroimaging.io) file structures.
![data sharing questions](../../img/img-sharing-questions_w800px.png)
Data will only ever be shared when the participant has given explicit consent to open sharing. All access protocols have been developed to ensure the highest levels of security to protect against accidental or malicious data breaches.
These pages have the answers to frequently asked questions on data sharing.
### General Data Protection Regulation (GDPR) compliant data sharing policy
<!-- [1. Why should I share my data?](../why)
[2. Can I share my data?]
3. How do I share my data?
4. When should I think about sharing my data? -->
<!-- ### General Data Protection Regulation (GDPR) compliant data sharing policy
The database has the capability to share data at between specified individuals, openly to all WIN members, or externally based on the requirements of the research lead.
#### De-identification
......@@ -35,22 +42,18 @@ The Data Usage Agreement and de-identification process is being developed with t
#### Quality control
WIN members will also be encouraged to run and share the results of predefined quality control algorithms, so anyone accessing the data can have a ready measure of image quality.
[![For WIN members](../../img/btn-win.png)](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/tools/data/#for-win-members) [![For external researchers](../../img/btn-external.png)](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/tools/data/#for-external-researchers)
[![For WIN members](../../img/btn-win.png)](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/tools/data/#for-win-members) [![For external researchers](../../img/btn-external.png)](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/tools/data/#for-external-researchers) -->
Coming soon
<!-- Coming soon
{: .label .label-yellow }
**THIS TOOL IS CURRENTLY IN DEVELOPMENT. PLEASE REFER TO THE INFORMATION BELOW TO UNDERSTAND THE AIM AND AMBITION OF THIS PROJECT. THE "HOW TO" GUIDE WILL BE BUILT BY THE COMMUNITY AND TOOL DEVELOPERS IN THE COMING MONTHS.**
<br>
<br> -->
## For WIN members
Note 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: [https://web.maillist.ox.ac.uk/ox/subscribe/win-open-data](https://web.maillist.ox.ac.uk/ox/subscribe/win-open-data)"
### Benefits
<!-- ### Benefits
#### Version control ![version-control](../../img/icon-version-control.png)
Coming soon
{: .label .label-yellow }
......@@ -62,45 +65,19 @@ Coming soon
#### Reproducible methods detail ![reproduce](../../img/icon-reproduce.png)
Coming soon
{: .label .label-yellow }
-->
### How to use
[WIN XNAT](https://xnat.win.ox.ac.uk) (accessible from the university network or VPN) is currently being built and will be used to share imaging data internally within WIN.
#### Access
You can log into [WIN XNAT](https://xnat.win.ox.ac.uk) using your WIN IT account (currently requires a connection to the university network or VPN).
#### Useful background
The [XNAT](https://xnat.org) website has useful background information about the XNAT platform.
#### BIDS in XNAT
For the current overview of how BIDS works in XNAT, see the [BIDS](./data/bids.md) page.
#### Python libraries
There are several python libraries](data/python.md) that can be used to write scripts against the XNAT API. See [python libraries](data/python.md) for more info on pyxnat, xnatpy and dax.
#### Docker in XNAT
To see how Docker works in XNAT, see the [Docker](data/docker.md) page.
#### Case Studies
The [OPDC project](data/opdc.md) uploaded DICOM data from jalapeno using python and dcmtk.
TODO: More case studies!
## 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](https://web.maillist.ox.ac.uk/ox/subscribe/win-open-data) 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 cassandra.gouldvanpraag@psych.ox.ac.uk.
## Working group members (alphabetically)
<!-- ## Working group members (alphabetically)
We are grateful to the following WIN members for their contributions to developing the Open Data server.
- [Stuart Clare](https://www.win.ox.ac.uk/people/stuart-clare)
- [Cassandra Gould van Praag]
- [Dave Flitney](https://www.win.ox.ac.uk/people/david-flitney)
- [Clare Mackay](https://www.win.ox.ac.uk/people/clare-mackay)
- [Duncan Mortimer](https://www.win.ox.ac.uk/people/duncan-mortimer)
- Paul Semple
- Duncan Smith
- [Matt South](https://www.win.ox.ac.uk/people/matthew-south)
- [Matt South](https://www.win.ox.ac.uk/people/matthew-south) -->
---
layout: default
title: BIDS in XNAT
parent: Open Data
grand_parent: Open WIN Tools
parent: Tools for XNAT
grand_parent: Open Data
has_children: false
nav_order: 1
---
......
---
layout: default
title: Deidentification
parent: Can I share my data?
grand_parent: Open Data
has_children: false
nav_order: 3
---
# Deidentification
{: .fs-9 }
Steps to protect the identity of your participants
{: .fs-6 .fw-300 }
---
![cani-deident](../../../img/img-cani-deident.png)
<!-- <html><body><i class="fas fa-exclamation-triangle"></i></body></html> -->
<!-- <html><body><i class="fas fa-check-circle"></i></body></html> -->
<details>
<summary><html><body><i class="fas fa-exclamation-triangle"></i></body></html> <b>Have you removed any "direct identifiers" in your data?</b></summary><br>
Direct identifiers are things which identify an individual without any additional information. For example their name, address or telephone number. <i>This information should never be shared with the data</i>.
<br><br>
</details>
<details>
<summary><html><body><i class="fas fa-exclamation-triangle"></i></body></html> <b>Are your imaging data in participant space?</b></summary><br>
Participant space (cortical structure) is unique to an individual and as such is an identifiable feature under GDPR. Avoid sharing data which is in participant space where possible. If it is preferable to share data in participant space, ensure other features described below are redacted as appropriate for your analysis.
<br><br>
</details>
<details>
<summary><html><body><i class="fas fa-exclamation-triangle"></i></body></html> <b>Have your Participant IDs been protected?</b></summary><br>
Are any keys which link researcher generated Participant IDs and WIN generated Scan IDs to GDPR "special category" data (names, contact information, consent documentation etc.) held in a facility which is surrounded by a suitable regime of controls and safeguards to prevent data breaches and misuse (<a href="https://cronfa.swan.ac.uk/Record/cronfa53688">Jones and Ford, 2018</a>)? In practice, this is achieved by following <a href="https://researchsupport.admin.ox.ac.uk/files/bpg09datacollectionandmanagementpdf">CUREC BPG 09</a>, with data only held on a approved shared drive (Departmental or One Drive), or a device with whole disk encryption.
The linkage key must be "stored separately from" (<a href="https://researchsupport.admin.ox.ac.uk/files/bpg09datacollectionandmanagementpdf">CUREC BPG 09</a>) special category and research data, It must not be shared with research data except in critical circumstances. The validity of requests for access to the linkage key should be assessed on an individual basis by the responsible data controller (usually the Principle Investigator).
<br><br>
</details>
<details>
<summary><html><body><i class="fas fa-exclamation-triangle"></i></body></html> <b>Have "indirect identifiers" such as age, gender, handedness or disease status been protected?</b></summary><br>
Consider combining "indirect identifiers" (<a href="https://researchsupport.admin.ox.ac.uk/files/bpg09datacollectionandmanagementpdf">CUREC BPG 09</a>) into bins such that no participant can be uniquely identified. Ideally bins should contain >= 5 participants.
<br><br>
</details>
<details>
<summary><html><body><i class="fas fa-exclamation-triangle"></i></body></html> <b>Have unique dicom fields been scrubbed?</b></summary><br>
If you are sharing dicom data, you should aim to scrub the dicom headers of identifiable and unique fields. Consider the relative risk of retaining some fields if they are important to your analysis.
<br><br>
</details>
<details>
<summary><html><body><i class="fas fa-exclamation-triangle"></i></body></html> <b>Have unique fields in .json sidecar files been scrubbed?</b></summary><br>
If you are sharing nifti data with json sidecar files, you should scrub the .json files of all identifiable and unique fields. Consider the relative risk of retaining some fields if they are important to your analysis.
<br><br>
</details>
<details>
<summary><html><body><i class="fas fa-exclamation-triangle"></i></body></html> <b>Have images been defaced?</b></summary><br>
If you are sharing data with facial features, have these images been defaced and assessed for the quality of the defacing? Consider using fsl-deface. Consider using <a href="https://raamana.github.io/visualqc/gallery_defacing.html">VisualQC</a> to inspect and document the success of your defacing.
<br><br>
</details>
---
<!-- Key -->
<html>
<body><small>
<p><i class="fas fa-exclamation-triangle"></i> = essential to address before sharing your data.<br>
<i class="fas fa-check-circle"></i> = desirable best practice.</p>
</small></body>
</html>
---
layout: default
title: Ethics
parent: Can I share my data?
grand_parent: Open Data
has_children: false
nav_order: 2
---
# Ethics
{: .fs-9 }
What have your ethical review committee and participants agreed to?
{: .fs-6 .fw-300 }
---
![cani-ethics](../../../img/img-cani-ethics.png)
<!-- <html><body><i class="fas fa-exclamation-triangle"></i></body></html> -->
<!-- <html><body><i class="fas fa-check-circle"></i></body></html> -->
<details>
<summary><html><body><i class="fas fa-exclamation-triangle"></i></body></html> <b>Have you described data sharing in your ethics application?</b></summary><br>
Your ethics application and participant information sheet should minimally refer to the sharing of data with colleagues outside of the University. Ideally, you should include the possibility of sharing "deidentified data in online databases". If you have collected MRI data under <a href="https://researchsupport.admin.ox.ac.uk/governance/ethics/resources/ap#collapse397171">CUREC Approved Procedure 17 (version 6.0+)</a> a statement fulfilling this requirement will be included already.
<br><br>
</details>
<details>
<summary><html><body><i class="fas fa-exclamation-triangle"></i></body></html> <b>Has your participant consented to data sharing?</b></summary><br>
Many consent forms have a separate section or box to indicate the participant is aware of your data sharing plans (box 4 on the <a href="https://researchsupport.admin.ox.ac.uk/governance/ethics/resources/ap#collapse397171">Approved Procedure 17 consent form</a>). Has your participant indicated they have agreed to data sharing as you have described?
<br><br>
</details>
---
<!-- Key -->
<html>
<body><small>
<p><i class="fas fa-exclamation-triangle"></i> = essential to address before sharing your data.<br>
<i class="fas fa-check-circle"></i> = desirable best practice.</p>
</small></body>
</html>
---
layout: default
title: Governance
parent: Can I share my data?
grand_parent: Open Data
has_children: false
nav_order: 1
---
# Data governance?
{: .fs-9 }
Internal and external policies which relate to the access of your data.
{: .fs-6 .fw-300 }
---
![cani-gov](../../../img/img-cani-gov.png)
<!-- <html><body><i class="fas fa-exclamation-triangle"></i></body></html> -->
<!-- <html><body><i class="fas fa-check-circle"></i></body></html> -->
<details>
<summary><html><body><i class="fas fa-exclamation-triangle"></i></body></html> <b>Is sharing restricted under Intellectual Properties rights?</b></summary><br>
Intellectual property rights are rights granted to creators and owners of works that are the result of human intellectual creativity (<a href="https://www.jisc.ac.uk/guides/intellectual-property-rights-in-a-digital-world">JISC Guides</a>). Put simply, you first need to establish whether the data is yours to share. If you have acquired new data for this project, you are in control of how it is shared. If, however, you are conducting secondary analysis on data acquired from elsewhere, please check what limits the owners have imposed on re-sharing. This information may be available from their license or a data usage agreement which you confirmed when accessing the data.
<br><br>
</details>
<details>
<summary><html><body><i class="fas fa-exclamation-triangle"></i></body></html> <b>Has your funder or industry partner approved data sharing?</b></summary><br>
If your research was partly or whole funded by an industry partner, they may have imposed conditions to restrict sharing to protect they commercial interests. Review any contracts to insure that funders or industry partners allow you to share the data.
<br><br>
</details>
<details>
<summary><html><body><i class="fas fa-exclamation-triangle"></i></body></html> <b>Have you investigated commercial potential of your data?</b></summary><br>
As a University employee you are obliged to consider the commercial potential of your outputs. If you think there may be commercial value in your data, please speak to <a href="https://innovation.ox.ac.uk/university-members/commercialising-technology/ip-patents-licenses/oui-fit/">Oxford University Innovation (OUI)</a> for support.
<br><br>
</details>
<details>
<summary><html><body><i class="fas fa-check-circle"></i></body></html> <b>Have you discussed open data sharing in your data management plan?</b></summary><br>
<p>Creating a data management plans helps you plan how you will manage the data acquired during your project by considering the type of data you are producing, who needs to access it and accordingly how it is stored. They are a mandatory part of some grant applications, but they are also a useful exercise for smaller projects which don't require separate funding.</p>
<p>Find out more about how the University can <a href="https://researchdata.ox.ac.uk/home/managing-your-data-at-oxford/data-management-planning/">support you in creating a data management plan</a>.</p>
<p>Review the <a href="https://wellcome.org/grant-funding/guidance/how-complete-outputs-management-plan">Wellcome Trust requirements for data management plans in relation to data sharing</a>.</p>
<p> Review a <a href="https://sharepoint.nexus.ox.ac.uk/sites/NDCN/FMRIB/IT/_layouts/15/WopiFrame.aspx?sourcedoc=/sites/NDCN/FMRIB/IT/Documents/WIN%20Centre%20-%20Data%20Management%20Plan%20MRC%20Template.docx&action=default&DefaultItemOpen=1">MRC format WIN specific example data management plan (pre data sharing infrastructure)</a>.</p>
<p> Review the <a href="https://www.ukri.org/publications/bbsrc-data-sharing-policy/">BBSRC requirements for data management plans in relation to data sharing</a></p>
<br><br>
</details>
<details>
<summary><html><body><i class="fas fa-check-circle"></i></body></html> <b>Does your Data Protection Impact Assessment (DPIA) reference data sharing?</b></summary><br>
All studies which collect new or re-use existing data must be assessed for risks of a data breach. This risk is assessed using a <a href="https://compliance.admin.ox.ac.uk/data-protection-forms#collapse1091641">Data Protection Impact Assessment (DPIA) Screening form</a>. Note for the purposes of the DPIA Screening, human imaging data may be considered "biometric data": "personal data resulting from specific technical processing relating to the physical, physiological, or behavioural characteristics of a natural person, which allows or confirms the unique identification of that natural person, such as facial images or fingerprint data."<br><br>
</details>
<details>
<summary><html><body><i class="fas fa-exclamation-triangle"></i></body></html> <b>Are you sharing data acquired from living humans?</b></summary><br>
GDPR restrictions relate only to data acquired from living humans.
<p><b>Non-human</b> data are not required to be de-identified. Consider sharing your data on the <a href="https://open.win.ox.ac.uk/DigitalBrainBank/#/">Digital Brain Bank</a>.</p>
<p><b>Ex vivo human data</b> should be treated in accordance with the requirements of the Common Law Duty of Confidentiality. You should also be aware of the possibility of living individuals (for example relatives of the deceased) being identified in this information, which would then need to be treated in line with GDPR personal information. Please review the <a href="http://www.hra-decisiontools.org.uk/consent/principles-deceased.html">HRA Decision Tool for principles for handling data from deceased human participants</a>. Consider sharing your data on the <a href="https://open.win.ox.ac.uk/DigitalBrainBank/#/">Digital Brain Bank</a>.</p><br><br>
</details>
---
<!-- Key -->
<html>
<body><small>
<p><i class="fas fa-exclamation-triangle"></i> = essential to address before sharing your data.<br>
<i class="fas fa-check-circle"></i> = desirable best practice.</p>
</small></body>
</html>
---
layout: default
title: Metadata
parent: Can I share my data?
grand_parent: Open Data
has_children: false
nav_order: 4
---
# Making your data more useful to others
{: .fs-9 }
Additional information could you share to make your data more useful?
{: .fs-6 .fw-300 }
---
![cani-meta](../../../img/img-cani-meta.png)
<!-- <html><body><i class="fas fa-exclamation-triangle"></i></body></html> -->
<!-- <html><body><i class="fas fa-check-circle"></i></body></html> -->
#### Metadata
<details>
<summary><html><body><i class="fas fa-check-circle"></i></body></html> <b>Is your data FAIR?</b></summary><br>
FAIR data is findable, accessible, interoperable and reusable. Take a look at the <a href="https://faircookbook.elixir-europe.org/content/home.html">FAIR Cook Book</a> alongside these questions to make sure the data the you publish has the most value to our community.
<br><br>
</details>
<details>
<summary><html><body><i class="fas fa-check-circle"></i></body></html> <b>Have you conducted and prepared to share a quality control analysis?</b></summary><br>
It is good practice to share a quality control (QC) analysis. Consider running <a href="https://mriqc.readthedocs.io/en/latest/">mriqc</a> and sharing the results with your data.
<br><br>
</details>
<details>
<summary><html><body><i class="fas fa-check-circle"></i></body></html> <b>Are you able to share the image acquisition protocol?</b></summary><br>
Consider adding the MR protocol and scanning procedure documents to the <a href="https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/protocols/">MR Protocols database</a>. Add a link to your database entry digital object identifier (doi) in your shared data.
<br><br>
</details>
<details>
<summary><html><body><i class="fas fa-check-circle"></i></body></html> <b>Are behavioural and clinical covariates appropriately described?</b></summary><br>
<p>Measured results for each participant should be provided in a single file containing all covariates, in appropriately <a href="https://en.wikipedia.org/wiki/Machine-readable_data">machine readable structure</a>.</p>
<p>Covariates should be accompanied by a data dictionary which describes each of the variables included, how they were derived and the source data where possible.</p>
</details>
#### Community standards
<details>
<summary><html><body><i class="fas fa-check-circle"></i></body></html> <b>Have you prepared the data according to community standards?</b></summary><br>
<p>Sharing your data in accordance with community standards makes it easier for others to understand and work with your data. It also means that code developed to work on data structured to this standard will be easier to apply. </p>
<p>The community standard for MRI data is the <a href="https://bids.neuroimaging.io">Brain Imaging Data Structure (BIDS)</a></p>
<p>Community standards for other imaging data are evolving as <a href="https://bids.neuroimaging.io/get_involved.html#extending-the-bids-specification">BIDS extension proposals (BEPS)</a>. Take a look at the current BEPS and consider contributing to the development of a standard for your data type.</p>
<p>A community standard for electrophysiology data is <a href="https://www.nwb.org">Neurodata Without Borders (NWB)</a>.</p>
</details>
<details>
<summary><html><body><i class="fas fa-check-circle"></i></body></html> <b>Has the experimental protocol been described and made ready to share with the data?</b></summary><br>
If you are following the BIDS standard, minimal experimental detail should be described in the dataset_descriptor.json file which is generated during BIDS conversion. If you are not following the BIDS standard, you should describe your experimental protocol to a sufficient level of detail and attach that information to your data.
<br><br>
</details>
---
<!-- Key -->
<html>
<body><small>
<p><i class="fas fa-exclamation-triangle"></i> = essential to address before sharing your data.<br>
<i class="fas fa-check-circle"></i> = desirable best practice.</p>
</small></body>
</html>
---
layout: default
title: Approriate reuse
parent: Can I share my data?
grand_parent: Open Data
has_children: false
nav_order: 5
---
# Appropriate reuse
{: .fs-9 }
What steps can you take to ensure your data is reused appropriately?
{: .fs-6 .fw-300 }
---
![cani-reuse](../../../img/img-cani-reuse.png)
<!-- <html><body><i class="fas fa-exclamation-triangle"></i></body></html> -->
<!-- <html><body><i class="fas fa-check-circle"></i></body></html> -->
#### Access restrictions
<!-- Can access to your data be restricted in a way which protects the privacy of your participants and you intellectual work? -->
<details>
<summary><html><body><i class="fas fa-check-circle"></i></body></html> <b>Can you create a "reviewer only" link to shared material?</b></summary><br>
In some cases you may wish to make your data available only to a reviewer before making it available for wider release. Is this possible with your intended repository?
<br><br>
</details>
<details>
<summary><html><body><i class="fas fa-check-circle"></i></body></html> <b>Can you restrict access to bonafide researchers only?</b></summary><br>
Given a the need for responsible reuse of your data, it may be wise to restrict re-use to those individuals who are likely to have a genuine research interest. Can your intended repository restrict access to allow only bonafide researchers, for example by institutional email verification, or an <a href="https://orcid.org">ORCID ID</a>?
<br><br>
</details>
#### Your acknowledgement
<details>
<summary><html><body><i class="fas fa-check-circle"></i></body></html> <b>Can you create a doi for your data?</b></summary><br>
Does the tool you are using to share your data allow you to create a citable digital object identifier (doi) for the exact version of your data you are sharing? This doi can be used by others to reference your data.
<br><br>
</details>
<details>
<summary><html><body><i class="fas fa-check-circle"></i></body></html> <b>Can you select a license which requires attribution?</b></summary><br>
Your data is a significant intellectual output, and you deserve to be recognised for it if your output is reused. We recommend using a repository where you can apply a license for reuse which necessitates attribution, for example <a href="https://creativecommons.org/licenses/by/4.0/">CC-BY-4.0</a>. You may additionally like to apply a license which restricts commercial use (for example <a href="https://creativecommons.org/licenses/by-nc/4.0/legalcode">CC-BY-NC-4.0</a>), allowing commercial use to be negotiated by the University.
<br><br>
</details>
#### Customising your Data Usage Agreement (DUA)
<details>
<summary><html><body><i class="fas fa-check-circle"></i></body></html> <b>Would you like to impose requirements for authorship?</b></summary><br>
You may wish to stipulate that you are contacted to discuss authorship and further contributions if your data are reused. Alternatively you may wish to stipulate that you are not included as an author on any reuse of the data. Is it possible to impose such requirements with your intended repository?
<br><br>
</details>
<details>
<summary><html><body><i class="fas fa-check-circle"></i></body></html> <b>Would you like to impose restrictions on resharing?</b></summary><br>
You may wish to stipulate that users of your data do not share it any further once they have acquired a copy. Is it possible to impose this requirement with your intended repository?
<br><br>
</details>
<details>
<summary><html><body><i class="fas fa-check-circle"></i></body></html> <b>Would you like to explicitly prohibit attempts to reidentify participants in your data?</b></summary><br>
Given that many types of imaging can not be made fully anonymous, it may be wise to include an additional legal restriction which explicitly prohibits attempts to re-identify your participants, for example via linkage to other public sphere or experimental data. Is it possible to impose such requirements with your intended repository?
<br><br>
</details>
<details>
<summary><html><body><i class="fas fa-exclamation-triangle"></i></body></html> <b>Do you need to add any funder requirements in the reuse of your data?</b></summary><br>
Some funders may require acknowledgement in perpetuity for data generated with their funds. Is it possible to impose such requirements with your intended repository?
<br><br>
</details>
---
<!-- Key -->
<html>
<body><small>
<p><i class="fas fa-exclamation-triangle"></i> = essential to address before sharing your data.<br>
<i class="fas fa-check-circle"></i> = desirable best practice.</p>
</small></body>
</html>
---
layout: default
title: Can I share my data?
parent: Open Data
has_children: true
nav_order: 2
has_toc: false
---
# Can I share my data?
{: .fs-9 }
Things to consider when planning to share your data
{: .fs-6 .fw-300 }
---
![cani-all](../../../img/img-cani-all.png)
Use the pages linked on the left to understand more about the required policy and best practice in preparing your data for sharing.
---
layout: default
title: Docker
parent: Open Data
grand_parent: Open WIN Tools
parent: Tools for XNAT
grand_parent: Open Data
has_children: false
nav_order: 2
---
......
---
layout: default
title: How do I share my data?
parent: Open Data
has_children: false
nav_order: 3
---
# How do I share my data?
{: .fs-9 }
Places you can share your data from
{: .fs-6 .fw-300 }
---
How you share your data (or where you share it from) will depend on the format of the data, the degree which you have been able to deidentify it, and your requirements for managed access or attribution.
Before sharing your data on any of these platforms, we suggest you:
1. Confirmed your requirements for [governance](../can-i-gov), [ethics](../can-i-ethics) and [reuse](../can-i-reuse).
2. [Deidentify](../can-i-deident) your data
3. Curate your [metadata](../can-i-meta)
After these stages have been considered one or a combination of these platforms may be appropriate for sharing your data.
## 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)](http://osf.io/). 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.**
When using OSF we recommend creating an account using your ORCID, ensuring your [ORCID is linked to your SSO](https://libguides.bodleian.ox.ac.uk/ORCID/orcid/register).
Take a look at this recording from the WIN Graduate program to learn more about OSF.
<div style="padding:56.25% 0 0 0;position:relative;"><iframe src="https://player.vimeo.com/video/668636108?h=35c6cf9f25&title=0&byline=0&portrait=0&speed=0&badge=0&autopause=0&player_id=0&app_id=58479/embed" allow="autoplay; fullscreen; picture-in-picture" allowfullscreen frameborder="0" style="position:absolute;top:0;left:0;width:100%;height:100%;"></iframe></div>
## NeuroVault
[NeuroVault](https://neurovault.org) 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
[OpenNeuro](https://openneuro.org) 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.**
**You should be confident that you have removed as many identifiable features as possible from all parts of the data, including ancillary files.**
You should also be satisfied with the licence conditions of adding your data to OpenNeuro, particularly that it can be reused for any purpose (including commercial) and users are not required to provide attribution for re-use of your data. Users are however *encouraged* to cite data depositors as good academic practice.
Each version of a dataset added to OpenNeuro is assigned a unique DOI
## WIN XNAT
The Open Data Working Group is building a searchable, user friendly [XNAT](https://www.xnat.org) 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)](https://bids.neuroimaging.io) 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
[WIN XNAT](https://xnat.win.ox.ac.uk) (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: [https://web.maillist.ox.ac.uk/ox/subscribe/win-open-data](https://web.maillist.ox.ac.uk/ox/subscribe/win-open-data)"
### 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.