Difference between revisions of "BIN-Miscellaneous DB"
m |
m |
||
(6 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
− | <div id=" | + | <div id="ABC"> |
− | + | <div style="padding:5px; border:1px solid #000000; background-color:#b3dbce; font-size:300%; font-weight:400; color: #000000; width:100%;"> | |
Miscellaneous Databases for Bioinformatics | Miscellaneous Databases for Bioinformatics | ||
− | + | <div style="padding:5px; margin-top:20px; margin-bottom:10px; background-color:#b3dbce; font-size:30%; font-weight:200; color: #000000; "> | |
− | + | (SGD; STRING; ...) | |
− | + | </div> | |
− | |||
− | |||
− | |||
− | SGD; STRING; ... | ||
</div> | </div> | ||
− | {{ | + | {{Smallvspace}} |
− | + | <div style="padding:5px; border:1px solid #000000; background-color:#b3dbce33; font-size:85%;"> | |
− | + | <div style="font-size:118%;"> | |
− | + | <b>Abstract:</b><br /> | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | < | ||
− | <div | ||
− | |||
<section begin=abstract /> | <section begin=abstract /> | ||
− | |||
This unit collects short explorations of various databases. It is probably best not to work through the units all in one go, but to go through them in context of an actual use case, when you need information from one of them. Currently we have SGD and STRING. | This unit collects short explorations of various databases. It is probably best not to work through the units all in one go, but to go through them in context of an actual use case, when you need information from one of them. Currently we have SGD and STRING. | ||
<section end=abstract /> | <section end=abstract /> | ||
− | + | </div> | |
− | + | <!-- ============================ --> | |
− | + | <hr> | |
− | + | <table> | |
− | == | + | <tr> |
− | === | + | <td style="padding:10px;"> |
− | < | + | <b>Objectives:</b><br /> |
− | <!-- | + | This unit will ... |
− | + | * ... introduce various database offerings and explore their use. | |
+ | </td> | ||
+ | <td style="padding:10px;"> | ||
+ | <b>Outcomes:</b><br /> | ||
+ | After working through this unit you ... | ||
+ | * ... can navigate and use the databases that are discussed here. | ||
+ | </td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | <!-- ============================ --> | ||
+ | <hr> | ||
+ | <b>Deliverables:</b><br /> | ||
+ | <section begin=deliverables /> | ||
+ | <li><b>Time management</b>: Before you begin, estimate how long it will take you to complete this unit. Then, record in your course journal: the number of hours you estimated, the number of hours you worked on the unit, and the amount of time that passed between start and completion of this unit.</li> | ||
+ | <li><b>Journal</b>: Document your progress in your [[FND-Journal|Course Journal]]. Some tasks may ask you to include specific items in your journal. Don't overlook these.</li> | ||
+ | <li><b>Insights</b>: If you find something particularly noteworthy about this unit, make a note in your [[ABC-Insights|'''insights!''' page]].</li> | ||
+ | <section end=deliverables /> | ||
+ | <!-- ============================ --> | ||
+ | <hr> | ||
+ | <section begin=prerequisites /> | ||
+ | <b>Prerequisites:</b><br /> | ||
+ | This unit builds on material covered in the following prerequisite units:<br /> | ||
*[[BIN-Databases|BIN-Databases (Bioinformatics Databases)]] | *[[BIN-Databases|BIN-Databases (Bioinformatics Databases)]] | ||
+ | <section end=prerequisites /> | ||
+ | <!-- ============================ --> | ||
+ | </div> | ||
− | {{ | + | {{Smallvspace}} |
− | |||
− | |||
− | |||
− | |||
− | {{ | + | {{Smallvspace}} |
− | + | __TOC__ | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
{{Vspace}} | {{Vspace}} | ||
Line 75: | Line 65: | ||
=== Evaluation === | === Evaluation === | ||
− | |||
− | |||
<b>Evaluation: NA</b><br /> | <b>Evaluation: NA</b><br /> | ||
− | :This unit is not evaluated for course marks. | + | <div style="margin-left: 2rem;">This unit is not evaluated for course marks.</div> |
− | |||
− | |||
− | |||
− | |||
− | </div | ||
− | |||
== Contents == | == Contents == | ||
− | |||
==SGD - a Yeast Model Organism Database=== | ==SGD - a Yeast Model Organism Database=== | ||
<div class="colmask doublepage"> | <div class="colmask doublepage"> | ||
Line 95: | Line 76: | ||
{{task|1= | {{task|1= | ||
− | Access the [ | + | Access the [https://www.yeastgenome.org/locus/S000002214 information page on Mbp1] at the ''Saccharomyces'' Genome Database. |
<ol> | <ol> | ||
Line 117: | Line 98: | ||
</ol> | </ol> | ||
+ | |||
+ | }} | ||
You will notice that some of this information relates to the molecule itself, and some of it relates to its relationship with other molecules. Some of it is stored at SGD, and some of it is cross-referenced from other databases. And we have textual data, numeric data, and images. | You will notice that some of this information relates to the molecule itself, and some of it relates to its relationship with other molecules. Some of it is stored at SGD, and some of it is cross-referenced from other databases. And we have textual data, numeric data, and images. | ||
If we would be working on yeast, most data we need is right here: curated, kept current and consistent, referenced to the literature and ready to use. But if you are working on a different species - some "MYSPE"- you need to integrate data yourself, from data sources such as the NCBI, or UniProt. The upside is that most of the information like this '''is available''' for many, many species. The downside is that you have to integrate information from many different sources essentially "by hand". | If we would be working on yeast, most data we need is right here: curated, kept current and consistent, referenced to the literature and ready to use. But if you are working on a different species - some "MYSPE"- you need to integrate data yourself, from data sources such as the NCBI, or UniProt. The upside is that most of the information like this '''is available''' for many, many species. The downside is that you have to integrate information from many different sources essentially "by hand". | ||
− | |||
− | |||
<!-- Column 1 end --> | <!-- Column 1 end --> | ||
Line 129: | Line 110: | ||
<!-- Column 2 start --> | <!-- Column 2 start --> | ||
{{task|1= | {{task|1= | ||
− | |||
* Navigate to the '''Analyze''' → '''Gene Lists''' page. Paste the following identifiers. (This could be the result of some functional screen, or a set of differentially expressed genes, or other gene list returned from an assay or bioinformatics procedure...): | * Navigate to the '''Analyze''' → '''Gene Lists''' page. Paste the following identifiers. (This could be the result of some functional screen, or a set of differentially expressed genes, or other gene list returned from an assay or bioinformatics procedure...): | ||
Line 139: | Line 119: | ||
* What do these genes have in common? Can you identify a common theme of function? | * What do these genes have in common? Can you identify a common theme of function? | ||
* Navigate to the '''Analyze''' → '''GO Slim mapper''' page. Paste your gene list for "Step 1". Choose "Yeast GO-Slim: Function" as the ontology of terms to search in for these genes for "Step 2". Choose "SELECT ALL Terms..." for "Step 3". Consider the results. Most of the genes have unknown functions, there is no clear theme for those with a known function. | * Navigate to the '''Analyze''' → '''GO Slim mapper''' page. Paste your gene list for "Step 1". Choose "Yeast GO-Slim: Function" as the ontology of terms to search in for these genes for "Step 2". Choose "SELECT ALL Terms..." for "Step 3". Consider the results. Most of the genes have unknown functions, there is no clear theme for those with a known function. | ||
− | * Now repeat the procedure for "GO-Slim:Process". All genes are annotated to "cell morphogenesis" (which is not surprising, because that is how I selected them.). And there are | + | * Now repeat the procedure for "GO-Slim:Process". All genes are annotated to "cell morphogenesis" (which is not surprising, because that is how I selected them.). And there are interesting and informative overlaps with other functional categories. |
*Click on "Download results". What do you get? How would you read this data into R? | *Click on "Download results". What do you get? How would you read this data into R? | ||
Line 158: | Line 138: | ||
<!-- Column 1 start --> | <!-- Column 1 start --> | ||
− | The essence of our "new" view of molcular biology is the study of interactions: after characterizing | + | The essence of our "new" view of molcular biology is the study of interactions: after characterizing biomolecules individually, we are assembling networks of relationships through protein-protein and other interaction experiments. But visualizing the results is not trivial since we need to display genes as networks, define attributes of the nodes and edges and encode them in our visualization, develop quantitative measures that help us mine the data for information, and map the results back into the network to evaluate the influence of the network topology (gene "neigborhoods") on our findings. Databases strive to build integrated viewers for this kind of data. However there is much that still needs to be done. Have a look at this article that discusses the gap between what one would need to do, and what is offered: |
{{#pmid: 26077899}} | {{#pmid: 26077899}} | ||
Line 170: | Line 150: | ||
{{task|1= | {{task|1= | ||
+ | |||
+ | * Review: | ||
+ | {{#pmid: 30476243}} | ||
* Navigate to the [http://string-db.org/ '''STRING database'''] and search for ''saccharomyces cerevisiae'' Mbp1 interactors. | * Navigate to the [http://string-db.org/ '''STRING database'''] and search for ''saccharomyces cerevisiae'' Mbp1 interactors. | ||
Line 198: | Line 181: | ||
</div> | </div> | ||
</div> | </div> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
{{Vspace}} | {{Vspace}} | ||
Line 215: | Line 186: | ||
== Notes == | == Notes == | ||
− | |||
− | |||
<references /> | <references /> | ||
{{Vspace}} | {{Vspace}} | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
<div class="about"> | <div class="about"> | ||
Line 270: | Line 199: | ||
:2017-08-05 | :2017-08-05 | ||
<b>Modified:</b><br /> | <b>Modified:</b><br /> | ||
− | : | + | :2020-09-23 |
<b>Version:</b><br /> | <b>Version:</b><br /> | ||
− | :1. | + | :1.1 |
<b>Version history:</b><br /> | <b>Version history:</b><br /> | ||
+ | *1.1 2020 Updates | ||
*1.0 First live version | *1.0 First live version | ||
*0.1 First stub | *0.1 First stub | ||
</div> | </div> | ||
− | |||
− | |||
{{CC-BY}} | {{CC-BY}} | ||
+ | [[Category:ABC-units]] | ||
+ | {{UNIT}} | ||
+ | {{LIVE}} | ||
</div> | </div> | ||
<!-- [END] --> | <!-- [END] --> |
Latest revision as of 08:51, 24 September 2020
Miscellaneous Databases for Bioinformatics
(SGD; STRING; ...)
Abstract:
This unit collects short explorations of various databases. It is probably best not to work through the units all in one go, but to go through them in context of an actual use case, when you need information from one of them. Currently we have SGD and STRING.
Objectives:
|
Outcomes:
|
Deliverables:
Prerequisites:
This unit builds on material covered in the following prerequisite units:
Contents
Evaluation
Evaluation: NA
Contents
SGD - a Yeast Model Organism Database=
Yeast happens to have a very well maintained model organism database - a Web resource dedicated to Saccharomyces cerevisiae. Where such dedicated resources are available, they are very useful for the community. For the general case however, we need to work with one of the large, general data providers - the NCBI and the EBI. But in order to get a sense of the type of data that is available, let's explore the SGD database.
Task:
Access the information page on Mbp1 at the Saccharomyces Genome Database.
- Browse through the Summary page and note the available information: you should see:
- information about the gene and the protein;
- Information about it's roles in the cell curated at the Gene Ontology database;
- Information about knock-out phenotypes; (Amazing. Would you have imagined that this is a non-essential gene?)
- Information about protein-protein interactions;
- Regulation and expression;
- A curators' summary of our understanding of the protein. Mandatory reading.
- And key references.
- Access the Protein tab and note the much more detailed information.
- Domains and their classification;
- Sequence;
- Shared domains;
- and much more...
You will notice that some of this information relates to the molecule itself, and some of it relates to its relationship with other molecules. Some of it is stored at SGD, and some of it is cross-referenced from other databases. And we have textual data, numeric data, and images.
If we would be working on yeast, most data we need is right here: curated, kept current and consistent, referenced to the literature and ready to use. But if you are working on a different species - some "MYSPE"- you need to integrate data yourself, from data sources such as the NCBI, or UniProt. The upside is that most of the information like this is available for many, many species. The downside is that you have to integrate information from many different sources essentially "by hand".
Task:
- Navigate to the Analyze → Gene Lists page. Paste the following identifiers. (This could be the result of some functional screen, or a set of differentially expressed genes, or other gene list returned from an assay or bioinformatics procedure...):
YAR014C YBR040W YBR200W YCL027W YCR089W YDL223C YDR085C YDR141C YER125W YER133W YER149C YHR102W YHR135C YHR158C YIL129C YKL048C YKL189W YKR031C YLL021W YLR229C YLR313C YLR332W YMR232W YNL154C YNR032C-A YOL111C YOR326W YPL123C YPR194C
- What do these genes have in common? Can you identify a common theme of function?
- Navigate to the Analyze → GO Slim mapper page. Paste your gene list for "Step 1". Choose "Yeast GO-Slim: Function" as the ontology of terms to search in for these genes for "Step 2". Choose "SELECT ALL Terms..." for "Step 3". Consider the results. Most of the genes have unknown functions, there is no clear theme for those with a known function.
- Now repeat the procedure for "GO-Slim:Process". All genes are annotated to "cell morphogenesis" (which is not surprising, because that is how I selected them.). And there are interesting and informative overlaps with other functional categories.
- Click on "Download results". What do you get? How would you read this data into R?
STRING - functional interactions
The essence of our "new" view of molcular biology is the study of interactions: after characterizing biomolecules individually, we are assembling networks of relationships through protein-protein and other interaction experiments. But visualizing the results is not trivial since we need to display genes as networks, define attributes of the nodes and edges and encode them in our visualization, develop quantitative measures that help us mine the data for information, and map the results back into the network to evaluate the influence of the network topology (gene "neigborhoods") on our findings. Databases strive to build integrated viewers for this kind of data. However there is much that still needs to be done. Have a look at this article that discusses the gap between what one would need to do, and what is offered:
Jeanquartier et al. (2015) Integrated web visualizations for protein-protein interaction databases. BMC Bioinformatics 16:195. (pmid: 26077899) |
[ PubMed ] [ DOI ] BACKGROUND: Understanding living systems is crucial for curing diseases. To achieve this task we have to understand biological networks based on protein-protein interactions. Bioinformatics has come up with a great amount of databases and tools that support analysts in exploring protein-protein interactions on an integrated level for knowledge discovery. They provide predictions and correlations, indicate possibilities for future experimental research and fill the gaps to complete the picture of biochemical processes. There are numerous and huge databases of protein-protein interactions used to gain insights into answering some of the many questions of systems biology. Many computational resources integrate interaction data with additional information on molecular background. However, the vast number of diverse Bioinformatics resources poses an obstacle to the goal of understanding. We present a survey of databases that enable the visual analysis of protein networks. RESULTS: We selected M=10 out of N=53 resources supporting visualization, and we tested against the following set of criteria: interoperability, data integration, quantity of possible interactions, data visualization quality and data coverage. The study reveals differences in usability, visualization features and quality as well as the quantity of interactions. StringDB is the recommended first choice. CPDB presents a comprehensive dataset and IntAct lets the user change the network layout. A comprehensive comparison table is available via web. The supplementary table can be accessed on http://tinyurl.com/PPI-DB-Comparison-2015. CONCLUSIONS: Only some web resources featuring graph visualization can be successfully applied to interactive visual analysis of protein-protein interaction. Study results underline the necessity for further enhancements of visualization integration in biochemical analysis tools. Identified challenges are data comprehensiveness, confidence, interactive feature and visualization maturing. |
The online resource that comes out as the best is the one at the STRING database.
Task:
- Review:
Szklarczyk et al. (2019) STRING v11: protein-protein association networks with increased coverage, supporting functional discovery in genome-wide experimental datasets. Nucleic Acids Res 47:D607-D613. (pmid: 30476243) |
[ PubMed ] [ DOI ] Proteins and their functional interactions form the backbone of the cellular machinery. Their connectivity network needs to be considered for the full understanding of biological phenomena, but the available information on protein-protein associations is incomplete and exhibits varying levels of annotation granularity and reliability. The STRING database aims to collect, score and integrate all publicly available sources of protein-protein interaction information, and to complement these with computational predictions. Its goal is to achieve a comprehensive and objective global network, including direct (physical) as well as indirect (functional) interactions. The latest version of STRING (11.0) more than doubles the number of organisms it covers, to 5090. The most important new feature is an option to upload entire, genome-wide datasets as input, allowing users to visualize subsets as interaction networks and to perform gene-set enrichment analysis on the entire input. For the enrichment analysis, STRING implements well-known classification systems such as Gene Ontology and KEGG, but also offers additional, new classification systems based on high-throughput text-mining as well as on a hierarchical clustering of the association network itself. The STRING resource is available online at https://string-db.org/. |
- Navigate to the STRING database and search for saccharomyces cerevisiae Mbp1 interactors.
- Visualize the network. Add a few proteins by clicking the (+) button two or three times.
- Click on a node to get a synopsis of its function.
- Explore the "confidence", "evidence" and "actions" networks for the retrieved interactors.
- Not all interacting proteins are also predicted to have a functional relationship with Mbp1. Do you agree?
- Explore the clustering and layout options. Do you understand what they do?
- Explore the Views on
- Neighborhood (gene-neighborhood is basically only relevant for prokaryotic operons though)
- Fusion (gene-fusion can identify proteins that stably interact in the cell)
- Occurence
- Coexpression
- Experiments
- Database, and
- Textmining
Each of these are methods for predicting functional relationships. Figure out how each one contributes to evidence of a functional interaction between Mbp1 and its predicted functional partners. I find the Occurrence view a unique and intriguing tool: visualizing in which organisms groups of genes are either all absent or all present allows to quickly establish functional clusters.
- Explore the "Download" options. Some of this data will be used in other learning units.
In summary, STRING is a convincingly well built tool to explore functional relationships between proteins.
Notes
About ...
Author:
- Boris Steipe <boris.steipe@utoronto.ca>
Created:
- 2017-08-05
Modified:
- 2020-09-23
Version:
- 1.1
Version history:
- 1.1 2020 Updates
- 1.0 First live version
- 0.1 First stub
This copyrighted material is licensed under a Creative Commons Attribution 4.0 International License. Follow the link to learn more.