<p>If you already have a reference transcriptome assembly, then you may run the Salmon tool for quantification using your RNA-seq samples. It has an automated library type inference function (<a href="https://salmon.readthedocs.io/en/latest/salmon.html#what-s-this-libtype" rel="nofollow noreferrer">https://salmon.readthedocs.io/en/latest/salmon.html#what-s-this-libtype</a>). It might help you to determine whether the libs are stranded or not.</p>

CC BY-SA 4.0
2020-06-05T03:37:00.753Z
2020-06-05T03:37:00.753Z
thomas duge de bernonville
<p>Unfortunately, the stranded nature of cDNA sequencing is not typically included in the metadata attached to a project, which means that downloading a small subset of the data and checking for strand consistency (as suggested by <a href="https://bioinformatics.stackexchange.com/a/13474/73">the other answer</a>) is often the quickest way to work that out (when that information isn't included in the methods section of the associated paper). This knowledge is not particularly useful for casually browsing projects to find a stranded protocol that fits a particular study specification.</p>

<p>Sometimes you get lucky, but not often. GEO RNASeq datasets <em>usually</em> have links to the SRA accessions, and those accessions <em>usually</em> include annotation about the library type. For example, consider this dataset on GEO:</p>

<p><a href="https://www.ncbi.nlm.nih.gov/geo/query/acc.cgi?acc=GSE151535" rel="nofollow noreferrer">https://www.ncbi.nlm.nih.gov/geo/query/acc.cgi?acc=GSE151535</a></p>

<p>It links to SRP265460 on SRA. Following the link for the first run for this project, I get to here:</p>

<p><a href="https://www.ncbi.nlm.nih.gov/sra/SRX8436504[accn]" rel="nofollow noreferrer">https://www.ncbi.nlm.nih.gov/sra/SRX8436504[accn]</a></p>

<p>This includes the following metadata about the run:</p>

<blockquote>
  <p><em>Instrument:</em> NextSeq 500<br>
  <em>Strategy:</em> RNA-Seq<br>
  <em>Source:</em> TRANSCRIPTOMIC<br>
  <em>Selection:</em> cDNA<br>
  <em>Layout:</em> SINGLE<br>
  <em>Construction protocol:</em> Replicates of oropharyngeal explants at different stages of development (37/38, 39, 41) were immersed in RNALater. Samples were homogenized with a Dounce homogenizer in RLT buffer containing ß-mercaptoethanol (Qiagen). The homogenate was then processed using an RNAEasy kit (Qiagen, Hilden, Germany). Replicate samples for each stage were analyzed for RNA quantity and quality on a Nanodrop 8000 spectrophotometer. RNA libraries were prepared for sequencing using standard Illumina protocols</p>
</blockquote>

<p>But, as you can see, there's nothing about whether its stranded or not: Illumina has both stranded and unstranded "standard" protocols.</p>

CC BY-SA 4.0
2020-06-05T22:16:34.723Z
2020-06-05T22:16:34.723Z
gringer
<p>I would like to use RNA-seq data from the NIH GEO database. How can I tell if library generation for the RNA-seq experiments are stranded vs not stranded?</p>

<rna-seq><geo>
How to tell if library generation for RNA-seq experiments are stranded vs not stranded
# How to tell if library generation for RNA-seq experiments are stranded vs not stranded

(Asked by: username_0 on 2020-06-04)

I would like to use RNA-seq data from the NIH GEO database. How can I tell if library generation for the RNA-seq experiments are stranded vs not stranded?

**Tags:** rna-seq, geo

---

## 2 answers

### Answer by username_1 on 2020-06-05. Score: 3 | Accepted answer

If you already have a reference transcriptome assembly, then you may run the Salmon tool for quantification using your RNA-seq samples. It has an automated library type inference function (<https://salmon.readthedocs.io/en/latest/salmon.html#what-s-this-libtype>). It might help you to determine whether the libs are stranded or not.


---

### Answer by username_2 on 2020-06-05. Score: 2

Unfortunately, the stranded nature of cDNA sequencing is not typically included in the metadata attached to a project, which means that downloading a small subset of the data and checking for strand consistency (as suggested by [the other answer](https://bioinformatics.stackexchange.com/a/13474/73)) is often the quickest way to work that out (when that information isn't included in the methods section of the associated paper). This knowledge is not particularly useful for casually browsing projects to find a stranded protocol that fits a particular study specification.

Sometimes you get lucky, but not often. GEO RNASeq datasets *usually* have links to the SRA accessions, and those accessions *usually* include annotation about the library type. For example, consider this dataset on GEO:

<https://www.ncbi.nlm.nih.gov/geo/query/acc.cgi?acc=GSE151535>

It links to SRP265460 on SRA. Following the link for the first run for this project, I get to here:

<https://www.ncbi.nlm.nih.gov/sra/SRX8436504[accn]>

This includes the following metadata about the run:

> *Instrument:* NextSeq 500  
> *Strategy:* RNA-Seq  
> *Source:* TRANSCRIPTOMIC  
> *Selection:* cDNA  
> *Layout:* SINGLE  
> *Construction protocol:* Replicates of oropharyngeal explants at different stages of development (37/38, 39, 41) were immersed in RNALater. Samples were homogenized with a Dounce homogenizer in RLT buffer containing ß-mercaptoethanol (Qiagen). The homogenate was then processed using an RNAEasy kit (Qiagen, Hilden, Germany). Replicate samples for each stage were analyzed for RNA quantity and quality on a Nanodrop 8000 spectrophotometer. RNA libraries were prepared for sequencing using standard Illumina protocols

But, as you can see, there's nothing about whether its stranded or not: Illumina has both stranded and unstranded "standard" protocols.


---

