Difference between revisions of "Databases"
m |
Ivan Yevshin (Talk | contribs) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 22: | Line 22: | ||
|[[Biopath]]|| || || ||style="background-color:PaleGreen"| + || | |[[Biopath]]|| || || ||style="background-color:PaleGreen"| + || | ||
|- | |- | ||
| − | |[[ | + | |[[Ensembl]]|| || ||style="background-color:PaleGreen"| + || || |
|- | |- | ||
|[[Geneways]]||style="background-color:PaleGreen"| + || || || || | |[[Geneways]]||style="background-color:PaleGreen"| + || || || || | ||
| Line 28: | Line 28: | ||
|[[Gene Ontology database|GO]]|| ||style="background-color:PaleGreen"| + || || || | |[[Gene Ontology database|GO]]|| ||style="background-color:PaleGreen"| + || || || | ||
|- | |- | ||
| − | |[ | + | |[[GTRD]]|| || + || || || + |
|- | |- | ||
|[http://humancyc.org/ HumanCyc]|| + || + || || || | |[http://humancyc.org/ HumanCyc]|| + || + || || || | ||
| Line 68: | Line 68: | ||
**[[File:PublicDB_icon.png]] Remote protected (commercial) database with read access (valid license). | **[[File:PublicDB_icon.png]] Remote protected (commercial) database with read access (valid license). | ||
| − | Databases are [[Repository pane|handled like any other]] data collection in the repository pane with the exception that databases cannot be removed. When a database is selected its description is displayed in the [[Information box| property inspector]] below. | + | Databases are [[Repository pane|handled like any other]] data collection in the repository pane with the exception that databases cannot be removed. When a database is selected its description is displayed in the [[Information box| property inspector]] below. |
| + | |||
| + | [[Information box#Search|Full text searches]] can be run through all the available databases. The search routine scans for exact matches, but use of wildcards is possible, too. | ||
==See also== | ==See also== | ||
| Line 74: | Line 76: | ||
*[[Repository pane]] | *[[Repository pane]] | ||
*[[Search tools]] | *[[Search tools]] | ||
| − | *[[ | + | *[[:Category:Databases|List of databases]] |
==External links== | ==External links== | ||
| − | * [http://www.ensembl.org/ | + | * [http://www.ensembl.org/ Ensembl official website] |
* [http://www.geneontology.org/ Gene Ontology official website] | * [http://www.geneontology.org/ Gene Ontology official website] | ||
* [http://www.ncbi.nlm.nih.gov/pubmed/15016385 Abstract on the Geneways database at NCBI website] | * [http://www.ncbi.nlm.nih.gov/pubmed/15016385 Abstract on the Geneways database at NCBI website] | ||
* [http://www.reactome.org/ReactomeGWT/entrypoint.html Reactome official website] | * [http://www.reactome.org/ReactomeGWT/entrypoint.html Reactome official website] | ||
Latest revision as of 11:13, 2 July 2013
| This page or section is a stub. Please add more information here! |
Close integration with biological databases containing experimental data is a distinctive feature of BioUML, which is essential for accurate and convenient modeling of biological systems. For the purpose of working with different kinds of data the database type concept has been introduced. The database type defines:
- data types (gene, protein, RNA, substance, reaction, etc.) that are stored in the database;
- mapping of the database content into diagram elements and diagram types that can be used with the database;
- diagram types that can be used to present the database content as a set of diagrams;
- the query engine to find interacting components of the system; search results can be shown as a graph and edited by the user.
According to their content (data type) biological databases can be divided into several groups as follows (one database can provide several types of data; the green colour indicates that the database is freely available in BioUML web edtion):
| Data type | |||||
| pathways | gene/protein classification | genome | pathways simulation | transcription factor | |
| Apoptosis model | + | ||||
| Biomodels | + | ||||
| Biopath | + | ||||
| Ensembl | + | ||||
| Geneways | + | ||||
| GO | + | ||||
| GTRD | + | + | |||
| HumanCyc | + | + | |||
| KEGG | + | ||||
| Proteome (Biobase) | + | ||||
| Reactome | + | + | |||
| Transfac (Biobase) | + | ||||
| TRANSPath (Biobase) | + | + | |||
| UCSC Genome Browser | + | ||||
| Virtual Human | + | ||||
Databases can be installed locally (for the BioUML workbench) or can be accessed via the Internet from the BioUML server, which supports secure access to databases. The server administrator can configure security settings for access to each database installed on the server. The information where a database is installed (locally or on the server side) as well as about its availability is displayed using different icons.
[edit] Interface
All the available databases are listed under the Databases tab in the repository pane. The icon color indicates location and accessibility of the database:
- blue color - the database is installed locally, accessible for reading and writing:
Local database;
- yellow - remote public database, accessibility for reading and writing is specified by R and W letters:
Public database with read access enabled,
Public database with read access, write access disabled,
Public database with read access, write access enabled,
Public database with read and write access;
- red color - remote protected database, the user must log-in to get access to the database, accessibility for reading and writing is specified by R and W letters:
Remote protected (commercial) read-only database (no access),
Remote protected (commercial) read-and-write database (no access);
- green color - remote protected database, the user successfully logged in, accessibility for reading and writing is specified by R and W letters:
Remote protected (commercial) database with read access (valid license).
Databases are handled like any other data collection in the repository pane with the exception that databases cannot be removed. When a database is selected its description is displayed in the property inspector below.
Full text searches can be run through all the available databases. The search routine scans for exact matches, but use of wildcards is possible, too.
