Team:Johns Hopkins-Wetware/yeastgoldengate
From 2012.igem.org
Mrjiaruiwang (Talk | contribs) |
|||
(12 intermediate revisions not shown) | |||
Line 22: | Line 22: | ||
<li><a href="https://2012.igem.org/Team:Johns_Hopkins-Wetware/Project">At a Glance</a></li> | <li><a href="https://2012.igem.org/Team:Johns_Hopkins-Wetware/Project">At a Glance</a></li> | ||
<li><a href="https://2012.igem.org/Team:Johns_Hopkins-Wetware/etohproject">Ethanol control</a></li> | <li><a href="https://2012.igem.org/Team:Johns_Hopkins-Wetware/etohproject">Ethanol control</a></li> | ||
+ | <li><a href="https://2012.igem.org/Team:Johns_Hopkins-Wetware/etohproject#modelanchor">Modeling</a></li> | ||
<li><a href="https://2012.igem.org/Team:Johns_Hopkins-Wetware/lightproject">Optogenetic control</a></li> | <li><a href="https://2012.igem.org/Team:Johns_Hopkins-Wetware/lightproject">Optogenetic control</a></li> | ||
+ | |||
</ul> | </ul> | ||
</li> | </li> | ||
Line 31: | Line 33: | ||
</ul> | </ul> | ||
</li> | </li> | ||
- | <li><a href="https://2012.igem.org/Team:Johns_Hopkins-Wetware/yeastgoldengate">Golden Gate</a> | + | <li><a href="https://2012.igem.org/Team:Johns_Hopkins-Wetware/yeastgoldengate">Yeast Golden Gate</a> |
+ | <ul> | ||
+ | <li><a href="https://2012.igem.org/Team:Johns_Hopkins-Wetware/Parts">Parts</a></li> | ||
+ | <li><a href="https://2012.igem.org/Team:Johns_Hopkins-Wetware/yeastgoldengate">RFC88</a></li> | ||
+ | </ul> | ||
</li> | </li> | ||
<li><a href="https://2012.igem.org/Team:Johns_Hopkins-Wetware/humanpractice">human practice</a> | <li><a href="https://2012.igem.org/Team:Johns_Hopkins-Wetware/humanpractice">human practice</a> | ||
+ | <ul> | ||
+ | <li><a href="https://2012.igem.org/Team:Johns_Hopkins-Wetware/thepartscourselabmanual">Lab Manual</a></li> | ||
+ | </ul> | ||
<li><a href="https://2012.igem.org/Team:Johns_Hopkins-Wetware/Safety">safety</a> | <li><a href="https://2012.igem.org/Team:Johns_Hopkins-Wetware/Safety">safety</a> | ||
</li> | </li> | ||
+ | <li><a href="https://2012.igem.org/Team:Johns_Hopkins-Wetware/requirements">Medal Fulfillment</a></li> | ||
</ul> | </ul> | ||
</div> <!--end div header--> | </div> <!--end div header--> | ||
Line 44: | Line 54: | ||
<div class="content"> | <div class="content"> | ||
<p> | <p> | ||
- | Yeast Golden Gate (RFC88) describes a new standard for the assembly of basic <i>Saccharomyces cerevisiae</i> transcriptional units (TUs) consisting of a promoter/5'untranslated region (UTR), open reading frame (ORF), and 3'UTR/terminator. Here, "promoter" refers to both the promoter and the 5' UTR, which we currently define as a single part. Future iterations of this standard will incorporate subdivision of currently defined parts e.g. into promoter and 5' UTR. The standard makes use of the type IIS restriction enzyme BsaI to generate standardized and user-defined 'signature overhangs', thus enabling directional and seamless TU assembly. RFC88 is supported by the Yeast Standardized Collection of Parts for Expression (SCoPE), a repository of subcloned and sequence verified parts compatible with this assembly standard. The Yeast SCoPE is currently populated by a large number of <i>S. cerevisiae</i> promoters and terminators that facilitate expression and characterization of non-native ORFs. | + | Yeast Golden Gate (RFC88) describes a new standard for the assembly of basic <i>Saccharomyces cerevisiae</i> transcriptional units (TUs) consisting of a promoter/5'untranslated region (UTR), open reading frame (ORF), and 3'UTR/terminator. Here, "promoter" refers to both the promoter and the 5' UTR, which we currently define as a single part. Future iterations of this standard will incorporate subdivision of currently defined parts e.g. into promoter and 5' UTR. The standard makes use of the type IIS restriction enzyme BsaI to generate standardized and user-defined 'signature overhangs', thus enabling directional and seamless TU assembly. RFC88 is supported by the Yeast Standardized Collection of Parts for Expression (SCoPE), a repository of subcloned and sequence verified parts compatible with this assembly standard. The Yeast SCoPE is housed at Johns Hopkins University and is currently populated by a large number of <i>S. cerevisiae</i> promoters and terminators that facilitate expression and characterization of non-native ORFs. |
+ | <br> | ||
+ | <a href="https://static.igem.org/mediawiki/2012/3/3e/Jhuigem2012RFC88.pdf"><h3>Click for RFC88</h3></a> | ||
</p> | </p> | ||
</div> | </div> | ||
Line 54: | Line 66: | ||
<img src="https://static.igem.org/mediawiki/2012/1/11/Jhhigem2012Bsai-cutting.png" alt="BsaI Cutting" class="center"/> | <img src="https://static.igem.org/mediawiki/2012/1/11/Jhhigem2012Bsai-cutting.png" alt="BsaI Cutting" class="center"/> | ||
<figcaption class="center_align"> | <figcaption class="center_align"> | ||
- | The recognition | + | The recognition site of BsaI (red/orange text) is offset from its cleavage site at positions +1 and +5 (white text). A part flanked by BsaI sites oriented in this manner will be left with user defined, 5' 'signature overhangs' (turquoise) following BsaI digestion. |
</figcaption> | </figcaption> | ||
</figure> | </figure> | ||
Line 68: | Line 80: | ||
<img src="https://static.igem.org/mediawiki/2012/b/bc/Jhuigem2012Signature-overhangs-diagram.png" alt="Signature Overhangs, TU assembly" class="wrap left" width="550px"/> | <img src="https://static.igem.org/mediawiki/2012/b/bc/Jhuigem2012Signature-overhangs-diagram.png" alt="Signature Overhangs, TU assembly" class="wrap left" width="550px"/> | ||
<figcaption> | <figcaption> | ||
- | Signature overhangs and the assembly of a transcriptional unit in a one-pot digestion-ligation. | + | Signature overhangs and the directional assembly of a transcriptional unit in a one-pot digestion-ligation. |
</figcaption> | </figcaption> | ||
</figure> | </figure> | ||
Line 80: | Line 92: | ||
<div class="content"> | <div class="content"> | ||
<figure class="wrap right"> | <figure class="wrap right"> | ||
- | <img src="https://static.igem.org/mediawiki/2012/ | + | <img src="https://static.igem.org/mediawiki/2012/4/48/JHUiGEM2012One_pot_assembly_of_TU.png" alt="One pot assembly of TU" width="500px"/> |
<figcaption class="center"> | <figcaption class="center"> | ||
- | + | Yeast Golden Gate One-pot assembly of TU | |
</figcaption> | </figcaption> | ||
</figure> | </figure> | ||
<p> | <p> | ||
- | The assembly of a TU may be carried out by simultaneous digestion and ligation, referred to here as a one-pot reaction. Donor constructs, encoding the promoter, ORF, and terminator parts, are introduced into a single reaction vessel along with BsaI and T4 DNA ligase. Further included is an acceptor vector specifically designed to encode signature overhangs, exposed by BsaI digestion, that are compatible with the 5' and 3' ends of the promoter and terminator, respectively. The combination of digestion and ligation leads to essentially reversible digestion of BsaI sites except when components of the TU/acceptor vector ligate; in this instance the BsaI site is eliminated. Over time the reaction generates more and more of the desired product. We eliminate background of intact donor molecules entirely by (i) a 5 minute at 50°C BsaI digestion to linearize residual acceptor vector molecules and (ii) encoding a different drug resistance marker in the acceptor vector. Finally, the parent acceptor vector encodes RFP between the BsaI sites. The RFP gene in the acceptor vector yields red colonies such that assembly of the TU in place of RFP is readily identified visually. Successful ligation will result in white colonies whereas re-ligated acceptor vectors will retain the RFP and present as red colonies. In practice, due to the 5 minute 50°C step that follows the 37°C incubation, a condition in which BsaI is active and the ligase is not, the background of red colonies is driven below the limit of detection in most instances.Other easily screenable or visual markers may be substituted for RFP and similarly, other combinations of drug markers could be used instead of Kan and Amp. | + | The assembly of a TU may be carried out by simultaneous digestion and ligation, referred to here as a one-pot reaction. Donor constructs, encoding the promoter, ORF, and terminator parts, are introduced into a single reaction vessel along with BsaI and T4 DNA ligase. Further included is an acceptor vector specifically designed to encode signature overhangs, exposed by BsaI digestion, that are compatible with the 5' and 3' ends of the promoter and terminator, respectively. The combination of digestion and ligation leads to essentially reversible digestion of BsaI sites except when components of the TU/acceptor vector ligate; in this instance the BsaI site is eliminated. |
+ | </p> | ||
+ | <p> | ||
+ | Over time the reaction generates more and more of the desired product. We eliminate background of intact donor molecules entirely by (i) a 5 minute at 50°C BsaI digestion to linearize residual acceptor vector molecules and (ii) encoding a different drug resistance marker in the acceptor vector. Finally, the parent acceptor vector encodes RFP between the BsaI sites. The RFP gene in the acceptor vector yields red colonies such that assembly of the TU in place of RFP is readily identified visually. Successful ligation will result in white colonies whereas re-ligated acceptor vectors will retain the RFP and present as red colonies. In practice, due to the 5 minute 50°C step that follows the 37°C incubation, a condition in which BsaI is active and the ligase is not, the background of red colonies is driven below the limit of detection in most instances. Other easily screenable or visual markers may be substituted for RFP and similarly, other combinations of drug markers could be used instead of Kan and Amp. | ||
</p> | </p> | ||
</div> | </div> | ||
- | <div class=" | + | <div class="content_header2"> |
</div> | </div> | ||
</div> | </div> |