"
Team:Paris/Tool DataBase
From 2009.igem.org
iGEM > Paris > Tool > DataBase
Contents |
A. Databases Schema
At this point, we want to know how do we think our database. In fact we don't have only one database. We thought of separate the application database in several parts. In order to have an application which is as effective as we want, we discuss about the fact of being able to fit it for as many laboratory needs as we could. We had to keep in mind that laboratory aren't the same and some have already their own databases.
A.1 how many ?
B. Biological Databases
We thought 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 (laboratory 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
