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

remove all line breaks

parent cd4ec292
# Data Sharing Decision Tree - Refactored to questions
<!-- <details>
<summary>Question?</summary><br>
<summary>Question?</summary>
details
</details> -->
......@@ -11,42 +11,42 @@ details
## Why should I share my data?
<details>
<summary>To create a citable research output</summary><br>
Collecting and curating your research data is often a huge undertaking which requires significant skill and expertise. You deserve to receive credit for the data you have created as an independent research object, over and above any publish manuscript. We will help you to share your data in a way that it can exist as a citable research object, on your CV and the digital realm.<br>
<summary>To create a citable research output</summary>
Collecting and curating your research data is often a huge undertaking which requires significant skill and expertise. You deserve to receive credit for the data you have created as an independent research object, over and above any publish manuscript. We will help you to share your data in a way that it can exist as a citable research object, on your CV and the digital realm.
</details>
<br>
<details>
<summary>Publisher requirement</summary><br>
<summary>Publisher requirement</summary>
Many publishers will now require you to share data, so your research findings can be verified. Our infrastructure will enable you to fulfil these requirements. Caution: Don't wait until you are about to publish before thinking about data sharing! It is much easier to share data if you have built in sharing as part of your study.
</details>
<br>
<details>
<summary>Funders want to make the most of their investment</summary><br>
<summary>Funders want to make the most of their investment</summary>
details
</details>
<br>
<details>
<summary>Sharing is becoming the norm</summary><br>
<summary>Sharing is becoming the norm</summary>
details
</details>
<br>
<details>
<summary>A sustainable platform and archive of your data</summary><br>
<summary>A sustainable platform and archive of your data</summary>
details
</details>
<br>
<details>
<summary>Speeds up translation</summary><br>
<summary>Speeds up translation</summary>
details
</details>
......@@ -56,15 +56,15 @@ details
<!-- -->
<details>
<summary>Is sharing restricted under Intellectual Properties rights?</summary><br>
<summary>Is sharing restricted under Intellectual Properties rights?</summary>
<details>
<summary>Has your funder or industry partner approved data sharing?</summary><br>
<summary>Has your funder or industry partner approved data sharing?</summary>
details
</details>
<details>
<summary>Have you investigated commercial potential of your data?</summary><br>
<summary>Have you investigated commercial potential of your data?</summary>
details
</details>
......@@ -73,12 +73,12 @@ details
<!-- -->
<details>
<summary>Do your data need protecting?</summary><br>
<summary>Do your data need protecting?</summary>
<!-- -->
<details>
<summary>Are you sharing data acquired from living humans?</summary><br>
<summary>Are you sharing data acquired from living humans?</summary>
GDPR restrictions relate only to data acquired from living humans.
If you have collected **non-human data**:
......@@ -100,12 +100,12 @@ details
<!-- -->
<details>
<summary>Have you considered data governance with respect to sharing?</summary><br>
<summary>Have you considered data governance with respect to sharing?</summary>
<!-- -->
<details>
<summary>Have you discussed open data sharing in your data management plan?</summary><br>
<summary>Have you discussed open data sharing in your data management plan?</summary>
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.
Find out more about how the University can [support you in creating a data management plan](https://researchdata.ox.ac.uk/home/managing-your-data-at-oxford/data-management-planning/)
......@@ -116,7 +116,7 @@ details
</details>
<details>
<summary>Have you completed a Data Protection Impact Assessment (DPIA) screening form which references data sharing?</summary><br>
<summary>Have you completed a Data Protection Impact Assessment (DPIA) screening form which references data sharing?</summary>
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 [Data Protection Impact Assessment (DPIA) Screening form](https://compliance.admin.ox.ac.uk/data-protection-forms#collapse1091641)
......@@ -128,18 +128,18 @@ details
<!-- -->
<details>
<summary>Do you have ethical approvals in place?</summary><br>
<summary>Do you have ethical approvals in place?</summary>
<!-- -->
<details>
<summary>Have you described data sharing in your ethics application</summary><br>
<summary>Have you described data sharing in your ethics application</summary>
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 [CUREC Approved Procedure 17](https://researchsupport.admin.ox.ac.uk/governance/ethics/resources/ap#collapse397171) (version 6.0+) statement fulfilling this requirement will be included.
</details>
<details>
<summary>Has your participant consented to data sharing?</summary><br>
<summary>Has your participant consented to data sharing?</summary>
Many consent forms have a separate section or box to indicate the participant is aware of your data sharing plans (box 4 on the [Approved Procedure 17 consent form](https://researchsupport.admin.ox.ac.uk/governance/ethics/resources/ap#collapse397171)). Has your participant indicated they have agreed to data sharing as you have described?
</details>
......@@ -148,23 +148,23 @@ details
<!-- -->
<details>
<summary>Have you de-identified your data?</summary><br>
<summary>Have you de-identified your data?</summary>
<!-- -->
<details>
<summary>Have you removed any "direct identifiers" in your data?</summary><br>
<summary>Have you removed any "direct identifiers" in your data?</summary>
Direct identifiers include...
</details>
<details>
<summary>Are your imaging data in participant space?</summary><br>
<summary>Are your imaging data in participant space?</summary>
Participant space (cortical structure) is unique to an individual. 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 far as possible and appropriate for your analysis.
</details>
<details>
<summary>Have your Participant IDs been protected?</summary><br>
<summary>Have your Participant IDs been protected?</summary>
Are any keys which link researcher generated Participant IDs and WIN generated Scan ID Participant 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 (Jones and Ford, 2018)? In practice, this is achieved by following CUREC BPG 09, 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" ([CUREC BPG 09](https://researchsupport.admin.ox.ac.uk/files/bpg09datacollectionandmanagementpdf)) 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).
......@@ -172,27 +172,27 @@ details
<details>
<summary>Have "indirect identifiers" such as age, gender, handedness or disease status been protected?</summary><br>
<summary>Have "indirect identifiers" such as age, gender, handedness or disease status been protected?</summary>
Consider combining "indirect identifiers" ([CUREC BPG 09](https://researchsupport.admin.ox.ac.uk/files/bpg09datacollectionandmanagementpdf)) into bins such that no participant can be uniquely identified. Ideally bins should contain < 5 participants.
</details>
<details>
<summary>Have unique dicom fields been scrubbed?</summary><br>
<summary>Have unique dicom fields been scrubbed?</summary>
If you are sharing dicom data, you should scrub the dicom headers of all identifiable and unique fields.
</details>
<details>
<summary>Have unique fields in .json sidecar files been scrubbed?</summary><br>
<summary>Have unique fields in .json sidecar files been scrubbed?</summary>
If you are sharing nifti data with json sidecar files, you should scrub the .json files of all identifiable and unique fields.
</details>
<details>
<summary>Have images been defaced?</summary><br>
<summary>Have images been defaced?</summary>
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.
</details>
<details>
<summary>Have you conducted and prepared to share a quality control analysis?</summary><br>
<summary>Have you conducted and prepared to share a quality control analysis?</summary>
It is good practice to share a quality control (QC) analysis. Consider using mriqc.
</details>
......@@ -201,7 +201,7 @@ details
<!-- -->
<details>
<summary>Have you prepared the data according to community standards?</summary><br>
<summary>Have you prepared the data according to community standards?</summary>
BIDS, BEPs
</details>
......@@ -209,40 +209,40 @@ details
<details>
<summary>Have you prepared the metadata to make your data FAIR?</summery><br>
<summary>Have you prepared the metadata to make your data FAIR?</summery>
<!-- -->
<details>
<summary>Are behavioural and clinical covariates appropriately described?</summary><br>
<summary>Are behavioural and clinical covariates appropriately described?</summary>
Measured results for each participant should be provided in a single file containing all covariates, in appropriately [machine readable structure](https://en.wikipedia.org/wiki/Machine-readable_data).
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.
</details>
<details>
<summary>Are you able to share the image acquisition protocol?</summary><br>
<summary>Are you able to share the image acquisition protocol?</summary>
Consider adding the MR protocol and scanning procedure documents to the [MR Protocols database](https://open.win.ox.ac.uk/protocols/). Add a link to your database entry in your shared data.
</details>
<details>
<summary>Has the experimental protocol been described and made ready to share with the data?</summary><br>
<summary>Has the experimental protocol been described and made ready to share with the data?</summary>
Minimal experimental detail is as described in the dataset_descriptor.json file which is generated during BIDS conversion.
</details>
</details>
<details>
<summary>Can access to my data be restricted?</summary><br>
<summary>Can access to my data be restricted?</summary>
<!-- -->
<details>
<summary>Can I create a "reviewer only" link?<summary><br>
<summary>Can I create a "reviewer only" link?<summary>
In some cases you may wishe to make your data available only to a reviewer before makeing it available for wider release. Is this possible with your intended repository?
</details>
<details>
<summary>Can I restrict access to bonafide researchers only?</summary><br>
<summary>Can I restrict access to bonafide researchers only?</summary>
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 [ORCID ID](https://orcid.org)?
</details>
......@@ -251,18 +251,18 @@ details
<!-- -->
<details>
<summary>Can I make sure that I am appropriately acknowledged when my data are reused?</summary><br>
<summary>Can I make sure that I am appropriately acknowledged when my data are reused?</summary>
<!-- -->
<details>
<summary>Can I create a doi for my data?</summary><br>
<summary>Can I create a doi for my data?</summary>
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.
</details>
<details>
<summary>Can I select a license which requires attribution ?</summary><br>
<summary>Can I select a license which requires attribution ?</summary>
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 [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/). You may additionally like to apply a license which restricts commercial use (for example [CC-BY-NC-4.0](https://creativecommons.org/licenses/by-nc/4.0/legalcode)), allowing commercial use to be negotiated by the University.
</details>
......@@ -273,20 +273,20 @@ details
<details>
<summary>Can I impose custom terms around the reuse of your data?</summary><br>
<summary>Can I impose custom terms around the reuse of your data?</summary>
<details>
<summary>Can you impose requirements for authorship?</summary><br>
<summary>Can you impose requirements for authorship?</summary>
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?
</details>
<details>
<summary>Can you impose restrictions on resharing?</summary><br>
<summary>Can you impose restrictions on resharing?</summary>
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?
</details>
<details>
<summary>Can you explicitly prohibit attempts to reidentify participants in your data</summary><br>
<summary>Can you explicitly prohibit attempts to reidentify participants in your data</summary>
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 reidentify your participants, for example via linkage to other public sphere or experimental data. Is it possible to impose such requirements with your intended repository?
</details>
......@@ -303,7 +303,7 @@ details
## How do I share my data?
<!-- <details>
<summary>Question?</summary><br>
<summary>Question?</summary>
details
</details> -->
......
Markdown is supported
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