"
Team:Paris/Tool DataBase
From 2009.igem.org
(Difference between revisions)
Christophe.R (Talk | contribs) (→DataBase overview) |
Christophe.R (Talk | contribs) (→DataBase overview) |
||
| Line 3: | Line 3: | ||
{{Template:Paris2009_menu6}} | {{Template:Paris2009_menu6}} | ||
| - | ==''' | + | ===A. DataBases Schema=== |
| + | |||
| + | '''flf:Put here some screenshots of the schema''' | ||
| + | |||
| + | ===B. Biological DataBase overview=== | ||
At this point, we want to know how do we think our database. In fact we don't have only one database. We think of integrating a modifiable software which can fit easily with databases. At a biological point of view, we've got to deal with the fact that we have to represent every DNA, those we have, those we had, and those we'll have. We also need a Database who can be use as a lab notebook, and a Protocols reference system. For the Biological part, we discuss about the principle to separate the theoretical DNA with the physical one: | At this point, we want to know how do we think our database. In fact we don't have only one database. We think of integrating a modifiable software which can fit easily with databases. At a biological point of view, we've got to deal with the fact that we have to represent every DNA, those we have, those we had, and those we'll have. We also need a Database who can be use as a lab notebook, and a Protocols reference system. For the Biological part, we discuss about the principle to separate the theoretical DNA with the physical one: | ||
| - | * theoretical DNA (''in silico'' DNA : <sub> | + | * theoretical DNA (''in silico'' DNA : <sub>is</sub>DNA) represent every DNA in any form (circular, linear, double, single, length etc...). With this methodology, we don't need to discuss about the presence of it in the lab. We can also name a <sub>is</sub>DNA witch is compose of other <sub>is</sub>DNA, and then, form entity like plasmid or even more full genome. |
| - | * physical DNA ( | + | * physical DNA (<sub>lab</sub>DNA) represent the working present DNA in the lab. It refers to the <sub>is</sub>DNA with some physical informations, like : quantities, freezer places and owners. |
this biological core database is enveloped by owner database which support the LabBook and Protocol databases. | this biological core database is enveloped by owner database which support the LabBook and Protocol databases. | ||
| - | |||
| - | |||
====References==== | ====References==== | ||
| - | + | X | |
| - | + | ||
Revision as of 15:44, 4 September 2009
iGEM > Paris > Tool > DataBase
A. DataBases Schema
flf:Put here some screenshots of the schema
B. Biological DataBase overview
At this point, we want to know how do we think our database. In fact we don't have only one database. We think of integrating a modifiable software which can fit easily with databases. At a biological point of view, we've got to deal with the fact that we have to represent every DNA, those we have, those we had, and those we'll have. We also need a Database who can be use as a lab notebook, and a Protocols reference system. For the Biological part, we discuss about the principle to separate the theoretical DNA with the physical one:
- theoretical DNA (in silico DNA : isDNA) represent every DNA in any form (circular, linear, double, single, length etc...). With this methodology, we don't need to discuss about the presence of it in the lab. We can also name a isDNA witch is compose of other isDNA, and then, form entity like plasmid or even more full genome.
- physical DNA (labDNA) represent the working present DNA in the lab. It refers to the isDNA with some physical informations, like : quantities, freezer places and owners.
this biological core database is enveloped by owner database which support the LabBook and Protocol databases.
References
X
