| Literature DB >> 24564482 |
Matthew P Campbell, René Ranzinger, Thomas Lütteke, Julien Mariethoz, Catherine A Hayes, Jingyu Zhang, Yukie Akune, Kiyoko F Aoki-Kinoshita, David Damerell, Giorgio Carta, Will S York, Stuart M Haslam, Hisashi Narimatsu, Pauline M Rudd, Niclas G Karlsson, Nicolle H Packer, Frédérique Lisacek.
Abstract
BACKGROUND: Recent progress in method development for characterising the branched structures of complex carbohydrates has now enabled higher throughput technology. Automation of structure analysis then calls for software development since adding meaning to large data collections in reasonable time requires corresponding bioinformatics methods and tools. Current glycobioinformatics resources do cover information on the structure and function of glycans, their interaction with proteins or their enzymatic synthesis. However, this information is partial, scattered and often difficult to find to for non-glycobiologists.Entities:
Mesh:
Substances:
Year: 2014 PMID: 24564482 PMCID: PMC4016020 DOI: 10.1186/1471-2105-15-S1-S9
Source DB: PubMed Journal: BMC Bioinformatics ISSN: 1471-2105 Impact factor: 3.169
Encoding of IUPAC monosaccharide α-D-Neup5Ac in databases
| Database | Monosaccharide | Substituent |
|---|---|---|
| CarbBank | D-gro-a-D-3-deoxy-galNon2ulop5NAc-onic | |
| CarbBank | a-D-Neup5Ac | |
| GLYCOSCIENCES.de | D-gro-a-D-3-deoxy-galNon2ulop5NAc-onic | |
| GLYCOSCIENCES.de | a-D-Neup5Ac | |
| GlycomeDB | a-dgro-dgal-NON-2:6|1:a|2:keto|3:d | (5d-1) n-acetyl |
| UniCarbKB | a-dgro-dgal-NON-2:6|1:a|2:keto|3:d | (5d-1) n-acetyl |
| CFG | NNa | |
| BCSDB | aXNeup | (5-1) Ac |
| Protein Data Bank | SIA | |
| Protein Data Bank | NAN |
Overview of how the IUPAC monosaccharide α-D-Neup5Ac is encoded in different databases as provided by MonosaccharideDB http://www.monosaccharidedb.org. The names of the database (Database), the monosaccharide name (Monosaccharide) and when specified, the separately handled substituent (Substituent), are given in the respectively designated columns. Note that in some databases even different names can be used for the same monosaccharide.
Figure 1Encoding formats for glycans. Examples for the sequence encoding of the O-Glycan with the GlycomeDB ID 534/EUROCarbDB/UniCarbDB ID 598. (A) LINUCS sequence format as used in GLYCOSCIENCES.de. (B) BCSDB sequence encoding. (C) CarbBank sequence format. (D) GlycoCT sequence format as used in GlycomeDB and UniCarbDB. (E) KCF format used in the KEGG database. (F) LinearCode® as used in the CFG database.
Figure 2Graphical representation of glycans. Examples for graphical representations of glycan structures corresponding to the illustration of Figure 1. (A) CFG cartoon representation using colour symbols. (B) CFG cartoon representation using greyscale symbols. (C) Oxford cartoon representation. (D) IUPAC like representation using textual names. (E) Chemical representation preferred by carbohydrate chemists. A definition of the symbols and corresponding monosaccharide names is shown below (E).
Current on-line resources
| Resource name | Rough content | URL |
|---|---|---|
| KEGG-GLYCAN | Glycan structures, References to reactions and pathways, Glyco-gene information | |
| CFG | Glycan structures, MS profile, GlycanArray data, Glyco-gene expression data | |
| GlycomeDB | Glycan structures, Cross references | |
| GLYCOSCIENCES.de | Glycan structures, 3D structures, NMR data, Software tools | |
| MonosaccharideDB | Repertoire of monosaccharides | |
| UniCarb-DB | Glycan structures, LC/MS-MS, HPLC data | |
| GlycoSuiteDB | Literature based curated glycan structures | |
| UniCarbKB | Curated glycan structures | |
| GlycoBase | Glycan structures, HPLC profiles | |
| JCGGDB | Glycan structures, glyco-gene information, glycomics-related protocols, cross-references to other national life science resources | |
| BCSDB | Bacterial glycan structures, NMR data, | |
| RINGS | Software tools | |
| GlycO ontology | Curated glycan structures |
List of resources cited throughout the text, with corresponding rough content description and URLs.
Available format translation across databases
| Output → | IUPAC | KCF | LINUCS | Linear Code | GlydeII | GlycoCT |
|---|---|---|---|---|---|---|
| RINGS | GLYCOSCIENCES.de, | Glycan Builder | GlycomeDB, Glycan Builder | GlycomeDB, UniCarbKB*, Glycan | ||
| UniCarbKB* | RINGS, | RINGS | GlycomeDB, | GlycomeDB, RINGS | ||
| GLYCOSCIENCES.de | RINGS | Glycan Builder | GlycomeDB, Glycan Builder | GlycomeDB, Glycan | ||
| RINGS | GlycomeDB, GlycanBuilder | GlycomeDB, Glycan | GlycomeDB, Glycan | |||
| - | RINGS | GlycomeDB | - | GlycomeDB | ||
| UniCarbKB* | RINGS | GlycomeDB, | Glycan Builder | GlycomeDB, Glycan |
Summary of existing software for parsing and translating the most popular formats (partly illustrated in Figures 1 and 2) and the web resource (described in Table 2) where the tool can be run or downloaded. For instance, a LINUCS (Figure 2A) structure can be translated to KCF (Figure 2E) in the RINGS website. Input formats are listed in the rows, and the output formats in the columns. The asterisk indicates that the parsers/translators are available on request but not directly accessible yet as on other websites.
Figure 3Graphical interfaces for glycan drawing. Examples for the output of tools for graphical input corresponding to the illustration of Figure 2. In the fore, a screenshot of DrawRINGS and in the back, a screenshot of GlycanBuilder are shown.