Team:SUSTC-Shenzhen-A/RFC
From 2012.igem.org
Line 13: | Line 13: | ||
==Informations are not useful in database== | ==Informations are not useful in database== | ||
<div> | <div> | ||
- | + | <p>We get a database that contains all the information about all the BioBricks. In this database, every BioBrick has 40 properties, they are:</p> | |
+ | <p>part_id (this is essential to locate a BioBrick in a database) part_name</p> | ||
</div> | </div> |
Revision as of 12:29, 22 September 2012
Contents |
Ways leading to a standardized bio-engineered-world
In 2003, the first attempt to make a synthetic biology a discipline that everyone can share about it was made. After the appearance of the first BioBrick(tm), the concept about standardization had been widely accepted. And it is a trend in synthetic biology now.
Thanks to the standardization, biologists have developed many useful tools with the help of the standardized parts, the BioBricks. These BioBricks really contribute a lot to the research field. And they make easier for researchers to communicate with each other under the same technical standards. Due to the convenience of BioBricks, thousands of BioBricks have been created and introduced during these years. Thus the database containing these BioBricks is getting larger and larger.
But here comes the problem. Since every one can share their BioBricks, sometimes the information of the BioBricks are incomplet when they submit. So it becomes hard for users to search for a BioBrick that they want. Although there is an RFC, RFC 52 already, but we are not satisfied. Because of the generl description of it, the database of the BioBricks is still a mess. So we want to create a new RFC to replace RFC 52.
We want to establish an RFC to describe the minimum information for a qualified BioBrick. We listed the minimum information a BioBrick should have, and gave a short description for each of them. Especially, we want to qualify the classification of BioBricks. All the BioBricks should be organized, so that users can search for it easily.
The current problem
Informations are not complete in partsregistry.org
Informations are not useful in database
We get a database that contains all the information about all the BioBricks. In this database, every BioBrick has 40 properties, they are:
part_id (this is essential to locate a BioBrick in a database) part_name