Team:SJTU-Software/Database

From 2014.igem.org

(Difference between revisions)
 
(9 intermediate revisions not shown)
Line 342: Line 342:
             <ul id="nav">
             <ul id="nav">
-
                 <li><a href="https://2014.igem.org/Team:SJTU-Software">Home</a></li>
+
                 <li><a href="https://2014.igem.org/Team:SJTU-Software"><font face="Jokerman">Home</font></a></li>
-
                 <li><a class="hsubs" href="https://2014.igem.org/Team:SJTU-Software/Overview">Software</a>
+
                 <li><a class="hsubs" href="https://2014.igem.org/Team:SJTU-Software/Overview"><font face="Jokerman">Software</font></a>
                     <ul class="subs">
                     <ul class="subs">
-
                         <li><a href="https://2014.igem.org/Team:SJTU-Software/Overview">Overview</a></li>
+
                         <li><a href="https://2014.igem.org/Team:SJTU-Software/Overview"><font face="Jokerman">Overview</font></a></li>
-
                         <li><a href="https://2014.igem.org/Team:SJTU-Software/Project/Tutorial">Tutorial</a></li>
+
                         <li><a href="https://2014.igem.org/Team:SJTU-Software/Project/Tutorial"><font face="Jokerman">Tutorial</font></a></li>
-
                         <li><a href="https://2014.igem.org/Team:SJTU-Software/Project/UserStudy">User Study</a></li>
+
                         <li><a href="https://2014.igem.org/Team:SJTU-Software/Project/UserStudy"><font face="Jokerman">User Study</font></a></li>
-
                         <li><a href="https://2014.igem.org/Team:SJTU-Software/Project/Demo">Demo</a></li>
+
                         <li><a href="https://2014.igem.org/Team:SJTU-Software/Project/Demo"><font face="Jokerman">Demo</font></a></li>
-
                         <li><a href="https://2014.igem.org/Team:SJTU-Software/Project/Download">Download</a></li>
+
                         <li><a href="https://2014.igem.org/Team:SJTU-Software/Project/Download"><font face="Jokerman">Download</font></a></li>
                     </ul>
                     </ul>
                 </li>
                 </li>
-
                 <li><a class="hsubs" href="https://2014.igem.org/Team:SJTU-Software/Database">Document</a>
+
                 <li><a class="hsubs" href="https://2014.igem.org/Team:SJTU-Software/Database"><font face="Jokerman">Document</font></a>
                     <ul class="subs">
                     <ul class="subs">
-
                         <li><a href="https://2014.igem.org/Team:SJTU-Software/Database">Database</a></li>
+
                         <li><a href="https://2014.igem.org/Team:SJTU-Software/Database"><font face="Jokerman">Database</font></a></li>
-
                         <li><a href="https://2014.igem.org/Team:SJTU-Software/Database/AssessmentModel">Assessment Model</a></li>
+
                         <li><a href="https://2014.igem.org/Team:SJTU-Software/Database/AssessmentModel"><font face="Jokerman">Assessment Model</font></a></li>
-
                         <li><a href="https://2014.igem.org/Team:SJTU-Software/Database/Conponent">Conponents</a></li>
+
                         <li><a href="https://2014.igem.org/Team:SJTU-Software/Database/Conponent"><font face="Jokerman">Conponents</font></a></li>
-
                         <li><a href="https://2014.igem.org/Team:SJTU-Software/Database/FutureDevelopment">For Future</a></li>
+
                         <li><a href="https://2014.igem.org/Team:SJTU-Software/Database/FutureDevelopment"><font face="Jokerman">For Future</font></a></li>
-
                         <li><a href="https://2014.igem.org/Team:SJTU-Software/Database/Event">Events</a></li>
+
                         <li><a href="https://2014.igem.org/Team:SJTU-Software/Database/Event"><font face="Jokerman">Events</font></a></li>
                     </ul>
                     </ul>
                 </li>
                 </li>
-
                 <li><a class="hsubs" href="">Requirement</a>
+
                 <li><a class="hsubs" href="https://2014.igem.org/Team:SJTU-Software/Requirement/Medal"><font face="Jokerman">Requirement</font></a>
                     <ul class="subs">
                     <ul class="subs">
-
                         <li><a href="https://2014.igem.org/Team:SJTU-Software/Requirement/Medal">Medal</a></li>
+
                         <li><a href="https://2014.igem.org/Team:SJTU-Software/Requirement/Medal"><font face="Jokerman">Medal</font></a></li>
-
                         <li><a href="https://2014.igem.org/Team:SJTU-Software/Requirement/Acknowledgement">Acknowledgement</a></li>
+
                         <li><a href="https://2014.igem.org/Team:SJTU-Software/Requirement/Acknowledgement"><font face="Jokerman">Acknowledgement</font></a></li>
                          
                          
-
                         <li><a href="https://2014.igem.org/Team:SJTU-Software/Requirement/HumanPractice">Human Practice</a></li>
+
                         <li><a href="https://2014.igem.org/Team:SJTU-Software/Requirement/HumanPractice"><font face="Jokerman">Human Practice</font></a></li>
                     </ul>
                     </ul>
                 </li>
                 </li>
-
                 <li><a href="https://2014.igem.org/Team:SJTU-Software/Team">Team</a>
+
                 <li><a href="https://2014.igem.org/Team:SJTU-Software/Team"><font face="Jokerman">Team</font></a>
                     <ul class="subs">
                     <ul class="subs">
-
                         <li><a href="https://2014.igem.org/Team:SJTU-Software/Team">Member</a></li>
+
                         <li><a href="https://2014.igem.org/Team:SJTU-Software/Team"><font face="Jokerman">Member</font></a></li>
                        
                        
                     </ul>
                     </ul>
Line 393: Line 393:
<li>
<li>
<div class="header">
<div class="header">
-
<span class="label"><a href="https://2014.igem.org/Team:SJTU-Software/Database"><font color=#ffffff>Database</font></a></span>
+
<span class="label"><a href="https://2014.igem.org/Team:SJTU-Software/Database"><font face="Jokerman" color=#ffffff>Database</font></a></span>
<span class="arrow up"></span>
<span class="arrow up"></span>
                                                          
                                                          
</div>
</div>
                                                 <ul class="menu">
                                                 <ul class="menu">
-
<li><a href="#dc">Data Collection</a></li>
+
<li><a href="#dc"><font face="Jokerman">Data Collection</font></a></li>
-
<li><a href="#sod">Structure of Database</a> </li>
+
<li><a href="#sod"><font face="Jokerman">Structure of Database</font></a> </li>
-
<li><a href="#qf">Quick Facts</a> </li>
+
<li><a href="#qf"><font face="Jokerman">Quick Facts</font></a> </li>
</ul>
</ul>
Line 406: Line 406:
<li>
<li>
<div class="header">
<div class="header">
-
<span class="label"><a href="https://2014.igem.org/Team:SJTU-Software/Database/AssessmentModel"><font color=#ffffff>Assessment Model</font></a></span>
+
<span class="label"><a href="https://2014.igem.org/Team:SJTU-Software/Database/AssessmentModel"><font face="Jokerman" color=#ffffff>Assessment Model</font></a></span>
</div>
</div>
Line 414: Line 414:
<li>
<li>
<div class="header">
<div class="header">
-
<span class="label"><a href="https://2014.igem.org/Team:SJTU-Software/Database/Conponent"><font color=#ffffff>Components in Design</font></a></span>
+
<span class="label"><a href="https://2014.igem.org/Team:SJTU-Software/Database/Conponent"><font face="Jokerman" color=#ffffff>Components in Present</font></a></span>
</div>
</div>
Line 421: Line 421:
<li>
<li>
<div class="header">
<div class="header">
-
<span class="label"><a href="https://2014.igem.org/Team:SJTU-Software/Database/FutureDevelopment"><font color=#ffffff>Further Development</font></a></span>
+
<span class="label"><a href="https://2014.igem.org/Team:SJTU-Software/Database/FutureDevelopment"><font face="Jokerman" color=#ffffff>Further Development</font></a></span>
</div>
</div>
</li>
</li>
                                         <li>
                                         <li>
<div class="header">
<div class="header">
-
<span class="label"><a href="https://2014.igem.org/Team:SJTU-Software/Database/Event"><font color=#ffffff>Events </font></a></span>
+
<span class="label"><a href="https://2014.igem.org/Team:SJTU-Software/Database/Event"><font face="Jokerman" color=#ffffff>Events </font></a></span>
</div>
</div>
</li>
</li>
Line 448: Line 448:
   
   
                           <div  class="container2" style="margin:-4% 0 0 0;height:200px;width:100%;float:left; display:inline" >
                           <div  class="container2" style="margin:-4% 0 0 0;height:200px;width:100%;float:left; display:inline" >
-
                           <p class="text"  style="margin:2% 60px auto"><font face="Helvetica" size="5px"  color="#242424">3. Database</font></p>
+
                           <p class="text"  style="margin:2% 60px auto"><font face="Helvetica" size="5px"  color="#242424">Database</font></p>
                             <p class="text"  style="margin:3% 60px auto"><font face="Helvetica" size="3px"  color="#242424">Here, we have reconstructed the database of the current existing biobricks. All the necessary information available on the Registry are collected and used to construct our own database. In this part, the source of data, the way of data collection, database structure and some facts of the biobricks in the database are introduced.</font></p>
                             <p class="text"  style="margin:3% 60px auto"><font face="Helvetica" size="3px"  color="#242424">Here, we have reconstructed the database of the current existing biobricks. All the necessary information available on the Registry are collected and used to construct our own database. In this part, the source of data, the way of data collection, database structure and some facts of the biobricks in the database are introduced.</font></p>
                           </div>
                           </div>
Line 463: Line 463:
   
   
                           <div  class="container2" style="margin:-4% 0 0 0;height:3350px;width:100%;float:left; display:inline"  >
                           <div  class="container2" style="margin:-4% 0 0 0;height:3350px;width:100%;float:left; display:inline"  >
-
                           <p class="text"  style="margin:2% 60px auto"><font face="Helvetica" size="5px"  color="#242424">3.1.1 Data collection</font></p>
+
                           <p class="text"  style="margin:2% 60px auto"><font face="Helvetica" size="5px"  color="#242424">Data collection</font></p>
                             <p class="text"  style="margin:3% 60px auto"><font face="Helvetica" size="3px"  color="#242424">Data are collected from 5 different websites on the Registry and Google Scholar.<br>  
                             <p class="text"  style="margin:3% 60px auto"><font face="Helvetica" size="3px"  color="#242424">Data are collected from 5 different websites on the Registry and Google Scholar.<br>  
-
The data needed in the reconstructed biobrick database is available from 5 sources, with four of them from the websites of Registry of Standard Biological Parts and 1 of them from Google Scholar. Addresses of those sources for BBa_B0034 are listed in Table 2.1.1, and the part name could be replaced by any biobrick.
+
The data needed in the reconstructed biobrick database is available from 5 sources, with four of them from the websites of Registry of Standard Biological Parts and 1 of them from Google Scholar. Addresses of those sources for BBa_B0034 are listed in Table 1, and the part name could be replaced by any biobrick.
</font></p>         
</font></p>         
<table border="1" borderColor="#ECC2FF" style="margin:1% 60px auto;height:100px;width:80%;font-size:1px;font-family:Helvetica;" >
<table border="1" borderColor="#ECC2FF" style="margin:1% 60px auto;height:100px;width:80%;font-size:1px;font-family:Helvetica;" >
Line 477: Line 477:
</table>   
</table>   
-
<p class="text"  style="margin:1% 60px auto"><font face="Helvetica" size="1px"  color="#242424">Table 2.1.1 Sources of the data in the biobrick database, using BBa_B0034 as an example
+
<p class="text"  style="margin:1% 60px auto"><font face="Helvetica" size="1px"  color="#242424">Table 1 Sources of the data in the biobrick database, using BBa_B0034 as an example
</font></p>  
</font></p>  
-
<p class="text"  style="margin:3% 60px auto"><font face="Helvetica" size="3px"  color="#242424">PERL scripts are composed to connect to those links and to pick out the information we need. In order to connect to those links, we need to understand the way how biobricks on the website are named. There exist two main ways to name the biobricks, which are illustrated in Table 2.1.2 and Table 2.1.3. “BBa” is used for most biobricks, names of which consist of 3 parts. The first part is “BBa_”; the second part is a capitalized letter; the third part is several digits, the number of which depends on the previous capitalized letter (possible combinations are listed in Table 2.1.2). “pSB” is specially used for plasmids, names of which consist of 4 parts. The first part is “pSB”; the second part is one digit ranging from 1 to 9; the third part is a single pattern or a combination of two patterns listed; the fourth part can be any number from 1 to 29.
+
<p class="text"  style="margin:3% 60px auto"><font face="Helvetica" size="3px"  color="#242424">PERL scripts are composed to connect to those links and to pick out the information we need. In order to connect to those links, we need to understand the way how biobricks on the website are named. There exist two main ways to name the biobricks, which are illustrated in Table 2 and Table 3. “BBa” is used for most biobricks, names of which consist of 3 parts. The first part is “BBa_”; the second part is a capitalized letter; the third part is several digits, the number of which depends on the previous capitalized letter (possible combinations are listed in Table 2). “pSB” is specially used for plasmids, names of which consist of 4 parts. The first part is “pSB”; the second part is one digit ranging from 1 to 9; the third part is a single pattern or a combination of two patterns listed; the fourth part can be any number from 1 to 29.
</font></p>   
</font></p>   
      
      
Line 510: Line 510:
<p class="text"  style="margin:1% 60px auto"><font face="Helvetica" size="1px"  color="#242424">
<p class="text"  style="margin:1% 60px auto"><font face="Helvetica" size="1px"  color="#242424">
-
Table 2.1.2 Rules in naming biobricks starting with “BBa_”
+
Table 2 Rules in naming biobricks starting with “BBa_”
</font></p>  
</font></p>  
Line 523: Line 523:
<p class="text"  style="margin:1% 60px auto"><font face="Helvetica" size="1px"  color="#242424">
<p class="text"  style="margin:1% 60px auto"><font face="Helvetica" size="1px"  color="#242424">
-
Table 2.1.3 Rules in naming biobricks starting with “pSB”
+
Table 3 Rules in naming biobricks starting with “pSB”
</font></p>  
</font></p>  
-
<p class="text"  style="margin:3% 60px auto"><font face="Helvetica" size="3px"  color="#242424">By substituting the names listed in Table 2.1.2 and Table 2.1.3 for the part name (BBa_B0034) in the addresses listed in Table 2.1.1, we can get access to the links about the information on biobricks. Data that are collected by PERL scripts from each website are listed in Table 2.1.4. More detailed description of those data are available in Table 2.1.5. PERL scripts used to collect those data are available on GitHub.
+
<p class="text"  style="margin:3% 60px auto"><font face="Helvetica" size="3px"  color="#242424">By substituting the names listed in Table 2 and Table 3 for the part name (BBa_B0034) in the addresses listed in Table 1, we can get access to the links about the information on biobricks. Data that are collected by PERL scripts from each website are listed in Table 4. More detailed description of those data are available in Table 5. PERL scripts used to collect those data are available on GitHub.
</font></p>   
</font></p>   
Line 542: Line 542:
<p class="text"  style="margin:1% 60px auto"><font face="Helvetica" size="1px"  color="#242424">
<p class="text"  style="margin:1% 60px auto"><font face="Helvetica" size="1px"  color="#242424">
-
Table 2.1.4 Data collected from the 5 sources
+
Table 4 Data collected from the 5 sources
</font></p>  
</font></p>  
Line 586: Line 586:
</table>   
</table>   
-
<p class="text"  style="margin:1% 60px auto"><font face="Helvetica" size="1px"  color="#242424">
+
<p class="text"  style="margin:1% 60px auto" margin="center"><font face="Helvetica" size="1px"  color="#242424">
-
?????????????????????????????????????????????????????
+
Table 5 Description of attributes in Easy BBK database
</font></p>  
</font></p>  
Line 608: Line 608:
   
   
                           <div  class="container2" style="margin:-4% 0 0 0;height:600px;width:100%;float:left; display:inline" >
                           <div  class="container2" style="margin:-4% 0 0 0;height:600px;width:100%;float:left; display:inline" >
-
                           <p class="text"  style="margin:2% 60px auto"><font face="Helvetica" size="5px"  color="#242424">3.1.2 Database Structure</font></p>
+
                           <p class="text"  style="margin:2% 60px auto"><font face="Helvetica" size="5px"  color="#242424">Database Structure</font></p>
-
                             <p class="text"  style="margin:3% 60px auto"><font face="Helvetica" size="3px"  color="#242424">The structure of the database is presented in Figure 3.1. The primary key in table “Main” is “part name”, with all the other tables linked to it by identical “part name”. There is no primary key in the tables except “Main” because biobricks could belong to more than one category or have more than one twins. Thus, the part name in the rest tables could be repeated for several times, depending on different biobricks.</font></p>
+
                             <p class="text"  style="margin:3% 60px auto"><font face="Helvetica" size="3px"  color="#242424">The structure of the database is presented in Figure 1. The primary key in table “Main” is “part name”, with all the other tables linked to it by identical “part name”. There is no primary key in the tables except “Main” because biobricks could belong to more than one category or have more than one twins. Thus, the part name in the rest tables could be repeated for several times, depending on different biobricks.</font></p>
                            
                            
                            
                            
                           <img src="https://static.igem.org/mediawiki/2014/8/8e/Sjtu_software_database.jpg" style="width:80%;height:auto;padding:2% 8%"></img>
                           <img src="https://static.igem.org/mediawiki/2014/8/8e/Sjtu_software_database.jpg" style="width:80%;height:auto;padding:2% 8%"></img>
-
<p class="text"  style="margin:1% 60px auto"><font face="SimSun" size="1px"  color="#242424">Figure 3.1 The structure of the reconstructed biobrick database
+
<p class="text"  style="margin:1% 60px auto"><font face="SimSun" size="1px"  color="#242424">Figure 1 The structure of the reconstructed biobrick database
</font></p>  
</font></p>  
                            
                            
Line 628: Line 628:
                           <br>
                           <br>
                               <div  class="container2" style="margin:-4% 0 0 0;height:130px;width:100%;float:left; display:inline"  >
                               <div  class="container2" style="margin:-4% 0 0 0;height:130px;width:100%;float:left; display:inline"  >
-
                           <p class="text"  style="margin:2% 60px auto"><font face="Helvetica" size="5px"  color="#242424">3.1.3 Quick Facts about the Biobricks</font></p>
+
                           <p class="text"  style="margin:2% 60px auto"><font face="Helvetica" size="5px"  color="#242424">Quick Facts about the Biobricks</font></p>
<p class="text"  style="margin:2% 60px auto"><font face="Helvetica" size="3px"  color="#242424">Here are figures counting the number of the values of some important attributes judging the quality of the biobricks.<br><br></font></p></div>
<p class="text"  style="margin:2% 60px auto"><font face="Helvetica" size="3px"  color="#242424">Here are figures counting the number of the values of some important attributes judging the quality of the biobricks.<br><br></font></p></div>
  <div  class="container2" style="margin:-4% 0 0 0;height:250px;width:50%;float:left; display:inline;" >
  <div  class="container2" style="margin:-4% 0 0 0;height:250px;width:50%;float:left; display:inline;" >
Line 703: Line 703:
      
      
<div align=center>
<div align=center>
-
     <div  class="container2" style="height:150px;width:71%;background-color: #272727;margin:-3.6% " >
+
     <div  class="container2" style="height:150px;width:71%;background-color: #272727;margin:-3.7% " >
           <div  class="container2" style="height:80px;width:100%;background-color: #272727;float:left; display:inline;" >
           <div  class="container2" style="height:80px;width:100%;background-color: #272727;float:left; display:inline;" >
  <div  style=" float:left;margin:3% auto auto 4%;">       
  <div  style=" float:left;margin:3% auto auto 4%;">       
Line 735: Line 735:
                           <br>
                           <br>
                           <br>
                           <br>
-
  <p class="container2"  style="margin:0% 5% auto"><font face="SimSun" size="4px"  color="#FFFFFF">iGemdry2014@163.com</font></p>
+
  <p class="container2"  style="margin:0% 5% auto"><font face="MoolBoran" size="5px"  color="#FFFFFF">iGemdry2014@163.com</font></p>
-
                           <p class="container2" style="margin:0 5% auto"><font face="SimSun" size="4px"  color="#FFFFFF">SJTU-Software,Shanghai,China</font></p>
+
                           <p class="container2" style="margin:0 5% auto"><font face="MoolBoran" size="5px"  color="#FFFFFF">SJTU-Software,Shanghai,China</font></p>
                            
                            
                            
                            

Latest revision as of 20:12, 17 October 2014




Database

Here, we have reconstructed the database of the current existing biobricks. All the necessary information available on the Registry are collected and used to construct our own database. In this part, the source of data, the way of data collection, database structure and some facts of the biobricks in the database are introduced.



Data collection

Data are collected from 5 different websites on the Registry and Google Scholar.
The data needed in the reconstructed biobrick database is available from 5 sources, with four of them from the websites of Registry of Standard Biological Parts and 1 of them from Google Scholar. Addresses of those sources for BBa_B0034 are listed in Table 1, and the part name could be replaced by any biobrick.

 
Name of WebsitesAddress  
XML formathttp://parts.igem.org/cgi/xml/part.cgi?part=BBa_B0034  
Hard informationhttp://parts.igem.org/cgi/partsdb/part_info.cgi?part_name=BBa_B0034
Get parthttp://parts.igem.org/partsdb/get_part.cgi?part=BBa_B0034
Experiencehttp://parts.igem.org/Part:BBa_B0034:Experience
Google scholarhttp://scholar.google.com.cn/scholar?q=BBa_B0034

Table 1 Sources of the data in the biobrick database, using BBa_B0034 as an example

PERL scripts are composed to connect to those links and to pick out the information we need. In order to connect to those links, we need to understand the way how biobricks on the website are named. There exist two main ways to name the biobricks, which are illustrated in Table 2 and Table 3. “BBa” is used for most biobricks, names of which consist of 3 parts. The first part is “BBa_”; the second part is a capitalized letter; the third part is several digits, the number of which depends on the previous capitalized letter (possible combinations are listed in Table 2). “pSB” is specially used for plasmids, names of which consist of 4 parts. The first part is “pSB”; the second part is one digit ranging from 1 to 9; the third part is a single pattern or a combination of two patterns listed; the fourth part can be any number from 1 to 29.

 
The First Part of the NameThe Second Part of the NameThe Third Part of the Name (Number of Digits)Examples
BBa_  
A6BBa_A340620
B4BBa_B0034
C4/5/6BBa_C0053; BBa_C10001
E4BBa_E5504
F4BBa_F2622
G4/5BBa_G0011; BBa_G00500
I4/5/6BBa_I10018
J4/5/6BBa_J52100; BBa_J540013
K6/7BBa_K374013; BBa_K1218016
M4/5BBa_M1904; BBa_M31000
P4BBa_P2007
Q5/6BBa_Q200514
R4BBa_R4037
S5BBa_S01297
T4BBa_T1009
V4BBa_V1022
Y5BBa_Y00100
Z4/5BBa_Z0506; BBa_Z52935  

Table 2 Rules in naming biobricks starting with “BBa_”

 
The First Part of the NameThe Second Part of the NameThe Third Part of the Name The Fourth Part of the NameExamples  
pSB1~9A/C/E/G/K/N/Na/R/S/St/T/Tm/Z1~29pSB1K16
pSB1~9Combination of 2 letters above1~29pSB1K16  

Table 3 Rules in naming biobricks starting with “pSB”

By substituting the names listed in Table 2 and Table 3 for the part name (BBa_B0034) in the addresses listed in Table 1, we can get access to the links about the information on biobricks. Data that are collected by PERL scripts from each website are listed in Table 4. More detailed description of those data are available in Table 5. PERL scripts used to collect those data are available on GitHub.

 
Name of WebsitesAddress  
XML formatpart id; part name; part short name; part short description; part type; part status; sample status; part results; part nickname; part rating; part url; part entered; part author; Sequences; Samples; References; groups; deep subparts; specified subparts; specified subscars; features; parameters; categories; twins
Hard informationDNA status; Group Favorite; Whether or not deleted; Used Times; Length of Documentation
Get partConfirmed Times; Not Confirmed Details
ExperienceAverage Rating; Number of Comments
Google scholarNumber of Publication; URL of the most related publication  

Table 4 Data collected from the 5 sources

 
PropertyDescription  
part idOfficial name of the part
part nameBBa_B0034
part short namePart name without “BBa_”
part short descriptionThe short description is usually a biological or technical descriptor of the part. It will show up on the part page
part typeThis will state the part type/function, and will show up at the top of the part page, to the left of the DNA Status
part status The status of the part based on the completeness of its documentation and characterization.system not currently in place
sample statusThe status of the part's physical DNA (sample) in the Repository
part resultsThe experience status for a part, as documented by the part authors
part nicknameNickname of the part
part ratingWhether there is a registry star for the part
part urlURL of main page for the part
part enteredEntered date of the part
part authorAuthor of the part
SequencesNucleotide sequence of the part
SamplesIt’s not enabled now
ReferencesIt’s not enabled now
GroupsIt’s not enabled now
deep subpartsAll subparts that compose the subparts in the part
specified subpartsAll subparts that compose the part
specified subscarsAll scars between subparts
FeaturesFeatures of the part
ParametersThe parameters are submitter-decided, allowing for a degree of technical specification for the part.
CategoriesCategories allow for a part to become content in automatically generated part tables, which is important in defining the organization of your part within the Registry, and specifically for the Catalog of Parts and Device
TwinsTwo or more parts are twins if they have the same sequence
DNA statusStates the DNA status of your part: Deleted, Planning, Sent, Available, etc. These statuses are generated by the Registry, so the user cannot edit them.
Group Favorite One can choose if the part is a favorite of your team/group.
Whether or not deletedWhether the part is deleted
Used TimesThe number of times the part has been specified in composite parts in the Registry
Confirmed TimesThe number of times the part sequence has been confirmed by users
Not Confirmed DetailsDetails of not confirmed facts
Average ratingThe mean value of rating for the part given by users
Number of CommentsThe number of comments from users
Number of PublicationThe number of related results of the part on Google Scholar
URL of the most related publicationThe most related result of the part on Google Scholar  

Table 5 Description of attributes in Easy BBK database



Database Structure

The structure of the database is presented in Figure 1. The primary key in table “Main” is “part name”, with all the other tables linked to it by identical “part name”. There is no primary key in the tables except “Main” because biobricks could belong to more than one category or have more than one twins. Thus, the part name in the rest tables could be repeated for several times, depending on different biobricks.

Figure 1 The structure of the reconstructed biobrick database



Quick Facts about the Biobricks

Here are figures counting the number of the values of some important attributes judging the quality of the biobricks.



iGemdry2014@163.com

SJTU-Software,Shanghai,China

back to top