Team:Groningen/OurBiobrick

From 2012.igem.org

(Difference between revisions)
 
(65 intermediate revisions not shown)
Line 10: Line 10:
z1 {  
z1 {  
font-size:18pt;
font-size:18pt;
-
line-height:21pt;
+
                        line-height:21pt;
-
color:white;
+
                        color:white;
}
}
 +
                 .ctd {
                 .ctd {
                         width: 220px;
                         width: 220px;
-
text-align: center;
+
text-align: center;
-
                        background: #000;
+
background: #000;
-
 
+
background-color: rgba(0,0,0,0.3);
-
background-color: transparent;
+
padding: 5px ;
-
background-color: rgba(0,0,0,0.3);
+
margin: 30px auto;
-
                        padding: 10px ;
+
color: #FFF;
-
                        margin: 30px auto;
+
-
                     
+
-
                        color: #FFF;
+
                 }
                 }
                 .cte {
                 .cte {
-
                        width: 250px;
+
                      width: 250px;
-
text-align: center;
+
      text-align: center;
-
                        background: #000;
+
      background: #000;
-
 
+
      padding-right:10px;
-
padding-right:10px;
+
      padding-left:10px;
-
padding-left:10px;
+
      background-color: rgba(0,0,0,0.3);
-
                        margin: 0 auto;
+
      margin: 0px auto;
-
background-color: transparent;
+
      color: #FFF;
-
  background-color: rgba(0,0,0,0.3);
+
-
 
+
-
                        color: #FFF;
+
-
 
+
                 }
                 }
</style>
</style>
 +
<br>
<div class="cte">
<div class="cte">
<div class="ctd">
<div class="ctd">
Line 50: Line 45:
</head>
</head>
</html>
</html>
-
 
<html>
<html>
<head>
<head>
Line 62: Line 56:
margin-top:0px;
margin-top:0px;
margin-bottom:20px;
margin-bottom:20px;
-
margin-left:100px;
+
margin-left:150px;
-
margin-right:100px;
+
margin-right:150px;
}
}
-
 
+
p.z5 {
 +
font-size:10pt;
 +
line-height:10pt;
 +
color:white;
 +
margin-top:0px;
 +
margin-bottom:20px;
 +
margin-left:150px;
 +
margin-right:150px;
 +
}
ol li{  
ol li{  
-
   margin-left:100px;
+
   margin-left:150px;
-
   margin-right:100px;  
+
   margin-right:150px;  
}
}
</style>
</style>
Line 74: Line 76:
<body>
<body>
-
<p class="margin">An important aspect of the iGEM competition is the use and creation of standard  biological parts. Each team will make new parts during iGEM and will place them in the [http://partsregistry.org Registry of Standard Biological Parts]. The iGEM software provides an easy way to present the parts your team has created . The "groupparts" tag will generate a table with all of the parts that your team adds to your team sandbox.  Note that if you want to document a part you need to document it on the [http://partsregistry.org Registry], not on your team wiki.
+
<p class="margin">
-
 
+
These are the biobricks that team Groningen submitted to the registry.  
-
Remember that the goal of proper part documentation is to describe and define a part such that it can be used without a need to refer to the primary literature. The next iGEM team should be able to read your documentation and be able to use the part successfully. Also, you should provide proper references to acknowledge previous authors and to provide for  users who wish to know more.
+
</p>
</p>
</body>
</body>
Line 83: Line 84:
| <groupparts>iGEM012 Groningen</groupparts>
| <groupparts>iGEM012 Groningen</groupparts>
|}
|}
 +
<br>
 +
<p class="z5">
 +
<i>The pink heart means 'group favorite' and 'W' means works.</i>
 +
</p>
<html>
<html>
<head>
<head>
Line 94: Line 99:
margin-top:0px;
margin-top:0px;
margin-bottom:20px;
margin-bottom:20px;
-
margin-left:100px;
+
margin-left:150px;
-
margin-right:100px;
+
margin-right:150px;
}
}
z2 {  
z2 {  
-
font-size:18pt;
+
font-size:14pt;
-
line-height:18pt;
+
line-height:15pt;
-
color:white;
+
color: #FF6700;
-
background-color: rgba(0,0,0,0.3);
+
}
 +
 
 +
.centerimage{
 +
margin: 0 auto;
 +
width: 350px;
}
}
ol li{  
ol li{  
-
   margin-left:100px;
+
   margin-left:150px;
-
   margin-right:100px;  
+
   margin-right:150px;  
}
}
 +
a:link {
 +
color: #FF6700;
 +
}
 +
a:visited {
 +
color: #333333;
 +
}
 +
a:hover {
 +
color: #FF6700;
 +
}
 +
a:active {
 +
color: #FF6700;
 +
}
</style>
</style>
</head>
</head>
Line 113: Line 134:
<br><br>
<br><br>
<p class="margin">
<p class="margin">
-
<z2>BBa_K818000</z2>
+
<A HREF="http://partsregistry.org/Part:BBa_K818000" TARGET="_BLANK"><z2>BBa_K818000</z2></A><br>
-
<br>
+
This backbone was designed to fulfill the need of a working <i>Bacillus subtilis</i> backbone for our project. This backbone plasmid was derived from pSac-Cm by insertion of the biobrick compatible restriction sites (prefixes and suffixes), a terminator (<A HREF="http://partsregistry.og/Part:BBa_B0015" TARGET="_BLANK"><FONT COLOR=#ff6700>BBa_B0015</FONT></A>) after the suffixes sequences and the sequence for red fluorescent protein (RFP) in its multiple cloning site (MCS). <br><br>
-
This backbone was designed to fulfill the need of a working Bacillus subtilis backbone for our project. This backbone plasmid was derived from pSac-Cm by insertion of biobrick compatible restriction sites (prefixes and suffixes), a terminator (BBa_B0015) after the suffixes sequences, and red fluorescent protein sequence (RFP) in between the prefix and suffix in its multiple cloning sites (MCS). New biobricks can be inserted into this vector by replacement of the RFP biobrick, and selection of the white colonies. This backbone has a multi host replication origin and replicates in E. coli and Bacillus subtilis. The plasmid is designed to integrate a cloned insert into the B. subtilis chromosome via double recombination between plasmid and chromosomal sacA sequences.
+
-
The terminator insertion after the suffixes in combination and insertion of the red fluorescent protein (RFP) in between the insertion site were meant to make cloning easier and faster. Transformants with inserts will not produce red color (as the RFP is replaced by the insert).
+
 +
This backbone has a multi host replication origin and replicates in <i>E. coli</i>. In <i>Bacillus subtilis</i>, the plasmid integrates at sacA. The plasmid is designed to integrate a cloned insert into the <i>B. subtilis</i> chromosome via double recombination between plasmid and chromosomal <i>sacA</i> sequences. This makes it easy to check for double crossover problems after transformation in <i>Bacillus subtilis</i>: transformants with the correct insertion will not be able to metabolize sucrose.<br><br>
 +
 +
Another advantage of using this plasmid is that it gives a stable, single copy plasmid integration inside the <i>Bacillus subtilis</i> chromosome, therefore, antibiotic selection is not necessary once the insert is transformed into <i>Bacillus subtilis</i>. This enables easy, stable cloning.<br><br>
 +
 +
The terminator insertion after the suffixes in combination of the red fluorescent protein (RFP) were meant to make cloning easier and faster: new biobricks can be inserted into this vector by replacement of the RFP biobrick. <i>E. coli</i> transformants with inserts will not produce red color (as the RFP is replaced by the insert), so the colonies can be picked easily (see the picture below).
 +
<div  align="center">
 +
<img class="centerimage" src="https://static.igem.org/mediawiki/2012/2/21/Groningen2012_EJ_20120912_psaccmt-RFP-contruct.png" width="200">
 +
<img class="centerimage" src="http://partsregistry.org/wiki/images/8/8f/Groningen2012_RR_20120914_psaccmt-RFP_redwhite_s.jpg" width="200">
 +
</div>
 +
<br>
 +
<p class="margin">
 +
The plasmid is transformed into any <i>B. subtilis</i> 168 host with selection for chloramphenicol (cat gene) resistance. This plasmid can be amplified inside <i>E.coli</i> with selection for chloramphenicol or ampicillin, and using red-white screening (see above). As described by the <A HREF="2010.igem.org/Team:Groningen" TARGET="_BLANK"><FONT COLOR=#ff6700>iGEM Groningen 2010</FONT></A> team, the red fluorescent protein cannot be produced in <i>Bacillus subtilis</i>.
 +
</p>
 +
<br>
 +
<p class="margin">
 +
<A HREF="http://partsregistry.org/Part:BBa_K818100" TARGET="_BLANK"><z2>BBa_K818100</z2></A><z2> and </z2><A HREF="http://partsregistry.org/Part:BBa_K818200" TARGET="_BLANK"><z2>BBa_K818200</z2></A><br>
 +
<i>SboA</i> and <i>Fnr</i> are the two promoters in <i>Bacillus subtilis</i> that are the most upregulated by the rotten meat's volatiles. See the <A HREF="https://2012.igem.org/Team:Groningen/Sensor"><FONT COLOR=#ff6700>sensor page</FONT></A> for more information on how we identified them, and the <A HREF="https://2012.igem.org/Team:Groningen/Construct"><FONT COLOR=#ff6700>construct page</FONT></A> for the characterization of these promoters. <br>
 +
<br>
 +
<z2>BBa_K818300</z2><br>
 +
The <i>alsT</i> promoter is a promoter in <i>B. subtilis</i> repressed by TnrA which is active in the presence of low ammonium in the environment. TnrA will be deactivated in the presence of high ammonium in the environment. When TnrA is deactivated, <i>alsT</i> is no longer repressed. Ammonium is detected in the rotten meat and it can be used as a precursor of the rotting process and the increasing concentration of ammonium will trigger the TnrA - <i>alsT</i> reaction which means activating alsT promoter and activating the downstream genes.<br>
 +
<br>
 +
<z2>BBa_K818400, BBa_K818500, and BBa_K818600</z2><br>
 +
A coding device to generate reporters (AmilCP, Lycopene, and AmilGFP) under regulation of sboA promoter. When the sboA promoter is activated, the downstream reporter will be produced. Please go to the <A HREF="https://2012.igem.org/Team:Groningen/Construct" TARGET="_BlANK"><FONT COLOR=#ff6700>Construct page</FONT></A> for a detailed characterization of the working of the <i>SboA</i>-AmilGFP construct.
 +
<br>
 +
<div  align="center">
 +
<img class="centerimage" src="https://static.igem.org/mediawiki/2012/c/c4/Groningen2012_EJ_20120921_Sboa-reporter-coding_device.png" width="200">
 +
</div></p>
 +
<br>
 +
<p class="margin">
 +
<z2>BBa_K818210 and BBa_K818310</z2>
 +
A coding device to generate lycopene (red pigment) under regulation of fnr promoter (BBa_K818210) and to generate AmilGFP under regulation of alsT promoter (BBa_K818310). When the promoter is activated, the downstream reporter will be produced. <br>
 +
<br><br><br>
</p>
</p>
</body>
</body>
</html>
</html>
{{Template:SponsorsGroningen2012}}
{{Template:SponsorsGroningen2012}}

Latest revision as of 18:35, 26 October 2012





Submitted BioBricks

These are the biobricks that team Groningen submitted to the registry.

<groupparts>iGEM012 Groningen</groupparts>


The pink heart means 'group favorite' and 'W' means works.



BBa_K818000
This backbone was designed to fulfill the need of a working Bacillus subtilis backbone for our project. This backbone plasmid was derived from pSac-Cm by insertion of the biobrick compatible restriction sites (prefixes and suffixes), a terminator (BBa_B0015) after the suffixes sequences and the sequence for red fluorescent protein (RFP) in its multiple cloning site (MCS).

This backbone has a multi host replication origin and replicates in E. coli. In Bacillus subtilis, the plasmid integrates at sacA. The plasmid is designed to integrate a cloned insert into the B. subtilis chromosome via double recombination between plasmid and chromosomal sacA sequences. This makes it easy to check for double crossover problems after transformation in Bacillus subtilis: transformants with the correct insertion will not be able to metabolize sucrose.

Another advantage of using this plasmid is that it gives a stable, single copy plasmid integration inside the Bacillus subtilis chromosome, therefore, antibiotic selection is not necessary once the insert is transformed into Bacillus subtilis. This enables easy, stable cloning.

The terminator insertion after the suffixes in combination of the red fluorescent protein (RFP) were meant to make cloning easier and faster: new biobricks can be inserted into this vector by replacement of the RFP biobrick. E. coli transformants with inserts will not produce red color (as the RFP is replaced by the insert), so the colonies can be picked easily (see the picture below).


The plasmid is transformed into any B. subtilis 168 host with selection for chloramphenicol (cat gene) resistance. This plasmid can be amplified inside E.coli with selection for chloramphenicol or ampicillin, and using red-white screening (see above). As described by the iGEM Groningen 2010 team, the red fluorescent protein cannot be produced in Bacillus subtilis.


BBa_K818100 and BBa_K818200
SboA and Fnr are the two promoters in Bacillus subtilis that are the most upregulated by the rotten meat's volatiles. See the sensor page for more information on how we identified them, and the construct page for the characterization of these promoters.

BBa_K818300
The alsT promoter is a promoter in B. subtilis repressed by TnrA which is active in the presence of low ammonium in the environment. TnrA will be deactivated in the presence of high ammonium in the environment. When TnrA is deactivated, alsT is no longer repressed. Ammonium is detected in the rotten meat and it can be used as a precursor of the rotting process and the increasing concentration of ammonium will trigger the TnrA - alsT reaction which means activating alsT promoter and activating the downstream genes.

BBa_K818400, BBa_K818500, and BBa_K818600
A coding device to generate reporters (AmilCP, Lycopene, and AmilGFP) under regulation of sboA promoter. When the sboA promoter is activated, the downstream reporter will be produced. Please go to the Construct page for a detailed characterization of the working of the SboA-AmilGFP construct.


BBa_K818210 and BBa_K818310 A coding device to generate lycopene (red pigment) under regulation of fnr promoter (BBa_K818210) and to generate AmilGFP under regulation of alsT promoter (BBa_K818310). When the promoter is activated, the downstream reporter will be produced.



Our sponsors:

Retrieved from "http://2012.igem.org/Team:Groningen/OurBiobrick"