Skip to content

Create an account and get up to 25% off.

Order

Pathway Human Homo sapiens

O-linked glycosylation of mucins

R-HSA-913709 in Reactome release 97: under O-linked glycosylation, with 65 genes placed in it by the mapping files and 1 child pathway in the hierarchy.

The same number in the other species

Reactome writes the mouse and rat events it infers from a human pathway under the human number with the species token. A door opens only where that species' own list in this release holds the id: R-MMU-913709 (mouse), R-RNO-913709 (rat). Whether the event was inferred from this one is what the record says.

01The record

Reactome's own record of this pathway

What this tells you

The pathway list, the hierarchy and the genes on this page are read from the files Reactome publishes for Reactome release 97, built into this site on 2026-09-09: the pathway list, the hierarchy relationship file and the two gene mapping files. The record card is the one live read, Reactome's own record of this pathway.

Reactome's download page describes the mapping files: Mapping files link the source database identifier to the lowest level pathway diagram or subset of the pathway, all levels of the pathway hierarchy or database identifier to all reactions. [R13] The gene list here is the all-levels mapping of NCBI Gene ids, filled from the all-levels mapping of Ensembl ids where the NCBI file has no row for a gene; each row names which file it came from by the shape of its source id. Each row carries the evidence codes the file writes for it, as written and unranked, and both where the file writes both; no page of Reactome's documentation the survey read defines the codes, so this page does not expand them. A gene id the identity files do not name is kept as the source's own id with no door rather than turned into a symbol.

On citing what a search finds, Reactome says: It should be remembered that while we strive to contain the most current and accurate data, Reactome should not be used in citations where other primary sources of information are available. [R12] The record card prints the literature Reactome attaches to a curated pathway for that reason. The data are public domain: All data in the Reactome database and files derived from that data are licensed under the Creative Commons Public Domain Dedication (CC0). User may copy, modify, and distribute these data, even for commercial purposes, without asking for permission. Attribution is encouraged but not required. [R10] The pathway illustrations are licensed apart, under CC BY 4.0, and none is shown here.

A gene on this list is one Reactome places in this pathway in this release, and that is all the row says: it does not say the gene is expressed in a tissue or associated with a disease, which are the other two explorers' questions, read from other sources. Reactome's papers of record are [R01] [R02].

  1. [R01] Ragueneau E, Gong C, Sinquin P, Sevilla C, Beavers D, Grentner A, et al. (2026). The Reactome Knowledgebase 2026. Nucleic Acids Research 54:D673-D681. PMID 41251150, doi 10.1093/nar/gkaf1223.
  2. [R02] Milacic M, Beavers D, Conley P, Gong C, Gillespie M, Griss J, et al. (2024). The Reactome Pathway Knowledgebase 2024. Nucleic Acids Research 52:D672-D678. PMID 37941124, doi 10.1093/nar/gkad1025.
  3. [R10] Reactome, reactome.org. License Agreement. https://reactome.org/license, read 2026-09-09.
  4. [R12] Reactome, reactome.org. Citing us. https://reactome.org/cite, read 2026-09-09.
  5. [R13] Reactome, reactome.org. Download. https://reactome.org/download-data, read 2026-09-09.
Reading this pathway's record from Reactome (the pathway record).Still reading. A first read of a pathway can take a while; this page waits up to 35 seconds for it, and its scripts then bring in the panel, or a line saying what did not arrive.

02The genes

Genes Reactome places in this human pathway

The mapping files place 65 genes in this human pathway; showing 1 to 65, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this human pathway, page 1 of 1
GeneA4GNTAuthorityHGNC:17968Mapping file id51146 NCBI fileEvidenceTAS
GeneB3GNT2AuthorityHGNC:15629Mapping file id10678 NCBI fileEvidenceTAS
GeneB3GNT3AuthorityHGNC:13528Mapping file id10331 NCBI fileEvidenceTAS
GeneB3GNT4AuthorityHGNC:15683Mapping file id79369 NCBI fileEvidenceTAS
GeneB3GNT5AuthorityHGNC:15684Mapping file id84002 NCBI fileEvidenceTAS
GeneB3GNT6AuthorityHGNC:24141Mapping file id192134 NCBI fileEvidenceTAS
GeneB3GNT7AuthorityHGNC:18811Mapping file id93010 NCBI fileEvidenceTAS
GeneB3GNT8AuthorityHGNC:24139Mapping file id374907 NCBI fileEvidenceTAS
GeneB3GNT9AuthorityHGNC:28714Mapping file id84752 NCBI fileEvidenceTAS
GeneB4GALT5AuthorityHGNC:928Mapping file id9334 NCBI fileEvidenceTAS
GeneB4GALT6AuthorityHGNC:929Mapping file id9331 NCBI fileEvidenceTAS
GeneC1GALT1AuthorityHGNC:24337Mapping file id56913 NCBI fileEvidenceTAS
GeneC1GALT1C1AuthorityHGNC:24338Mapping file id29071 NCBI fileEvidenceTAS
GeneCHST4AuthorityHGNC:1972Mapping file id10164 NCBI fileEvidenceTAS
GeneGALNT1AuthorityHGNC:4123Mapping file id2589 NCBI fileEvidenceTAS
GeneGALNT10AuthorityHGNC:19873Mapping file id55568 NCBI fileEvidenceTAS
GeneGALNT11AuthorityHGNC:19875Mapping file id63917 NCBI fileEvidenceTAS
GeneGALNT12AuthorityHGNC:19877Mapping file id79695 NCBI fileEvidenceTAS
GeneGALNT13AuthorityHGNC:23242Mapping file id114805 NCBI fileEvidenceTAS
GeneGALNT14AuthorityHGNC:22946Mapping file id79623 NCBI fileEvidenceTAS
GeneGALNT15AuthorityHGNC:21531Mapping file id117248 NCBI fileEvidenceTAS
GeneGALNT16AuthorityHGNC:23233Mapping file id57452 NCBI fileEvidenceTAS
GeneGALNT17AuthorityHGNC:16347Mapping file id64409 NCBI fileEvidenceTAS
GeneGALNT18AuthorityHGNC:30488Mapping file id374378 NCBI fileEvidenceTAS
GeneGALNT2AuthorityHGNC:4124Mapping file id2590 NCBI fileEvidenceTAS
GeneGALNT3AuthorityHGNC:4125Mapping file id2591 NCBI fileEvidenceTAS
GeneGALNT4AuthorityHGNC:4126Mapping file id8693 NCBI fileEvidenceTAS
GeneGALNT5AuthorityHGNC:4127Mapping file id11227 NCBI fileEvidenceTAS
GeneGALNT6AuthorityHGNC:4128Mapping file id11226 NCBI fileEvidenceTAS
GeneGALNT7AuthorityHGNC:4129Mapping file id51809 NCBI fileEvidenceTAS
GeneGALNT8AuthorityHGNC:4130Mapping file id26290 NCBI fileEvidenceTAS
GeneGALNT9AuthorityHGNC:4131Mapping file id50614 NCBI fileEvidenceTAS
GeneGALNTL5AuthorityHGNC:21725Mapping file id168391 NCBI fileEvidenceTAS
GeneGALNTL6AuthorityHGNC:33844Mapping file id442117 NCBI fileEvidenceTAS
GeneGCNT1AuthorityHGNC:4203Mapping file id2650 NCBI fileEvidenceTAS
GeneGCNT3AuthorityHGNC:4205Mapping file id9245 NCBI fileEvidenceTAS
GeneGCNT4AuthorityHGNC:17973Mapping file id51301 NCBI fileEvidenceTAS
GeneGCNT7AuthorityHGNC:16099Mapping file id140687 NCBI fileEvidenceTAS
GeneMUC1AuthorityHGNC:7508Mapping file id4582 NCBI fileEvidenceTAS
GeneMUC12AuthorityHGNC:7510Mapping file id10071 NCBI fileEvidenceTAS
GeneMUC13AuthorityHGNC:7511Mapping file id56667 NCBI fileEvidenceTAS
GeneMUC15AuthorityHGNC:14956Mapping file id143662 NCBI fileEvidenceTAS
GeneMUC16AuthorityHGNC:15582Mapping file id94025 NCBI fileEvidenceTAS
GeneMUC17AuthorityHGNC:16800Mapping file id140453 NCBI fileEvidenceTAS
GeneMUC19AuthorityHGNC:14362Mapping file id283463 NCBI fileEvidenceTAS
GeneMUC2AuthorityHGNC:7512Mapping file id4583 NCBI fileEvidenceTAS
GeneMUC20AuthorityHGNC:23282Mapping file id200958 NCBI fileEvidenceTAS
GeneMUC21AuthorityHGNC:21661Mapping file id394263 NCBI fileEvidenceTAS
GeneMUC3AAuthorityHGNC:7513Mapping file id4584 NCBI fileEvidenceTAS
GeneMUC4AuthorityHGNC:7514Mapping file id4585 NCBI fileEvidenceTAS
GeneMUC5ACAuthorityHGNC:7515Mapping file id4586 NCBI fileEvidenceTAS
GeneMUC5BAuthorityHGNC:7516Mapping file id727897 NCBI fileEvidenceTAS
GeneMUC6AuthorityHGNC:7517Mapping file id4588 NCBI fileEvidenceTAS
GeneMUC7AuthorityHGNC:7518Mapping file id4589 NCBI fileEvidenceTAS
GeneMUCL1AuthorityHGNC:30588Mapping file id118430 NCBI fileEvidenceTAS
GenePOC1B-GALNT4AuthorityHGNC:42957Mapping file id100528030 NCBI fileEvidenceTAS
GeneQTGALAuthorityHGNC:21727Mapping file id146712 NCBI fileEvidenceTAS
GeneST3GAL1AuthorityHGNC:10862Mapping file id6482 NCBI fileEvidenceTAS
GeneST3GAL2AuthorityHGNC:10863Mapping file id6483 NCBI fileEvidenceTAS
GeneST3GAL3AuthorityHGNC:10866Mapping file id6487 NCBI fileEvidenceTAS
GeneST3GAL4AuthorityHGNC:10864Mapping file id6484 NCBI fileEvidenceTAS
GeneST6GAL1AuthorityHGNC:10860Mapping file id6480 NCBI fileEvidenceTAS
GeneST6GALNAC2AuthorityHGNC:10867Mapping file id10610 NCBI fileEvidenceTAS
GeneST6GALNAC3AuthorityHGNC:19343Mapping file id256435 NCBI fileEvidenceTAS
GeneST6GALNAC4AuthorityHGNC:17846Mapping file id27090 NCBI fileEvidenceTAS

Evidence codes on this page: TAS, as the mapping file writes them; a row carrying two was written twice by the file, once under each. The mapping file id says which file placed the gene: an NCBI Gene id from NCBI2Reactome_All_Levels.txt, an Ensembl gene id from Ensembl2Reactome_All_Levels.txt. The two files can disagree about a code, so a row's codes are the one file's view. Measured by this site's build over this release on 2026-09-09: of the 138,908 human pathway-gene pairs both files place, 207 (0.149 per cent, over 47 genes) carry TAS in the Ensembl file where the NCBI rows carry IEA alone.

  • Reactome mapping files, the human rows for this pathway · Reactome release 97 · read · Reactome downloads"NCBI2Reactome_All_Levels.txt" and "Ensembl2Reactome_All_Levels.txt", Reactome, release 97, https://reactome.org/download-data/ (date of access 2026-09-09). Data CC0; attribution encouraged.

03The hierarchy

Parents and children in this release's hierarchy

Reactome's hierarchy is a graph rather than a tree: a pathway can sit under more than one parent, and the gene counts are each pathway's own placements at every level under it, so a parent's count is not the sum of its children's.

  • Reactome, the human pathway list and hierarchy relationship file · Reactome release 97 · read · Reactome downloads"ReactomePathways.txt" and "ReactomePathwaysRelation.txt", Reactome, release 97, https://reactome.org/download-data/ (date of access 2026-09-09). Data CC0; attribution encouraged.