From 6b053b86bec3946f1a7c2d084d3eaef46af9c9f1 Mon Sep 17 00:00:00 2001 From: Angela Kranz <77975677+AngelaKranz@users.noreply.github.com> Date: Sat, 7 Sep 2024 20:00:26 +0200 Subject: [PATCH] Update DMPDocs230824.js --- DMPDocs/DMPDocs230824.js | 19 +++++++++---------- 1 file changed, 9 insertions(+), 10 deletions(-) diff --git a/DMPDocs/DMPDocs230824.js b/DMPDocs/DMPDocs230824.js index 1811a05..7750d94 100644 --- a/DMPDocs/DMPDocs230824.js +++ b/DMPDocs/DMPDocs230824.js @@ -91,7 +91,7 @@ dmpStrings={

- The aim of this document is to provide guidelines on the principles of data management in $_PROJECTNAME. A Data Management Plan (DMP) will generated by using the responses to the EU questionnaire on DMP, which defines the data stored in $_PROJECTNAME. + The aim of this document is to provide guidelines on the principles of data management in $_PROJECTNAME. A Data Management Plan (DMP) will be generated by using the responses to the EU questionnaire on DMP, which defines the data stored in $_PROJECTNAME.

@@ -370,7 +370,7 @@ dmpStrings={ Data variables will be allocated standard names. For example, genes, proteins and metabolites will be named according to approved nomenclature and conventions. These will also be linked to functional - ontologies where possible. Datasets will also be named I a meaningful way to ensure readability by + ontologies where possible. Datasets will also be named in a meaningful way to ensure readability by humans. Plant names will include traditional names, binomials, and all strain/cultivar/subspecies/variety identifiers. @@ -590,11 +590,10 @@ dmpStrings={

- Where data are shared only within the consortium, if the datasets are not yet finished or are - undergoing IP checks, the data will be hosted internally and a username and password will be - required for access (see GDPR rules). When the data are made public in EU or US repositories, - completely anonymous access is normally allowed. This is the case for ENA as well and both are in - line with GDPR requirements. + When data are shared only within the consortium, if the datasets are not yet complete or are undergoing + IP checks, the data will be hosted internally, requiring a username and password for access (see GDPR rules). + Once the data are made public in EU or US repositories, completely anonymous access is typically allowed. + This applies to ENA as well, and both are in line with GDPR requirements.

@@ -1781,7 +1780,7 @@ dmpStrings={ Online platforms will be protected by vulnerability scanning, two-factor authorization and daily automatic backups allowing immediate recovery. All partners holding confidential project data will use secure platforms with automatic backups and offsite secure copies. - #if$_DATAPLANT As ARCs are stored in the PlantDataHub of DataPLANT, data security will be imposed. + #if$_DATAPLANT As ARCs are stored in the PLANTDataHUB of DataPLANT, data security will be imposed. This comprises secure storage, and the use of password and usernames is generally transferred via separate safe media. #endif$_DATAPLANT @@ -1791,7 +1790,7 @@ dmpStrings={

- As mentioned above, data will be made archived in + As mentioned above, data will be archived in international discipline related repositories which use specialized technologies: #if$_GENETIC|$_GENOMIC #if$_GENBANK NCBI-GenBank, #endif$_GENBANK #if$_ENA EBI-ENA, #endif$_ENA #endif$_GENETIC|$_GENOMIC #if$_TRANSCRIPTOMIC|$_GENETIC #if$_SRA NCBI-SRA, #endif$_SRA #if$_GEO NCBI-GEO, #endif$_GEO #endif$_TRANSCRIPTOMIC|$_GENETIC #if$_TRANSCRIPTOMIC|$_GENOMIC #if$_ARRAYEXPRESS @@ -6156,4 +6155,4 @@ dmpStrings={ ` -} \ No newline at end of file +}