Skip to content

Commit

Permalink
Merge pull request #42 from AngelaKranz/patch-1
Browse files Browse the repository at this point in the history
Update DMPDocs230824.js
  • Loading branch information
xiaoranzhou authored Sep 12, 2024
2 parents e1cdc00 + 6b053b8 commit bd0061f
Showing 1 changed file with 9 additions and 10 deletions.
19 changes: 9 additions & 10 deletions DMPDocs/DMPDocs230824.js
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ dmpStrings={
</p>
<p class="c0">
<span class="c1">
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.
</span>
</p>
<p class="c0">
Expand Down Expand Up @@ -370,7 +370,7 @@ dmpStrings={
<span class="c1">
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.
</span>
Expand Down Expand Up @@ -590,11 +590,10 @@ dmpStrings={
</p>
<p class="c0">
<span class="c1">
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.
</span>
</p>
<p class="c0">
Expand Down Expand Up @@ -1781,7 +1780,7 @@ dmpStrings={
<span class="c1">
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
</span>
Expand All @@ -1791,7 +1790,7 @@ dmpStrings={
<p class="c0">
<span class="c1 list-to-remove-comma">
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
Expand Down Expand Up @@ -6156,4 +6155,4 @@ dmpStrings={
</div>`


}
}

0 comments on commit bd0061f

Please sign in to comment.