Team:Queens Canada/Guide/DNA

From 2012.igem.org

(Difference between revisions)
 
(35 intermediate revisions not shown)
Line 1: Line 1:
{{:Template:Queens_Canada/Header}}
{{:Template:Queens_Canada/Header}}
<html>
<html>
 +
<head>
 +
<style type="text/css">
 +
.contentbox
 +
{
 +
padding-left: 30px;
 +
padding-right:30px;
 +
border-bottom: 1px dashed black;
 +
}
 +
.contenttitle
 +
{
 +
font-size: 2em;
 +
padding-left: 20px;
 +
padding-top: 10px;
 +
padding-bottom: 10px;
 +
 +
}
 +
</style>
 +
</head>
<body>
<body>
<script>  
<script>  
Line 9: Line 27:
<div id="labcontent">
<div id="labcontent">
<div id="NotebookTitle">
<div id="NotebookTitle">
-
<p>ChimeriQ - Description</p>
+
<p>DNA</p>
</div>
</div>
<div id="notebookmenu1" style="border-bottom: 1px solid black">
<div id="notebookmenu1" style="border-bottom: 1px solid black">
Line 15: Line 33:
   
   
<li> <a href="#Cut-sites"> Cut-sites </a> </li>
<li> <a href="#Cut-sites"> Cut-sites </a> </li>
 +
<li> <a href="#Bio_Fus"> Biobrick Fusion Standards</a> </li>
<li> <a href="#Cloning_methods"> Cloning methods</a> </li>
<li> <a href="#Cloning_methods"> Cloning methods</a> </li>
<li> <a href="#expression"> Parts for protein expression</a>  </li>
<li> <a href="#expression"> Parts for protein expression</a>  </li>
-
<li> <a href="#Other">Other</a> </li>
+
 
</ul>
</ul>
Line 29: Line 48:
Cut Sites
Cut Sites
</div>
</div>
-
<div id="contentbox">
+
<div class="contentbox">
-
PUT STUFF HERE!
+
Restriction Enzyme Cut sites are an essential element for creating protein chimers of any kind, not only for the creation of BioBrick Protein Chimers. As part of the protocol for creating these protein chimers, digestion and ligation will be involved. More often than not, digestion sites for restriction enzymes will be incorporated to the ends of the insert and the adjacent parts in order to ligate them together and into a plasmid. Therefore, it is critical to ensure that there are no cut sites present for the restriction enzymes that you will be using for digestion and ligation, otherwise it will be very difficult to get the full part ligated together with themselves and into the plasmid. For instance, if there is an EcoRI cut site present in the insert, then while you are digesting with the insert with EcoRI, the insert will be cut prematurely, and its function will likely be reduced.
 +
Removing restriction enzyme cut sites can be a very simple, or a very difficult process, depending on the location of the cut site in the desired part. If the part is close to the beginning or the end of the desired part, it may be simple to do a site directed mutagenesis. In order to do so, you would need to create a primer that overlaps the desired cut site, and change one nucleotide (preferably one that causes a silent mutation in the protein), such that the primer will still anneal to the template DNA, but will induce a single base pair nucleotide change that will remove the cut site from the PCR product. While the former is a very simple process, if the cut site is far enough away from the ends of the template DNA, this process is unlikely to work, as the primers will be too long. In this case, the simplest way to remove the cut site will be to have the DNA directly synthesized, although this can end up being a very costly process.
 +
<br>
 +
</br>
 +
Below are the Restriction Enzyme cut sites for various BioBrick standards
 +
<br>
 +
</br>
 +
<table style="vertical-align: text-top;">
 +
<td width="25%" text-align="center">
 +
BB RFC [10]
 +
<ul>
 +
<li>EcoRI site: GAATTC </li>
 +
<li>XbaI site: TCTAGA </li>
 +
<li>SpeI site: ACTAGT </li>
 +
<li>PstI site: CTGCAG </li>
 +
<li>NotI site: GCGGCCGC </li>
 +
</ul>
 +
</td>
 +
<td width="25%" text-align="center">
 +
BioBrick BB-2 RFC[12]
 +
<ul>
 +
<li>EcoRI site: GAATTC </li>
 +
<li>SpeI site: ACTAGT </li>
 +
<li>NheI site, GCTAGC </li>
 +
<li>PstI site: CTGCAG </li>
 +
<li>NotI site: GCGGCCGC </li>
 +
 
 +
</ul>
 +
</td>
 +
 
 +
<td width="25%" valign="top" text-align="center">
 +
Berkeley RFC[21]
 +
<ul>
 +
<li>EcoRI site: GAATTC </li>
 +
<li>BglII site: AGATCT </li>
 +
<li>BamHI site: GGATCC </li>
 +
<li>XhoI site: CTCGAG </li>
 +
</ul>
 +
</td>
 +
<td width="25%" text-align="center">
 +
Silver RFC[23]
 +
<ul>
 +
<li>EcoRI site: GAATTC </li>
 +
<li>XbaI site: TCTAGA </li>
 +
<li>SpeI site: ACTAGT </li>
 +
<li>PstI site: CTGCAG </li>
 +
<li>NotI site: GCGGCCGC </li>
 +
</ul>
 +
</table>
 +
 
 +
 
</div>
</div>
<div id="Cloning_methods" class="contenttitle">
<div id="Cloning_methods" class="contenttitle">
Cloning Methods
Cloning Methods
</div>
</div>
-
<div id="contentbox">
+
<div class="contentbox">
 +
<h3>PCR Overlap Extension</h3>
<p>When cloning parts into our construct, we chose to use PCR overlap extension and digestion/ligation
<p>When cloning parts into our construct, we chose to use PCR overlap extension and digestion/ligation
techniques. In order to perform PCR Overlap extension (our preferred method of cloning) we were
techniques. In order to perform PCR Overlap extension (our preferred method of cloning) we were
Line 41: Line 111:
to add overlap sites that match those of the parts we were adding. This allowed for PCR to extend
to add overlap sites that match those of the parts we were adding. This allowed for PCR to extend
the part onto another part with a matching overlap site; with the primers on either end of the inserts
the part onto another part with a matching overlap site; with the primers on either end of the inserts
-
acting as the site of initiation for Taq polymerase. Our primary resource was this <a href="http://www.biotechniques.com/BiotechniquesJournal/2010/June/Overlap-extension-PCR-cloning-a-simple-and-reliable-way-to-create-recombinant-plasmids/biotechniques-280116.html">paper</a>. A picture
+
acting as the site of initiation for Taq polymerase. Our primary resource was this <a href=http://www.biotechniques.com/BiotechniquesJournal/2010/June/Overlap-extension-PCR-cloning-a-simple-and-reliable-way-to-create-recombinant-plasmids/biotechniques-280116.html>paper</a>. A picture
representation of PCR-Overlap Extension can be seen below:</p>
representation of PCR-Overlap Extension can be seen below:</p>
-
<img src="">PCROE</img>
+
<img src="https://static.igem.org/mediawiki/2012/thumb/b/ba/Pcroe.png/800px-Pcroe.png"></img>
 +
 
 +
<h3>High Throughput Cloning</h3>
 +
<p>The protocol for this method is standard.</p>
 +
98C for 30s<br>
 +
60C for 30s<br>
 +
72C for 1.5/kb<br>
 +
- 18 cycles optimum<br>
 +
72C for 10min (final extension)<br>
 +
37C for 30min - Add Dpn1 (digest methylated DNA)<br>
 +
Tranform<br>
 +
<p>
 +
The choice of polyemerase is important! The article suggests using Phusion DNA Polymerase for the best results. We used Kapa Hi-Fi Hotsart Mix and confirm that it worked. The reference includes data for other polymerases as well.</p>
 +
Obtained from the following reference, under the Supplementary Material:<br>
 +
<a href="http://www.biotechniques.com/BiotechniquesJournal/2010/June/Overlap-extension-PCR-cloning-a-simple-and-reliable-way-to-create-recombinant-plasmids/biotechniques-280116.html">LINK</a> Anton V. Bryksin and Ichiro Matsumura. (2010) Overlap extension PCR cloning: a simple and reliable way to create recombinant plasmids. BioTechniques, Vol. 48, No. 6, pp. 463–465<br>
 +
 
 +
<p>Because this method is standard over all of our parts, we can use it for high throughput cloning. For example, if we had 96 parts in our standard, we can fill a 96 well PCR plate and run this program, digest with Dpn1, then transform all of these parts. This would about 3-4 hours, with the main amount of time being the PCR reaction. So in the case of chimeric protein design, if we wanted to screen a number of cloned structures configurations to find one that folded the way we wanted it to, we could use this method to rapidly clone and test a series of trials.</p>
 +
<p>We can liken this to crystallography, which can be done at high throughput by robots.</p>
 +
<p><b>An RFC is in the process of being submitted for this standard.</b></p>
 +
 
 +
<h3>Standard Cloning</h3>
<p>The other method of cloning made use of the cut sites found in our insert and a few restriction enzymes.
<p>The other method of cloning made use of the cut sites found in our insert and a few restriction enzymes.
Early on we noted the BioBrick standard caused a very problematic frame-shifts within the scar when
Early on we noted the BioBrick standard caused a very problematic frame-shifts within the scar when
Line 52: Line 142:
<p>Therefore we started doing research into other assembly standards to see if any of them alleviated
<p>Therefore we started doing research into other assembly standards to see if any of them alleviated
the problem. We judged the merits and flaws of each one (a list of the assembly standards considered
the problem. We judged the merits and flaws of each one (a list of the assembly standards considered
-
can be found <a href="http://openwetware.org/wiki/The_BioBricks_Foundation:Standards/Technical/Formats">here</a>). What we searched for was a standard that would avoid frame-shifts and nonsense
+
can be found <a href=http://openwetware.org/wiki/The_BioBricks_Foundation:Standards/Technical/Formats>here</a>). What we searched for was a standard that would avoid frame-shifts and nonsense
mutations when doing protein fusion, avoid N-terminal destabilization signals and dam methylation sites
mutations when doing protein fusion, avoid N-terminal destabilization signals and dam methylation sites
and preserve most of the restriction enzymes from the original BBa standard.</p>
and preserve most of the restriction enzymes from the original BBa standard.</p>
Line 75: Line 165:
so, we would have made zinc fingers to bind DNA and combined them with enzymes capable of cutting
so, we would have made zinc fingers to bind DNA and combined them with enzymes capable of cutting
away from the binding site. This would allow us to cut as close to the gene as possible.</p>
away from the binding site. This would allow us to cut as close to the gene as possible.</p>
 +
<br>
 +
</br>
</div>
</div>
 +
<div id="Bio_Fus" class="contenttitle">
 +
Biobrick Fusion Standards
 +
</div>
 +
<div class="contentbox">
 +
<p>When designing our flagella construct we examined a number of different ways of creating fusion proteins. Using the original BioBrick assembly standard does not work for fusion proteins, as it results in a frame shift and stop codon in the scar. At first we worked on creating a new method of fusion protein production, however we ran into many of the same problems as the standards that were already present. We went through the various fusion standards present on the openwetware web page, analyzing their different merits, eventually settling on Tom Knight’s BB-2 standard. You can follow this <a href=http://openwetware.org/wiki/The_BioBricks_Foundation:Standards/Technical/Formats>link</a> for some information on the various standards we examined.</p>
 +
<h3>Biofusion (Silver Lab)</h3>
 +
<div id="seqbox">
 +
<pre>
 +
  Prefix                         Suffix
 +
5’ GAATTC GCGGCCGC T TCTAGA ...part... ACTAGT A GCGGCCG CTGCAG 3’
 +
  EcoRI  NotI        XbaI         SpeI    NotI    PstI
 +
 +
This results in the following scar:
 +
 +
5’ ...part A...ACTAGA...part B...3’
 +
              ThrArg
 +
</pre>
 +
<p>The Biofusion standard slightly adjusted the original BioBrick standard such that the scar would now code for arginine instead of a stop codon, and the fusion would be in frame. Also, this standard uses the same enzymes as the original, so no new enzymes must be purchased. However, some issues do arise.These include the fact that the arginine present in the scar may be problematic in some cases due to its large size and the fact that it is coded by a rare codon. Also, Dam methylation may block cloning if the fused protein begins with Serine.</p>
 +
</div>
 +
<h3>Fusion Parts (Freiburg iGEM 2007)</h3>
 +
<div id="seqbox">
 +
<pre>
 +
Prefix             Suffix
 +
5' GAATTC GCGGCCGC T TCTAGA TG GCCGGC...part...ACCGGT TAAT ACTAGT A GCGGCCG CTGCAG 3'
 +
  EcoRI    NotI      XbaI  Met NgoMI          AgeI        SpeI    NotI    PstI
 +
 +
This results in the following scar:
 +
 +
5’ ...part A...ACCGGC...part B... 3’
 +
      ThrGly
 +
</pre>
 +
<p>The Fusion Parts standard proposed by Freiburg serves to allow fusion proteins but remove some of the disadvantages of the Biofusion standard. It does this by adding two new restriction enzymes: NgoMI and AgeI. This standard allows a less disruptive scar of threonine and glycine, while maintaining in frame fusions. However, this does require the purchase of two new restriction enzymes.</p>
 +
</div>
 +
<h3>BglBricks (Berkeley)</h3>
 +
<div id="seqbox">
 +
<pre>
 +
Prefix   Suffix
 +
5’ GAATTC ATG AGATCT...part...GGATCC TAA CTCGAG 3’
 +
  EcoRI      BglII          BamHI      XhoI
 +
 +
This results in the following scar:
 +
 +
5’ ...part A...GGATCT...part B...3’
 +
      GlySer
 +
</pre>
 +
<p>The BglBricks standard allows in frame production of fusion proteins with a benign scar of of glycine and serine. The prefix and suffix are also quite simple, containing only the 2 restriction sites connected by 3 bases. However, this method uses 3 new enzymes: BglII, BamHI and XhoI, of which BglII and BamHI cannot be heat-inactivated.</p>
 +
</div>
 +
<h3>BB-2 (Tom Knight)</h3>
 +
<div id="seqbox">
 +
<pre>
 +
Prefix         Suffix
 +
5’ GAATTC...ACTAGT...part...GCTAGC...CTGCAG 3’
 +
  EcoRI    SpeI            NheI    PstI
 +
 +
This results in the following scar:
 +
 +
5’...part A...GCTAGT...part B... 3’
 +
              AlaSer
 +
</pre>
 +
<p>The BB-2 standard proposed by Tom Knight was the method we ended up following to produce our chimeric flagella. This standard requires the addition of only one new restriction enzyme (NheI), and produces in frame fusions with a benign scar of alanine and serine. Also, the NheI cut site is fairly rare in E. coli, decreasing the likelihood of having cut sites within proteins, and this enzyme can be heat-inactivated. The main concern with this method is that it has not yet been tested extensively to prove its value as a standard method of Biobrick assembly.</p>
 +
<br>
 +
</br>
 +
</div>
 +
</div>
 +
<div id="expression" class="contenttitle">
<div id="expression" class="contenttitle">
Parts for protein expression
Parts for protein expression
</div>
</div>
-
<div id="contentbox">
+
<div class="contentbox">
-
PUT STUFF HERE
+
 
 +
<h3>Protein Expression</h3>
 +
<div>
 +
<p>As with any other gene sequences and parts, it was important to consider how to control the rate
 +
of expression for the protein, i.e. induce transcription of the insert and subsequent translation.
 +
Different promoter sequences are often incorporated upstream of the gene of interest to allow RNA
 +
polymerase a site to bind to in which to start transcription. Likewise ribosomal binding sites (RBS) are
 +
added downstream of the promoter to allow ribosomes to attach to the transcribe mRNA sequence.
 +
Depending on the promoter and RBS used, the level of expression for the protein can change anywhere
 +
from being produced in abundance or having little produced at all.</p>
 +
 
 +
<p>In our project we decided to use the <b>IPTG (Isopropyl β-D-1-thiogalactopyranoside) inducible promoter
 +
with RBS (Part:BBa J04500)</b>. The complex is made up of the LacI regulated promoter found naturally in
 +
E.coli and an rbs based off of a repressilator.</p>
</div>
</div>
-
<div id="Other" class="contenttitle">
+
 
-
Other
+
<h3>Promoter</h3>
 +
<div>
 +
<p>The promoter used is the natural promoter from the LacZYA operon. It contains two protein binding
 +
sites; the first is for the CAP protein which is found in E.coli and associated with cell health and glucose
 +
supply. The second site binds LacI protein which is expressed to inhibit expression of the Lac operon
 +
when no lactose is present. In the absence of the CAP protein and LacI, the promoter will increase
 +
transcription. However, the promoter is naturally constitutive (meaning that by default it is in an ON
 +
state) in E.coli strains that have low expression of LacI proteins (such as Top 10). Because of this fact
 +
and prior experience with the part, we decided to keep using this promoter. In theory (and most likely
 +
practice) any other constitutive promoter part would have sufficed for our project.</p>
 +
 
 +
<p>A crucial fact to note is that this part is incompatible in species containing active LacI coding regions
 +
and environments containing lactose and lactose analogs. The former reason is because active LacI
 +
expression will limit the efficiency of the promoter, the later because the presence of lactose would
 +
continuously activate the promoter. Therefore these factors were considered before adoption of this
 +
promoter.</p>
 +
<br>
 +
</br>
</div>
</div>
-
<div id="contentbox">
 
-
PUT STUFF HERE
 
</div>
</div>
 +
<script>  
<script>  

Latest revision as of 03:23, 27 October 2012
Control

DNA

Cut Sites
Restriction Enzyme Cut sites are an essential element for creating protein chimers of any kind, not only for the creation of BioBrick Protein Chimers. As part of the protocol for creating these protein chimers, digestion and ligation will be involved. More often than not, digestion sites for restriction enzymes will be incorporated to the ends of the insert and the adjacent parts in order to ligate them together and into a plasmid. Therefore, it is critical to ensure that there are no cut sites present for the restriction enzymes that you will be using for digestion and ligation, otherwise it will be very difficult to get the full part ligated together with themselves and into the plasmid. For instance, if there is an EcoRI cut site present in the insert, then while you are digesting with the insert with EcoRI, the insert will be cut prematurely, and its function will likely be reduced. Removing restriction enzyme cut sites can be a very simple, or a very difficult process, depending on the location of the cut site in the desired part. If the part is close to the beginning or the end of the desired part, it may be simple to do a site directed mutagenesis. In order to do so, you would need to create a primer that overlaps the desired cut site, and change one nucleotide (preferably one that causes a silent mutation in the protein), such that the primer will still anneal to the template DNA, but will induce a single base pair nucleotide change that will remove the cut site from the PCR product. While the former is a very simple process, if the cut site is far enough away from the ends of the template DNA, this process is unlikely to work, as the primers will be too long. In this case, the simplest way to remove the cut site will be to have the DNA directly synthesized, although this can end up being a very costly process.

Below are the Restriction Enzyme cut sites for various BioBrick standards

BB RFC [10]
  • EcoRI site: GAATTC
  • XbaI site: TCTAGA
  • SpeI site: ACTAGT
  • PstI site: CTGCAG
  • NotI site: GCGGCCGC
BioBrick BB-2 RFC[12]
  • EcoRI site: GAATTC
  • SpeI site: ACTAGT
  • NheI site, GCTAGC
  • PstI site: CTGCAG
  • NotI site: GCGGCCGC
Berkeley RFC[21]
  • EcoRI site: GAATTC
  • BglII site: AGATCT
  • BamHI site: GGATCC
  • XhoI site: CTCGAG
Silver RFC[23]
  • EcoRI site: GAATTC
  • XbaI site: TCTAGA
  • SpeI site: ACTAGT
  • PstI site: CTGCAG
  • NotI site: GCGGCCGC
 
Cloning Methods

PCR Overlap Extension

When cloning parts into our construct, we chose to use PCR overlap extension and digestion/ligation techniques. In order to perform PCR Overlap extension (our preferred method of cloning) we were required to fabricate a set of primers that were ligated onto the insert. These primer extensions served to add overlap sites that match those of the parts we were adding. This allowed for PCR to extend the part onto another part with a matching overlap site; with the primers on either end of the inserts acting as the site of initiation for Taq polymerase. Our primary resource was this paper. A picture representation of PCR-Overlap Extension can be seen below:

High Throughput Cloning

The protocol for this method is standard.

98C for 30s
60C for 30s
72C for 1.5/kb
- 18 cycles optimum
72C for 10min (final extension)
37C for 30min - Add Dpn1 (digest methylated DNA)
Tranform

The choice of polyemerase is important! The article suggests using Phusion DNA Polymerase for the best results. We used Kapa Hi-Fi Hotsart Mix and confirm that it worked. The reference includes data for other polymerases as well.

Obtained from the following reference, under the Supplementary Material:
LINK Anton V. Bryksin and Ichiro Matsumura. (2010) Overlap extension PCR cloning: a simple and reliable way to create recombinant plasmids. BioTechniques, Vol. 48, No. 6, pp. 463–465

Because this method is standard over all of our parts, we can use it for high throughput cloning. For example, if we had 96 parts in our standard, we can fill a 96 well PCR plate and run this program, digest with Dpn1, then transform all of these parts. This would about 3-4 hours, with the main amount of time being the PCR reaction. So in the case of chimeric protein design, if we wanted to screen a number of cloned structures configurations to find one that folded the way we wanted it to, we could use this method to rapidly clone and test a series of trials.

We can liken this to crystallography, which can be done at high throughput by robots.

An RFC is in the process of being submitted for this standard.

Standard Cloning

The other method of cloning made use of the cut sites found in our insert and a few restriction enzymes. Early on we noted the BioBrick standard caused a very problematic frame-shifts within the scar when ligating 2 or more parts. We tried to circumvent the problem by adding 1 or 2 nucleotides onto our DNA sequence to fix the frame but found this to be tedious due to the fact that this varied based on the part we wanted to ligate.

Therefore we started doing research into other assembly standards to see if any of them alleviated the problem. We judged the merits and flaws of each one (a list of the assembly standards considered can be found here). What we searched for was a standard that would avoid frame-shifts and nonsense mutations when doing protein fusion, avoid N-terminal destabilization signals and dam methylation sites and preserve most of the restriction enzymes from the original BBa standard.

Considering these reasons, we chose to switch our prefixes and suffixes to Tom Knight’s BBa 2 standard that allowed seamless in-frame ligations between multiple sequences of successive DNA. This change resulted in only 1 restriction enzyme (Xba1 to Nhe1) that differed from original BBa standard therefore providing the flexibility we needed to simultaneously work with both standards. For ligation, we used T4 ligase. A pictorial representation of the BBa 2 standard can be seen below:

      Prefix                      Suffix
    EcoRI    SpeI              NheI     PstI
5' GAATTC...ACTAGT ...part... GCTAGC...CTGCAG 3'

Fusing two parts would then leave the following scar:
5' ...part A... GCTAGT ...part B... 3'
                A  S

We also considered making our own artificial restriction enzymes in order to cut DNA off-site. To do so, we would have made zinc fingers to bind DNA and combined them with enzymes capable of cutting away from the binding site. This would allow us to cut as close to the gene as possible.



Biobrick Fusion Standards

When designing our flagella construct we examined a number of different ways of creating fusion proteins. Using the original BioBrick assembly standard does not work for fusion proteins, as it results in a frame shift and stop codon in the scar. At first we worked on creating a new method of fusion protein production, however we ran into many of the same problems as the standards that were already present. We went through the various fusion standards present on the openwetware web page, analyzing their different merits, eventually settling on Tom Knight’s BB-2 standard. You can follow this link for some information on the various standards we examined.

Biofusion (Silver Lab)

	  Prefix	                        Suffix
5’ GAATTC GCGGCCGC T TCTAGA ...part... ACTAGT A GCGGCCG CTGCAG 3’
   EcoRI  NotI        XbaI	        SpeI     NotI    PstI

This results in the following scar:

5’ ...part A...ACTAGA...part B...3’
               ThrArg

The Biofusion standard slightly adjusted the original BioBrick standard such that the scar would now code for arginine instead of a stop codon, and the fusion would be in frame. Also, this standard uses the same enzymes as the original, so no new enzymes must be purchased. However, some issues do arise.These include the fact that the arginine present in the scar may be problematic in some cases due to its large size and the fact that it is coded by a rare codon. Also, Dam methylation may block cloning if the fused protein begins with Serine.

Fusion Parts (Freiburg iGEM 2007)

		 Prefix				            Suffix
5' GAATTC GCGGCCGC T TCTAGA TG GCCGGC...part...ACCGGT TAAT ACTAGT A GCGGCCG CTGCAG 3'
   EcoRI    NotI      XbaI  Met NgoMI           AgeI        SpeI     NotI    PstI

This results in the following scar:

5’ ...part A...ACCGGC...part B... 3’
	       ThrGly

The Fusion Parts standard proposed by Freiburg serves to allow fusion proteins but remove some of the disadvantages of the Biofusion standard. It does this by adding two new restriction enzymes: NgoMI and AgeI. This standard allows a less disruptive scar of threonine and glycine, while maintaining in frame fusions. However, this does require the purchase of two new restriction enzymes.

BglBricks (Berkeley)

	 Prefix			   Suffix
5’ GAATTC ATG AGATCT...part...GGATCC TAA CTCGAG 3’
   EcoRI      BglII           BamHI      XhoI

This results in the following scar:

5’ ...part A...GGATCT...part B...3’
	       GlySer

The BglBricks standard allows in frame production of fusion proteins with a benign scar of of glycine and serine. The prefix and suffix are also quite simple, containing only the 2 restriction sites connected by 3 bases. However, this method uses 3 new enzymes: BglII, BamHI and XhoI, of which BglII and BamHI cannot be heat-inactivated.

BB-2 (Tom Knight)

	Prefix		         Suffix
5’ GAATTC...ACTAGT...part...GCTAGC...CTGCAG 3’
   EcoRI     SpeI            NheI     PstI

This results in the following scar:

5’...part A...GCTAGT...part B... 3’
              AlaSer

The BB-2 standard proposed by Tom Knight was the method we ended up following to produce our chimeric flagella. This standard requires the addition of only one new restriction enzyme (NheI), and produces in frame fusions with a benign scar of alanine and serine. Also, the NheI cut site is fairly rare in E. coli, decreasing the likelihood of having cut sites within proteins, and this enzyme can be heat-inactivated. The main concern with this method is that it has not yet been tested extensively to prove its value as a standard method of Biobrick assembly.



Parts for protein expression

Protein Expression

As with any other gene sequences and parts, it was important to consider how to control the rate of expression for the protein, i.e. induce transcription of the insert and subsequent translation. Different promoter sequences are often incorporated upstream of the gene of interest to allow RNA polymerase a site to bind to in which to start transcription. Likewise ribosomal binding sites (RBS) are added downstream of the promoter to allow ribosomes to attach to the transcribe mRNA sequence. Depending on the promoter and RBS used, the level of expression for the protein can change anywhere from being produced in abundance or having little produced at all.

In our project we decided to use the IPTG (Isopropyl β-D-1-thiogalactopyranoside) inducible promoter with RBS (Part:BBa J04500). The complex is made up of the LacI regulated promoter found naturally in E.coli and an rbs based off of a repressilator.

Promoter

The promoter used is the natural promoter from the LacZYA operon. It contains two protein binding sites; the first is for the CAP protein which is found in E.coli and associated with cell health and glucose supply. The second site binds LacI protein which is expressed to inhibit expression of the Lac operon when no lactose is present. In the absence of the CAP protein and LacI, the promoter will increase transcription. However, the promoter is naturally constitutive (meaning that by default it is in an ON state) in E.coli strains that have low expression of LacI proteins (such as Top 10). Because of this fact and prior experience with the part, we decided to keep using this promoter. In theory (and most likely practice) any other constitutive promoter part would have sufficed for our project.

A crucial fact to note is that this part is incompatible in species containing active LacI coding regions and environments containing lactose and lactose analogs. The former reason is because active LacI expression will limit the efficiency of the promoter, the later because the presence of lactose would continuously activate the promoter. Therefore these factors were considered before adoption of this promoter.



Retrieved from "http://2012.igem.org/Team:Queens_Canada/Guide/DNA"