Click here to close Hello! We notice that you are using Internet Explorer, which is not supported by Xenbase and may cause the site to display incorrectly. We suggest using a current version of Chrome, FireFox, or Safari.

How to get NGS data from EMBL-EBI in to the Xenbase-GEO pipeline.

The Xenbase NGS pipeline processes RNA-Seq and ChIP-seq data from the NCBI's GEO archive so that it is searchable, comparable and can be viewed on our genome viewer, JBrowse: see geneExpression/

It is important to know that NGS data that has been deposited with the EBI, is shared with the NCBI's BIOProject database, but that it does not then migrate automatically to GEO, and therefore Xenbase will NOT be able to automatically process your RNA-seq data.

So how can you get your NGS data into GEO if you have already submitted it to EMBL-EBI?

[1] Reference the SRA Study accession (SRPnnnn) and BioProject accession (PRJNAnnnn) in the SERIES 'Overall design' field.

[2] In the 'raw file' column of the SAMPLES section, please list the corresponding SRA Experiment accessions (SRXnnnnnn) so that we can create the appropriate links between the SRA Experiments and GEO Samples.

[3] Add a 'BioSample' column to the SAMPLES section and include the corresponding BioSample accessions (SAMNnnnnnn).

[4] Add an 'instrument model' column to the SAMPLES section and indicate the instrument model that was used for sequencing.

Note that you do not need to fill in the 'RAW FILES' or 'PAIRED-END EXPERIMENTS' sections.

Then follow these additional steps:

[5] Upload the Metadata template and processed data files to GEO.

FTP instructions for depositing sequencing data to GEO are here:

[6] If you have previously contacted GEO and received an email reply from them [i.e, from,] please reference the issue/ticket number the NCBI tracking system gave you [eg #29999555) so that the GEO curator processing your submission is aware of any correspondence.

Researchers who have followed these steps reported that it was easy and straight forward, but please let Xenbase know if you have any trouble: