From bf15b3c848810938b8eda0095bf145460e1c3f4a Mon Sep 17 00:00:00 2001
From: Cassandra Gould van Praag <casssandra.gouldvanpraag@psych.ox.ac.uk>
Date: Wed, 27 Apr 2022 21:16:58 +0100
Subject: [PATCH] fill out project stages
---
docs/data/when.md | 19 ++++++++++---------
1 file changed, 10 insertions(+), 9 deletions(-)
diff --git a/docs/data/when.md b/docs/data/when.md
index 2ab155a3..f27b7386 100644
--- a/docs/data/when.md
+++ b/docs/data/when.md
@@ -15,16 +15,17 @@ The stage of your project will add constraints to your data sharing plans
---
-<!-- Sharing your data can be a significant step change from traditional modes of research which concentrate on the final manuscript only. To most effectively prepare your project for this change, it can be useful to consider your requirements for sharing at the point of project planning. -->
+Sharing data can be hard if you have not built in the intention to share from the outset. Below we describe what actions you can be taking at each stage of your project to ensure your data sharing is efficient and stress free!
-Coming soon
-{: .label .label-yellow }
+<!-- Coming soon
+{: .label .label-yellow } -->
-| Stage | If you start thinking about data sharing now |
+
+| Stage | What to think about now
|:-:|:--|
-|  **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. |
-|  **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) |
-|  **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. |
-|  **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. |
-|  **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. |
+|  **Planning** | When your project is in the planning stage, you can think think carefully about the [ethical](../can-i#ethics), [governance](../can-i#governance) and [identifiability](../can-i#deidentification) issues which might limit your ability to share your data completely openly. Once you know the limits of what is theoretically possible, you can describe how you can achieve this practically in a data management plan. |
+|  **Data collection** | While collecting your data, you can begin to [collate metadata and organise your data according to community standards](../can-i#metadata). You should also aim to work with non-proprietary file file formats where possible. |
+|  **Analysis** | While you are analysing your data, be mindful of the restrictions which might be necessary to ensure the shared data are maximally [deidentified](../can-i#deidentification). For example, it might be preferable to conduct your analysis using binned categorical data rather than continuous variables which make individual participants more identifiable. Consider writing your code in a way that allows for flexible and efficient re-analysis on any such factors. You should also keep an active [data dictionary](https://faircookbook.elixir-europe.org/content/recipes/interoperability/creating-data-dictionary.html), where you describe the variables you create, how they are named in your code or data, and how they are derived. |
+|  **Writing up** | While writing up your project, think about the reason you are sharing your data. If you are sharing data so another researcher can validate your figures, should focus on ensuring the data (and code) required for that purpose are accessible and well described. If you are sharing a larger or more complete data set, you may wish to focus on ensuring that the value in the reuse of that data is appropriately emphasised and 'advertised' in your project write-up, or consider publishing a separate [data paper](https://the-turing-way.netlify.app/reproducible-research/rdm/rdm-article.html). |
+|  **Publishing** | You should aim to have all of your data available in your [intended repository]((../how) *before you submit your project manuscript to a journal for publication*. Your repository may have specific metadata requirements (much like journal formatting guidelines) and in some cases the data may need to be reviewed before it is made public (for example [EBRAINS](https://ebrains.eu)), so sharing it may take some time. By having the data available in advance of submission, you can include a persistent digital object identifier (doi) or reviewer-only access link with your manuscript submission. Ensure that you have carefully considered [how contributors to your data will be recognised](../can-i#contributor-attribution).|
--
GitLab