get_taxon_datasets: Retrieve the datasets for a given taxon

In jsicherman/Gemma-API: A wrapper for Gemma's Restful API to access curated gene expression data and differential expression analyses

Retrieve the datasets for a given taxon

Description

This function is deprecated in favor of get_datasets

Usage

get_taxon_datasets(
  taxon,
  offset = 0L,
  limit = 20,
  sort = "+id",
  raw = getOption("gemma.raw", FALSE),
  memoised = getOption("gemma.memoised", FALSE),
  file = getOption("gemma.file", NA_character_),
  overwrite = getOption("gemma.overwrite", FALSE),
  ...
)

Arguments

taxon	can either be Taxon ID, Taxon NCBI ID, or one of its string identifiers: scientific name, common name. It is recommended to use Taxon ID for efficiency. Please note, that not all taxa have all the possible identifiers available. Use the get_taxa_by_ids function to retrieve the necessary information. For convenience, below is a list of officially supported taxa: ID Comm.name Scient.name NcbiID 1 human Homo sapiens 9606 2 mouse Mus musculus 10090 3 rat Rattus norvegicus 10116 11 yeast Saccharomyces cerevisiae 4932 12 zebrafish Danio rerio 7955 13 fly Drosophila melanogaster 7227 14 worm Caenorhabditis elegans 6239
offset	The offset of the first retrieved result.
limit	Optional, defaults to 20. Limits the result to specified amount of objects. Has a maximum value of 100. Use together with offset and the totalElements attribute in the output to compile all data if needed.
sort	Order results by the given property and direction. The '+' sign indicate ascending order whereas the '-' indicate descending.
raw	TRUE to receive results as-is from Gemma, or FALSE to enable parsing. Raw results usually contain additional fields and flags that are omitted in the parsed results.
memoised	Whether or not to save to cache for future calls with the same inputs and use the result saved in cache if a result is already saved. Doing options(gemma.memoised = TRUE) will ensure that the cache is always used. Use forget_gemma_memoised to clear the cache.
file	The name of a file to save the results to, or NULL to not write results to a file. If raw == TRUE, the output will be a JSON file. Otherwise, it will be a RDS file.
overwrite	Whether or not to overwrite if a file exists at the specified filename.
...	Kept for compatibility. Ignored

Value

A data table with information about the queried dataset(s). A list if raw = TRUE. Returns an empty list if no datasets matched.

The fields of the output data.table are:

• experiment.shortName: Shortname given to the dataset within Gemma. Often corresponds to accession ID

• experiment.name: Full title of the dataset

• experiment.ID: Internal ID of the dataset.

• experiment.description: Description of the dataset

• experiment.troubled: Did an automatic process within gemma or a curator mark the dataset as "troubled"

• experiment.accession: Accession ID of the dataset in the external database it was taken from

• experiment.database: The name of the database where the dataset was taken from

• experiment.URI: URI of the original database

• experiment.sampleCount: Number of samples in the dataset

• experiment.batchEffectText: A text field describing whether the dataset has batch effects

• experiment.batchCorrected: Whether batch correction has been performed on the dataset.

• experiment.batchConfound: 0 if batch info isn't available, -1 if batch counfoud is detected, 1 if batch information is available and no batch confound found

• experiment.batchEffect: -1 if batch p value < 0.0001, 1 if batch p value > 0.1, 0 if otherwise and when there is no batch information is available or when the data is confounded with batches.

• experiment.rawData: -1 if no raw data available, 1 if raw data was available. When available, Gemma reprocesses raw data to get expression values and batches

• geeq.qScore: Data quality score given to the dataset by Gemma.

• geeq.sScore: Suitability score given to the dataset by Gemma. Refers to factors like batches, platforms and other aspects of experimental design

• taxon.name: Name of the species

• taxon.scientific: Scientific name for the taxon

• taxon.ID: Internal identifier given to the species by Gemma

• taxon.NCBI: NCBI ID of the taxon

• taxon.database.name: Underlying database used in Gemma for the taxon

• taxon.database.ID: ID of the underyling database used in Gemma for the taxon

Examples

get_taxon_datasets("human")

jsicherman/Gemma-API documentation built on April 27, 2024, 2:57 a.m.