43 | | It took longer than expected, but we were able to develop the glycan structure workflow with an additional step: retrieve similar |
44 | | glycan structures to the retrieved ones. GlycoEpitope will continue to develop other web services with which to build workflows. |
| 43 | It took longer than expected, but we were able to create a BioMoby web service in GlycoEpitope. |
| 44 | * GlycoEpitope |
| 45 | * getGlycoEpitopeIDfromKeyword |
| 46 | * getIUPACfromGlycoEpitopeID |
| 47 | * RINGS |
| 48 | * getKCFfromIUPAC |
| 49 | |
| 50 | Our workflow thus takes as input a keyword and searches GlycoEpitopeDB for entries matching the keyword. The retrieved entries are then used to get the glycan structures from each entry in IUPAC format. A new utility in RINGS was then developed to convert from IUPAC to KCF format. In an additional step, we retrieved similar glycan structures to the converted ones in KCF format. Both RINGS and GlycoEpitope will continue to develop other web services with which to build workflows. |