EVI-Genoret Database
From Wiki
| (3 intermediate revisions not shown.) | |||
| Line 1: | Line 1: | ||
The [[EVI-Genoret]] Database (see the [http://www-genoret.u-strasbg.fr/genoret web site]) | The [[EVI-Genoret]] Database (see the [http://www-genoret.u-strasbg.fr/genoret web site]) | ||
| - | For any question please contact | + | For any question please contact [mailto:Raymond.Ripp@igbmc.u-strasbg.fr Raymond Ripp] |
| - | The aim of the Genoret Database is to centralise phenotypic, genomic and proteomic data concerning retinal diseases as well as a minimal data-type set concerning patients. This should allow implementation of standards (Clinical Report Forms, Standardized Operation Procedures, Standardized Experimental Procedures) and permit the establishment of common information networking systems. | + | The aim of the Genoret Database is to centralise phenotypic, genomic and proteomic data concerning retinal diseases as well as a minimal data-type set concerning patients. This should allow implementation of standards (Clinical Report Forms, Standardized Operation Procedures ([[SOPs]]), Standardized Experimental Procedures) and permit the establishment of common information networking systems. |
| - | + | The Genoret Database is a Relational Database whose advantage is to store heterogeneous data in a standard format. It provides an easy manual or automatic access, allowing direct deposits focused on workpackages and workpackage deliverables. Furthermore the establishment of Automatic Update Programs respecting Quality Control Assessment will allow the integration of new techniques, data and protocols approved by the Consortium. | |
| - | + | The Genoret Database needs to be linked to other databases. For technical or security reasons most of the data has to remain at the owner's site and should only be accessed in a restricted manner. For this, specific programs will be developed and implemented in each centre. | |
The patient catalogue (level 1) will permit to highlight the existence of patient data-sets matching relevant criteria for ophthalmologists, geneticians or industrial companies. Further access (level 2) can be granted with the owner's agreement. | The patient catalogue (level 1) will permit to highlight the existence of patient data-sets matching relevant criteria for ophthalmologists, geneticians or industrial companies. Further access (level 2) can be granted with the owner's agreement. | ||
The database can be visited via a three level web interface : restricted, general and public. | The database can be visited via a three level web interface : restricted, general and public. | ||
| - | The restricted level can be accessed by any defined group of EVI-Genoret registered people. The owner decides who has access to his/her data. The general level is for all registered [ | + | The restricted level can be accessed by any defined group of EVI-Genoret registered people. The owner decides who has access to his/her data. The general level is for all registered [[EVI-Genoret member]]s (with [[login and password]]). The public level corresponds to free internet access. |
The relational database will be the link between all components and workpackages, from gene to disease, from animal models to clinical trials, etc. We hope that these data-sharing possibilities will incite members to deposit their data. | The relational database will be the link between all components and workpackages, from gene to disease, from animal models to clinical trials, etc. We hope that these data-sharing possibilities will incite members to deposit their data. | ||
| - | The relational database is mainly organized through a | + | The relational database is mainly organized through a [http://www.postgresql.org/ PostgreSQL] Database Management System. Web interfaces are developed using [http://www.php.net/ PHP], Html, Javascript and Java programming languages. Secure data exchange can be performed through the encrypted SSL protocol (Secure Socket Layer). Within the Application Server additional access modules will be developed to interrogate each specific local or foreign database. |
Current revision
The EVI-Genoret Database (see the web site)
For any question please contact Raymond Ripp
The aim of the Genoret Database is to centralise phenotypic, genomic and proteomic data concerning retinal diseases as well as a minimal data-type set concerning patients. This should allow implementation of standards (Clinical Report Forms, Standardized Operation Procedures (SOPs), Standardized Experimental Procedures) and permit the establishment of common information networking systems.
The Genoret Database is a Relational Database whose advantage is to store heterogeneous data in a standard format. It provides an easy manual or automatic access, allowing direct deposits focused on workpackages and workpackage deliverables. Furthermore the establishment of Automatic Update Programs respecting Quality Control Assessment will allow the integration of new techniques, data and protocols approved by the Consortium.
The Genoret Database needs to be linked to other databases. For technical or security reasons most of the data has to remain at the owner's site and should only be accessed in a restricted manner. For this, specific programs will be developed and implemented in each centre.
The patient catalogue (level 1) will permit to highlight the existence of patient data-sets matching relevant criteria for ophthalmologists, geneticians or industrial companies. Further access (level 2) can be granted with the owner's agreement.
The database can be visited via a three level web interface : restricted, general and public. The restricted level can be accessed by any defined group of EVI-Genoret registered people. The owner decides who has access to his/her data. The general level is for all registered EVI-Genoret members (with login and password). The public level corresponds to free internet access.
The relational database will be the link between all components and workpackages, from gene to disease, from animal models to clinical trials, etc. We hope that these data-sharing possibilities will incite members to deposit their data.
The relational database is mainly organized through a PostgreSQL Database Management System. Web interfaces are developed using PHP, Html, Javascript and Java programming languages. Secure data exchange can be performed through the encrypted SSL protocol (Secure Socket Layer). Within the Application Server additional access modules will be developed to interrogate each specific local or foreign database.
