Team:Edinburgh/Project
From 2010.igem.org
(4 intermediate revisions not shown) | |||
Line 48: | Line 48: | ||
<li><a href="https://2010.igem.org/Team:Edinburgh/BioBricks#Genomic">submitted parts</a></li> | <li><a href="https://2010.igem.org/Team:Edinburgh/BioBricks#Genomic">submitted parts</a></li> | ||
<li><a href="https://2010.igem.org/Team:Edinburgh/Results#Genomic">results</a></li> | <li><a href="https://2010.igem.org/Team:Edinburgh/Results#Genomic">results</a></li> | ||
- | <li><a href="https://2010.igem.org/Team:Edinburgh/Project/Future">future | + | <li><a href="https://2010.igem.org/Team:Edinburgh/Project/Future">the future</a></li> |
<li><a href="https://2010.igem.org/Team:Edinburgh/Project/References">references</a></li> | <li><a href="https://2010.igem.org/Team:Edinburgh/Project/References">references</a></li> | ||
</ul> | </ul> | ||
Line 55: | Line 55: | ||
<li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial" class="dir">bacterial BRIDGEs</a> | <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial" class="dir">bacterial BRIDGEs</a> | ||
<ul> | <ul> | ||
- | <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial/Core_repressilator">the | + | <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial/Core_repressilator">the project</a></li> |
<li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial/Red_light_producer">red light</a></li> | <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial/Red_light_producer">red light</a></li> | ||
<li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial/Red_light_sensor">red sensor</a></li> | <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial/Red_light_sensor">red sensor</a></li> | ||
Line 64: | Line 64: | ||
<li><a href="https://2010.igem.org/Team:Edinburgh/BioBricks#Bacterial">submitted parts</a></li> | <li><a href="https://2010.igem.org/Team:Edinburgh/BioBricks#Bacterial">submitted parts</a></li> | ||
<li><a href="https://2010.igem.org/Team:Edinburgh/Results#Bacterial">results</a></li> | <li><a href="https://2010.igem.org/Team:Edinburgh/Results#Bacterial">results</a></li> | ||
- | <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial/Future">future | + | <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial/Future">the future</a></li> |
<li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial/References">references</a></li> | <li><a href="https://2010.igem.org/Team:Edinburgh/Bacterial/References">references</a></li> | ||
</ul> | </ul> | ||
Line 77: | Line 77: | ||
<li><a href="https://2010.igem.org/Team:Edinburgh/Modelling/Tools">tools</a></li> | <li><a href="https://2010.igem.org/Team:Edinburgh/Modelling/Tools">tools</a></li> | ||
<li><a href="https://2010.igem.org/Team:Edinburgh/Results#Modelling">results</a></li> | <li><a href="https://2010.igem.org/Team:Edinburgh/Results#Modelling">results</a></li> | ||
- | <li><a href="https://2010.igem.org/Team:Edinburgh/Modelling/Future">future | + | <li><a href="https://2010.igem.org/Team:Edinburgh/Modelling/Future">the future</a></li> |
<li><a href="https://2010.igem.org/Team:Edinburgh/Modelling/References">references</a></li> | <li><a href="https://2010.igem.org/Team:Edinburgh/Modelling/References">references</a></li> | ||
</ul> | </ul> | ||
Line 84: | Line 84: | ||
<li><a href="https://2010.igem.org/Team:Edinburgh/Human" class="dir">human BRIDGEs</a> | <li><a href="https://2010.igem.org/Team:Edinburgh/Human" class="dir">human BRIDGEs</a> | ||
<ul> | <ul> | ||
- | |||
<li><a href="https://2010.igem.org/Team:Edinburgh/Human/Communication">communication of science</a></li> | <li><a href="https://2010.igem.org/Team:Edinburgh/Human/Communication">communication of science</a></li> | ||
- | <li><a href="https://2010.igem.org/Team:Edinburgh/Human/ | + | <li><a href="https://2010.igem.org/Team:Edinburgh/Human/Branding">iGEM survey</a></li> |
- | + | ||
<li><a href="https://2010.igem.org/Team:Edinburgh/Human/Conversations">conversations</a></li> | <li><a href="https://2010.igem.org/Team:Edinburgh/Human/Conversations">conversations</a></li> | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
<li><a href="https://2010.igem.org/Team:Edinburgh/Human/Epic">the epic</a></li> | <li><a href="https://2010.igem.org/Team:Edinburgh/Human/Epic">the epic</a></li> | ||
- | <li><a href="https://2010.igem.org/Team:Edinburgh/ | + | <li><a href="https://2010.igem.org/Team:Edinburgh/Human/FutureApps">future applications</a></li> |
- | <li><a href="https://2010.igem.org/Team:Edinburgh/Human | + | <li><a href="https://2010.igem.org/Team:Edinburgh/Results#Human">further thoughts</a></li> |
<li><a href="https://2010.igem.org/Team:Edinburgh/Human/References">references</a></li> | <li><a href="https://2010.igem.org/Team:Edinburgh/Human/References">references</a></li> | ||
</ul> | </ul> | ||
Line 137: | Line 129: | ||
<br> | <br> | ||
- | <p>What if synthetic biologists were able to utilise an efficient two-step recombination method for markerless gene insertion and deletion? In 2008, Wei Sun, Shifeng Wang, and Roy Curtiss III of Arizona State University published such a protocol, based on the lambda red recombinase system (a simple method for disrupting chromosomal genes in bacteria such as <i>E. coli</i> using PCR products). The 2010 University of Edinburgh iGEM team has adapted their method to take advantage of the reusability of BioBricks, such that biologists can target critical areas of the <i>E. coli</i> genome with even greater efficiency.</p> | + | <p>Plasmid transformation <b>protocols</b> are the <b>backbone</b> of modern day synthetic biology, allowing for bacteria such as <i>E. coli</i> to take up foreign genetic material and express it as part of their cellular mechanisms. However, since only a relatively low number of cells are actually transformed in the process, selection markers are necessary to <b>identify</b> the cells that have acquired the plasmid; this usually takes the form of an antibiotic resistance gene built into the plasmid, which has the <b>undesired</b> effect of giving the transformed cells resistance to commonly-used antibiotics.</p> |
+ | |||
+ | <p>What if synthetic biologists were able to <b>utilise</b> an efficient two-step recombination method for markerless gene insertion and deletion? In 2008, Wei Sun, Shifeng Wang, and Roy Curtiss III of Arizona State University <b>published</b> such a protocol, based on the lambda red recombinase system (a simple method for disrupting chromosomal genes in bacteria such as <i>E. coli</i> using PCR products). The 2010 University of Edinburgh iGEM team has <b>adapted</b> their method to take advantage of the reusability of BioBricks, such that synthetic biologists can <b>target</b> critical areas of the <i>E. coli</i> genome with even greater efficiency.</p> | ||
- | <p>BRIDGE stands for BioBrick Recombination In Direct Genomic Editing. It is an alternative method for inserting BioBricks into the genome by using homologous recombination instead of restriction digestion, with the added bonus of not leaving a marker behind in the product.</p><br> | + | <p><b>BRIDGE</b> stands for BioBrick Recombination In Direct Genomic Editing. It is an alternative <b>method</b> for inserting BioBricks into the genome by using homologous recombination instead of restriction digestion, with the added <b>bonus</b> of not leaving a marker behind in the product.</p><br> |
<br> | <br> | ||
Line 145: | Line 139: | ||
<br> | <br> | ||
- | <p>Our BRIDGE construct | + | <p>Our BRIDGE construct contains two selection markers in order to <b>successfully</b> complete the protocol (described in greater detail <a href="https://2010.igem.org/Team:Edinburgh/Project/Protocol">here</a>): <i>cat</i>, which confers chloramphenicol resistance, and <i>sacB</i>, which is toxic when the host is grown on sucrose. Both the construct and the desired gene are inserted by homologous recombination using the lambda red recombinase system. For this we <b>require</b> up- and down-stream sequences of the genes that we wish to replace.</p> |
- | <p>To prove the principle of BRIDGE we | + | <p>To <b>prove</b> the principle of BRIDGE we removed a non-essential, constitutively expressed gene from the <i>E. coli</i> genome and replaced it with a well-known marker, GFP. This could have been <b>extended</b> further: we also had several genes from a past project idea which we could delete to increase fatty acid synthesis, and other genes we could introduce which would result in the production of long chain alkenes from the excess fatty acids. This is not <b>useful</b> for our current project but it would be a nice way to demonstrate the effectiveness of BRIDGE.</p> |
- | <p>Eventually, we | + | <p>Eventually, we hoped that BRIDGE could be used to introduce whole light producer-sensor constructs, to <b>demonstrate</b> its ability for utilisation in further work using BioBricks.</p><br> |
<br> | <br> | ||
Line 165: | Line 159: | ||
</li> | </li> | ||
<li> | <li> | ||
- | <a href="https://2010.igem.org/Team:Edinburgh/ | + | <a href="https://2010.igem.org/Team:Edinburgh/Project/Future">Our vision of the future of the BRIDGE protocol, and where we would like to go next.</a> |
</li> | </li> | ||
<li> | <li> | ||
- | <a href="https://2010.igem.org/Team:Edinburgh/ | + | <a href="https://2010.igem.org/Team:Edinburgh/Project/References">References used throughout the section.</a><br> |
</li> | </li> | ||
</ul> | </ul> |
Latest revision as of 02:14, 28 October 2010
Genomic BRIDGEs
Plasmid transformation protocols are the backbone of modern day synthetic biology, allowing for bacteria such as E. coli to take up foreign genetic material and express it as part of their cellular mechanisms. However, since only a relatively low number of cells are actually transformed in the process, selection markers are necessary to identify the cells that have acquired the plasmid; this usually takes the form of an antibiotic resistance gene built into the plasmid, which has the undesired effect of giving the transformed cells resistance to commonly-used antibiotics.
What if synthetic biologists were able to utilise an efficient two-step recombination method for markerless gene insertion and deletion? In 2008, Wei Sun, Shifeng Wang, and Roy Curtiss III of Arizona State University published such a protocol, based on the lambda red recombinase system (a simple method for disrupting chromosomal genes in bacteria such as E. coli using PCR products). The 2010 University of Edinburgh iGEM team has adapted their method to take advantage of the reusability of BioBricks, such that synthetic biologists can target critical areas of the E. coli genome with even greater efficiency.
BRIDGE stands for BioBrick Recombination In Direct Genomic Editing. It is an alternative method for inserting BioBricks into the genome by using homologous recombination instead of restriction digestion, with the added bonus of not leaving a marker behind in the product.
Our Project
Our BRIDGE construct contains two selection markers in order to successfully complete the protocol (described in greater detail here): cat, which confers chloramphenicol resistance, and sacB, which is toxic when the host is grown on sucrose. Both the construct and the desired gene are inserted by homologous recombination using the lambda red recombinase system. For this we require up- and down-stream sequences of the genes that we wish to replace.
To prove the principle of BRIDGE we removed a non-essential, constitutively expressed gene from the E. coli genome and replaced it with a well-known marker, GFP. This could have been extended further: we also had several genes from a past project idea which we could delete to increase fatty acid synthesis, and other genes we could introduce which would result in the production of long chain alkenes from the excess fatty acids. This is not useful for our current project but it would be a nice way to demonstrate the effectiveness of BRIDGE.
Eventually, we hoped that BRIDGE could be used to introduce whole light producer-sensor constructs, to demonstrate its ability for utilisation in further work using BioBricks.
Table of Contents
- The protocol proper, explaining the technical details of BRIDGE.
- The BioBricks we submitted as part of developing the BRIDGE protocol.
- A summary of what we achieved developing the BRIDGE protocol.
- Our vision of the future of the BRIDGE protocol, and where we would like to go next.
-
References used throughout the section.