Skip to content

Commit e634de8

Browse files
Merge pull request #3166 from antgonza/fix-3160
fix #3160
2 parents d472848 + f5d7f06 commit e634de8

File tree

2 files changed

+34
-48
lines changed

2 files changed

+34
-48
lines changed

qiita_pet/support_files/doc/source/checklist-for-ebi-ena-submission.rst

Lines changed: 30 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
11
.. role:: red
2+
.. _checklist-for-ebi-ena-submission:
23

34
Making data Public in Qiita and/or send data to EBI-ENA
45
=======================================================
@@ -22,6 +23,8 @@ time to request a submission is when you are writing your paper. Remember that t
2223
data can be submitted to EBI and can be kept private and simply make public when
2324
the paper is accepted. Note that EBI/ENA takes up to 15 days to change the status
2425
from private to public, so consider this when submitting data and your manuscript.
26+
If need help send an email to `[email protected] <mailto:[email protected]>`__
27+
and please include your study ID.
2528

2629
.. note::
2730
For convenience Qiita allows you to upload a QIIME mapping file to process your data. However,
@@ -43,7 +46,7 @@ For the latest definitions and explanation visit the `EBI/ENA Missing value repo
4346
Checklist
4447
---------
4548

46-
For each preparation that needs to be uploaded to EBI-ENA we will check:
49+
Remember, metadata is the most important part for an analysis, without it we only have sequences; thus, for each preparation that needs to be uploaded to EBI-ENA or become public we will check:
4750

4851
1. Data processing
4952

@@ -60,9 +63,11 @@ For each preparation that needs to be uploaded to EBI-ENA we will check:
6063
3. *sample_type*
6164
4. *taxon_id* - needs to match *scientific_name* value
6265
5. *scientific_name* - needs to match *taxon_id* value - this is the name of the `metagenome <https://www.ncbi.nlm.nih.gov/Taxonomy/Browser/wwwtax.cgi?mode=Tree&id=12908&lvl=3&srchmode=1&keep=1&unlock>`__ referenced in the column *taxon_id* and that the two values match. Submission will not work if the user puts *host_scientific_name* or *host_taxid* instead. Do not accept EBI null values. For null values use *scientific_name* “metagenome” and *taxon_id* “256318”
63-
6. *env_biome*, *env_feature*, *env_material*, *env_package*, for options `visit the ENVO section in <http://ols.wordvis.com/>`__
66+
6. *env_biome*, *env_feature*, *env_material*, *env_package*, for options `visit ENVO <http://ols.wordvis.com/>`__
6467
7. *elevation*, *latitude*, *longitude*
65-
8. *empo_1*, *empo_2*, *empo_3*
68+
8. *physical_specimen_location*
69+
9. *collection_timestamp*
70+
10. *empo_1*, *empo_2*, *empo_3*
6671

6772
.. table::
6873
:widths: auto
@@ -133,6 +138,28 @@ For each preparation that needs to be uploaded to EBI-ENA we will check:
133138
9. *instrument_model*
134139
10. *sequencing_method*
135140

141+
.. note::
142+
The current valid values for instrument_model per platform are - please contact us if you would like to add yours to this list:
143+
+---------------------+----------------------------------------------------------------------------------------------------------+
144+
| Platform | Valid instrument_model options |
145+
+=====================+==========================================================================================================+
146+
| ``LS454`` | ``454 GS``, ``454 GS 20``, ``454 GS FLX``, ``454 GS FLX+``, ``454 GS FLX Titanium``, ``454 GS Junior``, |
147+
| | ``454 GS Junior`` or ``unspecified`` |
148+
+---------------------+----------------------------------------------------------------------------------------------------------+
149+
| ``Illumina`` | ``HiSeq X Five``, ``HiSeq X Ten``, ``Illumina Genome Analyzer``, ``Illumina Genome Analyzer II``, |
150+
| | ``Illumina Genome Analyzer IIx``, ``Illumina HiScanSQ``, ``Illumina HiSeq 1000``, |
151+
| | ``Illumina HiSeq 1500``,, ``Illumina HiSeq 2000``, ``Illumina HiSeq 2500``, ``Illumina HiSeq 3000``, |
152+
| | ``Illumina HiSeq 4000``, ``Illumina MiSeq``, ``Illumina MiniSeq``, ``Illumina NovaSeq 6000``, |
153+
| | ``NextSeq 500``, ``NextSeq 550``, ``Illumina NovaSeq 6000`` or ``unspecified`` |
154+
+---------------------+----------------------------------------------------------------------------------------------------------+
155+
| ``Ion_Torrent`` | ``Ion Torrent PGM``, ``Ion Torrent Proton``, ``Ion Torrent S5``, ``Ion Torrent S5 XL`` |
156+
+---------------------+----------------------------------------------------------------------------------------------------------+
157+
| ``PacBio_SMRT`` | ``PacBio RS``, ``PacBio RS II``, ``Sequel``, ``Sequel II`` |
158+
+---------------------+----------------------------------------------------------------------------------------------------------+
159+
| ``Oxford_Nanopore`` | ``GridION`` |
160+
+---------------------+----------------------------------------------------------------------------------------------------------+
161+
162+
136163
c. Additional minimal columns, if possible:
137164

138165
1. *pcr_primers*

qiita_pet/support_files/doc/source/gettingstartedguide/index.rst

Lines changed: 4 additions & 45 deletions
Original file line numberDiff line numberDiff line change
@@ -87,20 +87,6 @@ Example files
8787
You can download an example sample information file from
8888
`here <ftp://ftp.microbio.me/pub/qiita/sample_prep_information_files_examples.tgz>`__.
8989

90-
EBI-ENA NULL values vocabulary
91-
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
92-
93-
For all public studies including those being submitted to EBI, no blanks are allowed in the sample information.
94-
We support the following null values: *not applicable*, *not collected*, *not provided*,
95-
*restricted access*.
96-
97-
For the latest definitions and explanation visit the `EBI/ENA Missing value reporting <http://www.ebi.ac.uk/ena/about/missing-values-reporting>`__.
98-
99-
.. warning::
100-
Column names in your information files cannot be named as a Postgres reserved word. For example, a column cannot be named
101-
`CONDITION`, but could instead be named `DISEASE_CONDITION`. For a full list of these reserved words, see this
102-
`link <https://www.postgresql.org/docs/9.3/static/sql-keywords-appendix.html>`__.
103-
10490

10591
Sample information file
10692
~~~~~~~~~~~~~~~~~~~~~~~
@@ -123,10 +109,11 @@ sample information file to be added to the system:
123109
| | | characters are alphabetic ``[A-Za-z]``, numeric ``[0-9]``, and periods ``.``. |
124110
+-------------------+-----------------------------+-------------------------------------------------------------------------------+
125111

126-
Required fields for EBI submission
127-
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
112+
Required fields for EBI submission and to make a study public
113+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
114+
115+
In order to submit your data to EBI, please review :ref:`checklist-for-ebi-ena-submission`.
128116

129-
In order to submit your data to EBI, certain fields are required in your sample information file. You can download a spread sheet containing these required fields on the `Knight Lab website <https://knightlab.ucsd.edu/wordpress/?page_id=478>`__ under "MetaData Template".
130117

131118
Attaching the Sample Information to the Study
132119
---------------------------------------------
@@ -272,34 +259,6 @@ prep information file to be added to the system:
272259
| | | match the sample_name in the sample template. |
273260
+-------------------+-------------------------------+------------------------------------------------------------------------+
274261

275-
Required fields for EBI submission
276-
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
277-
278-
279-
In order to submit your data to EBI, certain fields are required in your preparation information file. You can download a spread sheet containing these required fields on the `Knight Lab website <https://knightlab.ucsd.edu/wordpress/?page_id=478>`__ under "Prep Template".
280-
281-
282-
For all valid values for instrument_model per platform, view the values in the table below:
283-
284-
+---------------------+----------------------------------------------------------------------------------------------------------+
285-
| Platform | Valid instrument_model options |
286-
+=====================+==========================================================================================================+
287-
| ``LS454`` | ``454 GS``, ``454 GS 20``, ``454 GS FLX``, ``454 GS FLX+``, ``454 GS FLX Titanium``, ``454 GS Junior``, |
288-
| | ``454 GS Junior`` or ``unspecified`` |
289-
+---------------------+----------------------------------------------------------------------------------------------------------+
290-
| ``Illumina`` | ``HiSeq X Five``, ``HiSeq X Ten``, ``Illumina Genome Analyzer``, ``Illumina Genome Analyzer II``, |
291-
| | ``Illumina Genome Analyzer IIx``, ``Illumina HiScanSQ``, ``Illumina HiSeq 1000``, |
292-
| | ``Illumina HiSeq 1500``,, ``Illumina HiSeq 2000``, ``Illumina HiSeq 2500``, ``Illumina HiSeq 3000``, |
293-
| | ``Illumina HiSeq 4000``, ``Illumina MiSeq``, ``Illumina MiniSeq``, ``Illumina NovaSeq 6000``, |
294-
| | ``NextSeq 500``, ``NextSeq 550``, ``Illumina NovaSeq 6000`` or ``unspecified`` |
295-
+---------------------+----------------------------------------------------------------------------------------------------------+
296-
| ``Ion_Torrent`` | ``Ion Torrent PGM``, ``Ion Torrent Proton``, ``Ion Torrent S5``, ``Ion Torrent S5 XL`` |
297-
+---------------------+----------------------------------------------------------------------------------------------------------+
298-
| ``PacBio_SMRT`` | ``PacBio RS``, ``PacBio RS II``, ``Sequel``, ``Sequel II`` |
299-
+---------------------+----------------------------------------------------------------------------------------------------------+
300-
| ``Oxford_Nanopore`` | ``GridION`` |
301-
+---------------------+----------------------------------------------------------------------------------------------------------+
302-
303262

304263
Required fields for pre-processing target gene data
305264
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

0 commit comments

Comments
 (0)