Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
114 changes: 114 additions & 0 deletions content/blog/2026-gget-joins-scverse.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,114 @@
+++
title = "gget joins the scverse ecosystem"
date = 2026-06-30T00:00:05+01:00
description = "scverse adds programmatic access to genomic reference databases through gget."
author = "Muskan Hashim, Laura Luebbert, Lukas Heumos"
draft = false
+++

Querying genomic reference databases is something every bioinformatician does constantly, and doing it well has historically required juggling a patchwork of APIs, file formats, and web interfaces.
[gget](https://github.com/scverse/gget) was built to fix that, and is now officially part of the scverse ecosystem.

<img src="/img/blog/gget_x_scverse_overview.png" style="max-width: 100%;" alt="gget x scverse Overview." />

## What is gget?

gget is a Python package and command-line tool for programmatic access to biological databases.
It was published in [*Bioinformatics* in 2023](https://academic.oup.com/bioinformatics/article/39/1/btac836/6971843) from the Pachter Lab at Caltech, and provides a unified interface to more than 20 reference databases such as Ensembl, UniProt, NCBI, UCSC, AlphaFold, and more through a consistent API.

### gget enables biological interpretation within scverse workflows

Analyses built on scverse tools can be the starting point for biological interpretation.
For example, after clustering with [Scanpy](https://scanpy.readthedocs.io/) and identifying marker genes, you might want to understand what those genes do, how they are expressed across tissues, whether they are associated with disease, and how their protein products are structured.
Without tooling answering these questions means leaving Python and visiting several web portals.

gget closes that loop and is designed for exactly the questions arising at the end of a scverse analysis.
It returns results in formats that fit back into the analysis environment.

```py
import scanpy as sc
import gget

# Load and process single-cell data
adata = sc.read_h5ad("my_data.h5ad")

sc.pp.normalize_total(adata)
sc.pp.log1p(adata)
sc.tl.rank_genes_groups(adata, groupby="cell_type")

# Pull the top marker genes for a cluster
markers = sc.get.rank_genes_groups_df(adata, group="T cells")["names"].tolist()[:20]

# gget.info() requires Ensembl IDs
# Use gget.search() to resolve symbols to IDs first
Comment thread
muskanhashim marked this conversation as resolved.
search_results = gget.search(markers, "homo_sapiens")
ensembl_ids = search_results["ensembl_id"].tolist()
gget.info(ensembl_ids)

# Run enrichment
gget.enrichr(markers, database="GO_Biological_Process_2023")

# Fetch expression across human tissues from ARCHS4
gget.archs4(markers[0], which="tissue")
```

The `gget.cellxgene` module returns data as [AnnData](https://anndata.readthedocs.io/) objects helping slot results directly into scverse pipelines:

```py
# gget.cellxgene needs a one-time setup to install the cellxgene-census backend
gget.setup("cellxgene")

# Query CellxGene for pancreatic data and get back an AnnData object
adata = gget.cellxgene(
tissue="pancreas",
cell_type="pancreatic ductal cell",
gene=["INS", "GCG", "SST"],
census_version="stable"
)

# Inspect the returned AnnData object
adata
```

Output (stable → 2025-11-08 release):

```text
AnnData object with n_obs × n_vars = 29010 × 3
obs: 'dataset_id', 'assay', 'suspension_type', 'sex', 'tissue_general', 'tissue', 'cell_type', 'disease', 'is_primary_data'
var: 'soma_joinid', 'feature_id', 'feature_name', 'feature_type', 'feature_length', 'nnz', 'n_measured_obs'
```

## Alignment with the scverse mission

scverse is a modular, open, and interoperable foundation for biology.
Individual packages focus on what they do best, use shared data structures, and compose naturally with one another.
The addition of gget to our ecosystem complements our existing tooling by interoperating with the most widely used metadata & dataset databases.

Someone studying spatial transcriptomics with [Squidpy](https://squidpy.readthedocs.io/en/stable/) may want to fetch ligand-receptor protein structures from PDB, or pull disease associations from Open Targets, or BLAST a sequence of interest.
The integration of gget makes each of those a one-liner by being the layer helping you handle external reference databases alongside those analyses.


## What joining the scverse ecosystem means

For gget, joining scverse means adopting shared community infrastructure: the [scverse package template](https://github.com/scverse/cookiecutter-scverse), continuous integration conventions, as well as the documentation and testing practices the ecosystem shares.
It also means participating in the same community spaces where the broader ecosystem is discussed and developed.

For users, it means gget is where you would expect to find it: listed as one of our ecosystem packages at [scverse.org/packages](https://scverse.org/packages), discussed in the [scverse Zulip](https://scverse.zulipchat.com/) and [Discourse](https://discourse.scverse.org/), and maintained with the same expectations of quality and openness that apply across the ecosystem.

## Get started

gget is available on PyPI:

```shell
pip install gget
```

The [documentation](https://scverse.org/gget/) covers all modules with worked examples.
The [GitHub repository](https://github.com/scverse/gget) is the best place to report issues, propose new database integrations, or contribute.

If you are new to the scverse ecosystem, [scverse.org/join](scverse.org/join) is the place to start.
We’re excited to see what the community builds together.

<br>

*— the scverse team.*
Binary file added static/img/blog/gget_x_scverse_overview.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading