From 4ae4e658420fd16888de6c22e89daf64e0c08fc2 Mon Sep 17 00:00:00 2001 From: Dimitri Papadopoulos <3234522+DimitriPapadopoulos@users.noreply.github.com> Date: Fri, 30 Jul 2021 14:37:05 +0200 Subject: [PATCH 1/2] Reorder words to make sense Increment DUA version. I'm fixing the English text only. While I could fix French and Greek too, I feel it is better to organize this for all languages or let initial translators handle this. --- docs/source/gdpr/data_user_agreement.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/source/gdpr/data_user_agreement.rst b/docs/source/gdpr/data_user_agreement.rst index dedb218..43dc547 100644 --- a/docs/source/gdpr/data_user_agreement.rst +++ b/docs/source/gdpr/data_user_agreement.rst @@ -32,7 +32,7 @@ English Data user agreement for accessing identifiable human data ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -**Version:** OBC-GDPR-DUA 1.0.0 +**Version:** OBC-GDPR-DUA 1.0.1 I request access to the data collected in the digital repository of the , part of the , established at , (hereinafter referred to as the ). @@ -41,7 +41,7 @@ By accepting this agreement, I become the `data controller ”. (b) Authors of publications or presentations using the data should cite relevant publications describing the methods developed and used by the to acquire and process the data. The specific publications that are appropriate to cite in any given study will depend on what the data were used and for what purposes. When applicable, a list of publications will be included in the collection. (c) Neither the or , nor the researchers that provide this data will be liable for any results and/or derived data. They shall not be included as an author of publications or presentations without consent. 6. Failure to abide by these guidelines will result in termination of my privileges to access these data. From a774b424c1be1f45f5d2d38fe510dd86b36832d7 Mon Sep 17 00:00:00 2001 From: Dimitri Papadopoulos <3234522+DimitriPapadopoulos@users.noreply.github.com> Date: Thu, 5 Aug 2021 22:33:26 +0200 Subject: [PATCH 2/2] to be on a group-level: what does this mean? I believe the intended phrase was: to be group-level data I find this alternative better (4.960.000 Google hits instead of 308.000): to be aggregate data --- docs/source/gdpr/data_user_agreement.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/gdpr/data_user_agreement.rst b/docs/source/gdpr/data_user_agreement.rst index 43dc547..15349ef 100644 --- a/docs/source/gdpr/data_user_agreement.rst +++ b/docs/source/gdpr/data_user_agreement.rst @@ -41,7 +41,7 @@ By accepting this agreement, I become the `data controller ”. (b) Authors of publications or presentations using the data should cite relevant publications describing the methods developed and used by the to acquire and process the data. The specific publications that are appropriate to cite in any given study will depend on what the data were used and for what purposes. When applicable, a list of publications will be included in the collection. (c) Neither the or , nor the researchers that provide this data will be liable for any results and/or derived data. They shall not be included as an author of publications or presentations without consent. 6. Failure to abide by these guidelines will result in termination of my privileges to access these data.