-
Notifications
You must be signed in to change notification settings - Fork 3
Add documentation for NGS data with metadata #68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -40,6 +40,7 @@ openBIS. | |||||
| Formats: | ||||||
|
|
||||||
| - [NGS single-end / paired-end data](#ngs-single-end--paired-end-data) | ||||||
| - [NGS single-end / paired-end data with metadata (deprecated)](#ngs-single-end--paired-end-data-with-metadata-(deprecated)) | ||||||
|
|
||||||
| ### NGS single-end / paired-end data | ||||||
|
|
||||||
|
|
@@ -81,4 +82,59 @@ look like this: | |||||
| |-- <QBIC sample code>.fastq.gz.sha256sum | ||||||
| ``` | ||||||
|
|
||||||
| ### NGS single-end / paired-end data with metadata (deprecated) | ||||||
|
|
||||||
| **Disclaimer!** | ||||||
| This data format is targeted for a single use case and should not be | ||||||
| used for general data registration purposes. Please use the | ||||||
| [NGS single-end / paired-end data](#ngs-single-end--paired-end-data) | ||||||
| format for now. | ||||||
|
|
||||||
| **Responsible dropbox:** | ||||||
| [QBiC-register-imgag-dropbox](drop-boxes/register-imgag-dropbox) | ||||||
|
|
||||||
| **Resulting data model in openBIS** | ||||||
| Q_TEST_SAMPLE -> Q_NGS_SINGLE_SAMPLE_RUN (with sample code) -> DataSet | ||||||
| of type Q_NGS_RAW_DATA (directory with raw sequencing files contained) | ||||||
|
Comment on lines
+97
to
+98
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I cannot verify if this is the structure. I did not find an openbis project for that so I will trust you here :) |
||||||
|
|
||||||
| Example sample ids: | ||||||
|
|
||||||
| QABCD001AE (Analyte, Q_TEST_SAMPLE) | ||||||
| NGS[0-9]{2}QABCS001AE (Sequencing Result, Q_NGS_SINGLE_SAMPLE_RUN) where | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Since we also give example for the codes I think its ok to also avoid the regex here
Suggested change
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think it is important to now, how the code will look like. It will be always to digit, from 00-99. |
||||||
| the running two-digit number is taken from the identifier suffix from | ||||||
| the `genetics_id` in the metadata file. | ||||||
|
|
||||||
| **Description** | ||||||
| For paired-end sequencing reads in FASTQ format, the file structure | ||||||
| needs to look like this | ||||||
|
|
||||||
| ``` | ||||||
| <QBIC sample code> // Directory | ||||||
| |-- file1.fastq.gz | ||||||
| |-- file2.fastq.gz | ||||||
| |-- metadata | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. maybe make it more explicit
Suggested change
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. no, its |
||||||
| |- ... | ||||||
| ``` | ||||||
|
|
||||||
| **Expected metadata** | ||||||
| Additional metadata is required in this format case and expected to be | ||||||
| noted in JSON in a file called `metadata` and following the | ||||||
| [upload metadata schema](drop-boxes/register-imgag-dropbox/upload-metadata.schema.json). | ||||||
| A valid JSON object can look like this: | ||||||
|
|
||||||
| ``` | ||||||
| { | ||||||
| "files": [ | ||||||
| "reads.1.fastq.gz", | ||||||
| "reads.2.fastq.gz" | ||||||
| ], | ||||||
| "type": "dna_seq", | ||||||
| "sample1": { | ||||||
| "genome": "GRCh37", | ||||||
| "id_genetics": "GS000000_01", | ||||||
| "id_qbic": "QTEST002AE", | ||||||
| "processing_system": "Test system", | ||||||
| "tumor": "no" | ||||||
| } | ||||||
| } | ||||||
| ``` | ||||||
|
Comment on lines
+125
to
+140
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nice, I like the example! |
||||||
This file was deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe point out what differentiates the two registration processes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thats deep business, i actually would not like to have it here.