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

restructure can-i nav to single page

parent 73bd7e8d
Pipeline #13475 passed with stages
in 2 minutes and 11 seconds
---
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>
<p>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.</p>
<p><b>File formats</b> are an important feature of FAIR standards. In all cases you should aim to release your data in non-proprietary formats (for example comma separated values <code>csv</code> rather than excel <code>xsl</code>).</p>
<p>Shared data should be <a href="https://en.wikipedia.org/wiki/Machine-readable_data">machine readable</a> where possible, and any non-imaging data should be provided in a <b>single file containing all measures</b> (for example covariates, behavioural measures, clinical outcomes). This data should be accompanied by a <b>data dictionary</b> which describes each of the variables included, how they were derived and where to obtain the source data where possible.</p>
<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>
This diff is collapsed.
......@@ -18,9 +18,9 @@ Places you can share your data from
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)
1. Confirm your requirements for [governance](../can-i#governance), [ethics](../can-i#ethics) and [reuse](../can-i#appropriate-reuse).
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.
......
......@@ -20,8 +20,8 @@ The stage of your project will add constraints to your data sharing plans
| Stage | If you start thinking about data sharing now |
|:-:|:--|
| ![cani-reuse](../../../img/img-when-planning.png) **Planning** | While you are still planning your project you can address issues of [governance](../can-i-gov) which might prohibit you from sharing your data in its most impactful form. It is also useful to know [where you will share your data from](../how), and understand the requirements of that tool. You will need to have a good idea of the format of your data as it changes through the project, and what would be the most valuable material to share. |
| ![cani-reuse](../../../img/img-when-data-coll.png) **Data collection** | If you have already started collecting your data, review your [governance documents](../can-i-gov) and understand the limits of what is possible given the agreements in place. If you are able to share your data, you should begin [collating metadata and organising your data according to community standards](../can-i-meta). Think about what material you ultimately would like to share and [where you will share it data from](../how) |
| ![cani-reuse](../../../img/img-when-planning.png) **Planning** | While you are still planning your project you can address issues of [governance](../can-i#governance) which might prohibit you from sharing your data in its most impactful form. It is also useful to know [where you will share your data from](../how), and understand the requirements of that tool. You will need to have a good idea of the format of your data as it changes through the project, and what would be the most valuable material to share. |
| ![cani-reuse](../../../img/img-when-data-coll.png) **Data collection** | If you have already started collecting your data, review your [governance documents](../can-i#governance) and understand the limits of what is possible given the agreements in place. If you are able to share your data, you should begin [collating metadata and organising your data according to community standards](../can-i#metadata). Think about what material you ultimately would like to share and [where you will share it data from](../how) |
| ![cani-reuse](../../../img/img-when-anal.png) **Analysis** | Quisque congue aliquam tellus ac pulvinar. Quisque eget urna libero. Donec aliquam dolor ex, nec semper purus suscipit sit amet. Interdum et malesuada fames ac ante ipsum primis in faucibus. Ut posuere justo felis, sed auctor metus pellentesque et. Praesent mattis ut eros et luctus. Proin faucibus commodo ligula. Quisque orci sem, aliquet nec lorem vel, aliquet tempus dolor. Proin ac auctor elit, mollis sollicitudin nulla. Vivamus egestas nisi lacinia rhoncus tristique. Maecenas sit amet metus vel erat posuere mollis a id felis. Pellentesque ut enim vel sapien scelerisque convallis. Fusce sed nunc eu augue pharetra tempus. |
| ![cani-reuse](../../../img/img-when-writing.png) **Writing up** | Quisque congue aliquam tellus ac pulvinar. Quisque eget urna libero. Donec aliquam dolor ex, nec semper purus suscipit sit amet. Interdum et malesuada fames ac ante ipsum primis in faucibus. Ut posuere justo felis, sed auctor metus pellentesque et. Praesent mattis ut eros et luctus. Proin faucibus commodo ligula. Quisque orci sem, aliquet nec lorem vel, aliquet tempus dolor. Proin ac auctor elit, mollis sollicitudin nulla. Vivamus egestas nisi lacinia rhoncus tristique. Maecenas sit amet metus vel erat posuere mollis a id felis. Pellentesque ut enim vel sapien scelerisque convallis. Fusce sed nunc eu augue pharetra tempus. |
| ![cani-reuse](../../../img/img-when-submission.png) **Publishing** | Maecenas a neque et neque pretium gravida. Suspendisse in risus accumsan, accumsan libero sit amet, fringilla dolor. Mauris ut augue risus. Morbi sed pulvinar odio, quis elementum elit. Maecenas nec malesuada urna. Fusce mattis ante quis erat mollis pharetra. Praesent faucibus tempor massa. Morbi vel pretium mi. Aenean ac dictum nulla, vel dignissim magna. Phasellus eu suscipit lorem, ac vestibulum est. Nullam ut velit est. Ut sit amet laoreet ex. Donec eu tortor eros. Etiam sit amet ligula sit amet urna ultrices vulputate et quis tortor. |
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