Data Integration Workflow |
|
Based on use cases collected from the user community, various glycan, protein and proteoform datasets are collected from major data repositories and data generators. These datasets pass through intensive quality control protocols, and data model is created to represent the relationship between data fields. The data model created relies on existing GlycoRDF and UniProt Core namespaces or ontologies created for glycan and protein data respectively. Finally, triples are generated based on the data model and loaded to a triple store which is accessible to GlyGen front and other sites through RESTful APIs. The cleaned datasets that were used to generate triples are also made available for browsing and downloads through the datasetview interface.
|
|
Collected Use Cases |
| | 257 use cases were collected from more than 100 researchers from several biomedical disciplines impacted by glycobiology. The use cases were further condensed to 114 distinct use cases and were grouped into six categories |
Major Data Resources |
| | GlyGen specific data is collected from several public resources such as UniProtKB, GlyTouCan, UniCarbKB, NCBI RefSeq, NCBI PubChem, Protein Resource Ontology, BioMuta, BioXpress for data integration into GlyGen |
Data Generators |
| | GlyGen specific data is also collected by collaborating with individual PIs, researchers, and labs generating data |
Data categorization, Integration, Quality control |
| | From the use cases and collected data, selected use cases, and data are categorized into three categories - Protein centric, Proteoform centric and Glycan centric data category. Once the data is categorized, it is integrated into GlyGen, based on the aims and goals of the project phase. The integrated data is verified and checked for quality manually and automatically with the help of scripts |
Datasets and Metadata and Data Model |
| | After the data is categorized, integrated and verified, datasets in CSV format are created from the data. The datasets in Protein and Proteoform category have UniProtKB canonical identifiers as the primary key whereas datasets in Glycan category have GlyTouCan identifiers as the primary key. Once the datasets are created, a detailed readme file is created based on the BioCompute Object specification that not only provides metadata information about the dataset but also enables reproducibility of the dataset. In Parallel, data model network is created after the data is categorized, integrated and verified which helps to understand how the data in different categories are linked together. The datasets and data model network are then displayed on the Dataset Collection Viewer interface |
Dataset viewer |
| | The dataset viewer interface allows to view the datasets, preview the data and also to download the data. It also allows reading the readme for the generated datasets. The dataset viewer interface also contains web pages for GlyGen APIs, FAQs, Data model and data integration workflow |
Triple Generation (work in progress) |
| | RDF N-Triples will be generated from the CSV datasets and stored in GlyGen triplestore |
Triplestore (work in progress) |
| | The GlyGen triplestore will use Virtuoso database to store all the N-Triples and can be accessed via RESTful GlyGen APIs and via public resources RESTful APIs |
APIs, GlyGen Frontend and Public resources |
| | The GlyGen frontend can access the GlyGen triplestore via the GlyGen RESTful APIs and displays the user requested GlyGen data. Similarly, other public resources can access the GlyGen Triplestore via RESTful APIs for GlyGen data and provide it to their users |