Team:TU-Eindhoven/Parts

From 2012.igem.org

(Difference between revisions)
Line 3: Line 3:
<groupparts>iGEM012 TU-Eindhoven</groupparts>
<groupparts>iGEM012 TU-Eindhoven</groupparts>
[[File:GECO.jpg|400px|center]]
[[File:GECO.jpg|400px|center]]
-
<p>To start off with, the iGEM team decided to prepare BioBricks of the GECO proteins since the BioBricks of the calcium channels CCH1 and MID1 (<partinfo>BBa_K363008</partinfo> and <partinfo>BBa_K363009</partinfo> respectively) are already available and able to ligate directly into bacterial plasmids. Moreover, to ligate these calcium channels into yeast plasmids, it's more practical to order the sequences directly from Iida<html><a href="#ref_Iida"name="text_Iida"><sup>[2]</sup></a></html>, because then the sequence is immediately available for yeast plasmids.</p>
+
<p>To start off with, the iGEM team decided to prepare BioBricks of the GECO proteins since the BioBricks of the calcium channels CCH1 and MID1 (<partinfo>BBa_K363008</partinfo> and <partinfo>BBa_K363009</partinfo> respectively) are already available and able to ligate directly into bacterial plasmids. Moreover, to ligate these calcium channels into yeast plasmids, it's more practical to order the sequences directly from Iida<html><a href="#ref_Iida"name="text_Iida"><sup>[1]</sup></a></html>, because then the sequence is immediately available for yeast plasmids.</p>
<br />
<br />
-
<p>Our iGEM team prepared three different BioBricks: BBa_K881000 (R-GECO), BBa_K881001 (G-GECO), BBa_K881002 (B-GECO). These three <span class="lightblue">GECO proteins</span>, which are obtained from ''Zhao et al. 2011''<html><a href="#ref_zhao" name="text_zhao"><sup>[1]</sup></a></html>, are red, green and blue fluorescent respectively. The protocol for ligation and restriction obtained from the BioBrick library didn't work for our Biobricks. Therefore, we designed <span class="lightblue">our own protocol</span>, which can be found at the '[[Team:TU-Eindhoven/Protocols|Protocol]]' page, and is shortly described here. The coding DNA for these three proteins was ligated into a <partinfo>pSB1C3</partinfo> vector. After culturing, the vectors were restricted with restriction enzymes XbaI en PstI. These enzymes restricted the vector nicely, however, the DNA sequence coding for the fluorescent GECO proteins appears to contain a restriction site for PstI aswell. Therefore, this procedure was repeated with restriction enzymes <span class="lightblue">XbaI</span> and <span class="lightblue">SpeI</span>. Using this restriction method, the BioBricks can be used in <span class="lightblue">yeast</span> cells and <span class="lightblue">E. coli</span> bacteria.</p>
+
<p>Our iGEM team prepared three different BioBricks: BBa_K881000 (R-GECO), BBa_K881001 (G-GECO), BBa_K881002 (B-GECO). These three <span class="lightblue">GECO proteins</span>, which are obtained from ''Zhao et al. 2011''<html><a href="#ref_zhao" name="text_zhao"><sup>[2]</sup></a></html>, are red, green and blue fluorescent respectively. The protocol for ligation and restriction obtained from the BioBrick library didn't work for our Biobricks. Therefore, we designed <span class="lightblue">our own protocol</span>, which can be found at the '[[Team:TU-Eindhoven/Protocols|Protocol]]' page, and is shortly described here. The coding DNA for these three proteins was ligated into a <partinfo>pSB1C3</partinfo> vector. After culturing, the vectors were restricted with restriction enzymes XbaI en PstI. These enzymes restricted the vector nicely, however, the DNA sequence coding for the fluorescent GECO proteins appears to contain a restriction site for PstI aswell. Therefore, this procedure was repeated with restriction enzymes <span class="lightblue">XbaI</span> and <span class="lightblue">SpeI</span>. Using this restriction method, the BioBricks can be used in <span class="lightblue">yeast</span> cells and <span class="lightblue">E. coli</span> bacteria.</p>
<br />
<br />
<p>Although, these BioBricks are prepared in a more efficient way using our own protocol, the <span class="lightblue">permission</span> we needed to apply the GECO BioBricks to registry library was more difficult than expected. You can read more about this struggle at the '[[Team:TU-Eindhoven/Thoughts|Other Thoughts]]' page.</p>
<p>Although, these BioBricks are prepared in a more efficient way using our own protocol, the <span class="lightblue">permission</span> we needed to apply the GECO BioBricks to registry library was more difficult than expected. You can read more about this struggle at the '[[Team:TU-Eindhoven/Thoughts|Other Thoughts]]' page.</p>
Line 28: Line 28:
<html>
<html>
<ul>
<ul>
-
<li><a href="#text_zhao" name="ref_zhao">[1]</a> Y. Zhao, et al., An expanded palette of genetically encoded Ca2+ indicators, Science 333: 1888-1891, (2011)</a></li>
+
<li><a href="#text_Iida" name="ref_Iida">[1]</a> K. Iida, et al., Essential, completely conserved glycine residue in the domain III S2S3 linker of voltage-gated calcium channel α1 subunits in yeast and mammals, Journal of Biological Chemistry 282: 25659-25667, (2007)</a></li>
-
<li><a href="#text_Iida" name="ref_Iida">[2]</a> K. Iida, et al., Essential, completely conserved glycine residue in the domain III S2S3 linker of voltage-gated calcium channel α1 subunits in yeast and mammals, Journal of Biological Chemistry 282: 25659-25667, (2007)</a></li>
+
<li><a href="#text_zhao" name="ref_zhao">[2]</a> Y. Zhao, et al., An expanded palette of genetically encoded Ca2+ indicators, Science 333: 1888-1891, (2011)</a></li>
</ul>
</ul>
</html>
</html>
{{:Team:TU-Eindhoven/Templates/footer}}
{{:Team:TU-Eindhoven/Templates/footer}}

Revision as of 00:14, 27 September 2012