Skip to content

Commit

Permalink
Update user_docs/metadata/submitter_guide.md
Browse files Browse the repository at this point in the history
Co-authored-by: Jan Eufinger <[email protected]>
  • Loading branch information
mauerk and eufjan authored Aug 7, 2024
1 parent d9afb84 commit e13ffbd
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion user_docs/metadata/submitter_guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,9 @@ The classes [**Analysis**](https://docs.ghga.de/metadata/entities/#analysis) and

[**Process Data Files**](https://docs.ghga.de/metadata/entities/#process-data-file) are the output of an analysis and linked to it. The class functions similar to a Research Data File and requires submitters to define the matching file alias, type and analysis that generated them to link them to the remaining metadata.

Additionally, the submitter can embellish the classes with **Supplementary files**, such as experimental protocols for the experiment class, workflow parameter files for the analysis class or structured metadata, such as phenopackets or PED files for the individual class. Supplementary files are encrypted and inaccessible without an accepted data access request. This allows submission of metadata that should not be publicly visible as it can only be accessed by requesters after signing a data transfer agreement and decrypting the files. Hence, the data portal will only indicate the presence of supplementary files for classes and signify that a submission contains additional information, e.g. in the form of encrypted phenopackets for individuals, but not process or show their content.
Additionally, the submitter can embellish the classes with **Supplementary files**, such as experimental protocols for the experiment class, workflow parameter files for the analysis class or structured metadata, such as phenopackets or PED files for the individual class.
Supplementary files are encrypted and inaccessible without an accepted data access request.
This allows submission of metadata that should not be publicly visible **as it can only be accessed by requesters after the data controller has approved a data transfer request** and the data is made available via the portal to the data requester. Hence, the data portal will only indicate the presence of supplementary files for classes and signify that a submission contains additional information, e.g. in the form of encrypted phenopackets for individuals, but not process or show their content.

### Administrative Metadata
Once the experimental and analytic approach as well as the file generation have been described, the submitter can define the conditions on how to share the data.
Expand Down

0 comments on commit e13ffbd

Please sign in to comment.