Difference between revisions of "Team:Freiburg/Testpage"

Line 2: Line 2:
 
{{Freiburg/Menubar}}
 
{{Freiburg/Menubar}}
  
 +
{{Freiburg/wiki_content_start}}
 
<html>
 
<html>
 
<style>
 
 
/* upwards navigation blob */
 
 
#upwards_blob{
 
    display: none;
 
}
 
 
 
/* min-width is chosen so the blob does just not interfere with the content box */
 
/* 1021 content_box-width + 46 blob-width + 20 scrollbar + some buffer space */
 
@media screen and (min-width: 1144px){
 
    #upwards_blob{
 
        transition: transform 0.5s ease;
 
        display: inline;
 
        position: absolute;
 
        top: 900px;
 
        right: 30px;
 
        z-index: 1000;
 
        transform: translateY(130px);
 
    }
 
}
 
 
</style>
 
 
<div id="upwards_blob"><a href="#globalWrapper"><img src="https://static.igem.org/mediawiki/2015/9/93/Freiburg_upwards_blob.png"></a></div>
 
 
 
 
<script type="text/javascript">
 
 
// The upwards-blob div is defined in Freiburg/CSS as its absolute position should be initialized on the top of the page
 
 
$(document).ready(function(){
 
  var $blob = $("#upwards_blob"),
 
      $window = $(window),
 
      $doc_heighttop = $(document).height() - $window.height();
 
 
  //console.log('windowwidth:'+$window.width());
 
  //console.log('windowheight:'+$window.height());
 
 
  $(window).scroll(function(event) {
 
      if ($window.width() > 1144) {
 
      // y is scroll progress (distance from top)
 
      // top is about bottomline of window
 
      var y = $(this).scrollTop(),
 
      top = $(this).scrollTop() + $window.height() -100;
 
      //console.log($(this).scrollTop()+'  doc_heighttop:'+$doc_heighttop+'        top:'+top);
 
 
      // use CSS transform to move button into view when user scrolls down
 
      if (y > 60 ) {
 
        //console.log('blob inside');
 
        $blob.css({"display":"inline", "transform": "translateY(0)"}); // = 30 px inside right
 
      }
 
 
      // move blob out of view when page is scrolled up again
 
      if (y <  60) {
 
        //console.log('blob outside');
 
        $blob.css({"transform": "translateY(130px)"}); // = 100 px outside
 
      }
 
        // define position of blob relative to page top, increases dynamically with scrolling
 
      $blob.css({"top": top });
 
 
    } else {
 
      $blob.css({"display": "none" }); // if page is too small, no blob is displayed
 
    }
 
  });
 
 
  $(window).resize(function(){
 
    if ($window.width() < 1144) {
 
      $blob.css({"display": "none" }); // if the user resizes the window when the blob is displayed
 
    }   
 
  });
 
});
 
 
</script>
 
 
 
 
 
<style>
 
<style>
 
/*========= BEGIN: style for navigation bar ==========*/
 
/*========= BEGIN: style for navigation bar ==========*/
#project {
+
#results {
     background: url(https://static.igem.org/mediawiki/2015/d/da/Freiburg_icon_project_active_yellow.png) no-repeat;
+
     background: url(https://static.igem.org/mediawiki/2015/2/2e/Freiburg_icon_results_active_yellow.png) no-repeat;
 
}
 
}
  
#project a {
+
#results a {
 
     color: #ecdc18;
 
     color: #ecdc18;
 
}
 
}
  
 
#runningchip {
 
#runningchip {
     left: 18.6%;
+
     left: 52%;
 
}
 
}
 
/*========= END: style for navigation bar ==========*/
 
/*========= END: style for navigation bar ==========*/
 
.horizontal_menu li {
 
    display: block;
 
    margin-top: 5px;
 
}
 
 
.biobrick_emphasize {
 
    font-size: 15pt;
 
}
 
 
/*===================BEGIN:Amazing Bubble Sidebar==========================*/
 
 
/*===================END:Amazing Bubble Sidebar==========================*/
 
 
</style>
 
</style>
 
<!-------------------- BEGIN:BUBBLE BAR -------------------
 
<div class="bubble_sidebar bubble1">
 
    <p>Human Practice</p>
 
</div>
 
 
<div class="bubble_sidebar bubble2">
 
    <p>Acknowledgements</p>
 
</div>
 
 
<div class="bubble_sidebar bubble3">
 
    <p>Main Results</p>
 
</div>
 
------------------ END:BUBBLE BAR -------------------->
 
 
  
  
<div class="content_box" style="margin-top:0">
+
<div class="content_box">
<h1 class="sectionedit1">DNA Engineering</h1>
+
  
<div class="floatbox left">  
+
<h1 style="text-align:right">Cell-Free Expression of Immobilized DNA</h1>
 
<p>
 
<p>
A protein array containing different antigens specific for distinct diseases is one of the main parts of the DiaCHIP. Manufacturing this array can be done by conventional <a class="wikilink1" href="https://2015.igem.org/Team:Freiburg/Project/Protein_Purification" title="ProtPur">protein expression</a> and spotting of the proteins on a specific surface by hand or via <a class="wikilink1" href="https://2015.igem.org/Team:Freiburg/Project/Cellfree_Expression" title="cell_free">cell-free expression</a>. Both systems are based on different expression backbones. Therefore, a lot of cloning was required to obtain all constructs.
+
An important advantage of the DiaCHIP is the possibility to ship and store information encoded by DNA. From a DNA template array protein arrays can be produced on demand. In order to obtain this template, DNA is fixed on a silicone slide forming one side of our microfluidic chamber. Making use of a cell-free expression system, the DNA can then be transcribed and translated into the respective proteins resulting in the final protein array. The coding sequence of the proteins is genetically fused to a tag allowing their binding to a specific surface on the opposite side of the chamber.  
<br>
+
To reduce this ambitious task to a minimum of effort, we elaborated a well-structured <a class="wikilink1" href="#detailed_cloning_anchor" title="Detailed_cloning">cloning strategy</a> including a self-designed <a class="wikilink1" href="#cloning_site_anchor" title="Cloning site">multiple cloning site</a>. The cloning site for these purposes was incorporated into the commercial expression vector pET22b+ resulting in <a class="wikilink1" href="#vector_design_anchor" title="vector_design">pET_iGEM</a>.  
+
 
</p>
 
</p>
</div>
 
  
<div class="floatbox right">
+
<h2>Successful binding of DNA to the Silicone Slide</h2>
<p>
+
We soon realized that protein expression is probably a problem many iGEM Teams around the world are facing during their projects. Therefore, we decided to improve the plasmid backbone <a class="media" href="http://parts.igem.org/Part:pSB6A1" target="_blank" title="pSB6A1">pSB6A1</a> for protein overexpression providing the Registry with <a  class="wikilink1" href="https://2015.igem.org/Team:Freiburg/Description" title=„pOP“>pOP</a>, an expression backbone suitable for iGEM standard cloning procedures.
+
<br>
+
To help future iGEM Teams with their decision, which cloning method to use, we compared and contrasted classical cloning and Gibson Assembly in a <a class="wikilink1" href="https://2015.igem.org/Team:Freiburg/Project/Classic_vs_Gibson" title="Review">short review</a>.
+
</p>
+
  
<div class="horizontal_menu">
+
<div class="image_box left">
<ul>
+
  <div class="thumb2 trien" style="width:300px">
    <li><a href="#cloning_site_anchor" title="Cloning site">1. Our Cloning Site</a></li>
+
    <li><a href="#vector_design_anchor" title="vector_design">2. Design of pET_iGEM</a></li>
+
    <li><a href="#detailed_cloning_anchor" title="Detailed_cloning">3. Detailed Cloning Strategy</a></li>
+
    <li><a href="https://2015.igem.org/Team:Freiburg/Description" title=„pOP“>4. pOP - Protein Expression Meets iGEM Standards</a></li>
+
    <li><a href="https://2015.igem.org/Team:Freiburg/Project/Classic_vs_Gibson" title="Review">5. Short Review on Cloning Methods</a></li>
+
</ul>
+
</div>
+
</div>
+
 
+
</div>
+
 
+
<span id="cloning_site_anchor" class="anchor"></span>
+
<div id="cloning_site" class="content_box">
+
  <h1>1. Our Cloning Site</h1>
+
<div class="floatbox left">
+
  <p>
+
The cloning site we developed enables the assembly of different antigens with a number of tags in a standardized manner making it simple for many people to work with. A first calculation based on the assumption of using about 15 antigens and four different tag systems resulted in a total of 120 constructs to be cloned. This underlines the need for a simplified cloning procedure.
+
        </p>
+
        <p>
+
We did not use one of the available iGEM standards as a new cloning site for several reasons.
+
        </p>
+
</div>
+
 
+
<div class="floatbox right"> 
+
        <p>
+
The RFCs are designed to enable serial assembly of various sequences, but the exchange of single parts at a later time point is not possible<sup><a class="fn_top" href="#fn__1" id="fnt__1" name="fnt__1">1)</a></sup>. In order to be able to exchange tags at the N-terminus as well as at the C-terminus, distinct restriction sites need to persist between the parts. Moreover, we first wanted to establish an expression cassette inserted between BioBrick pre- and suffix of the submission backbone <a class="urlextern" href="http://parts.igem.org/Part:pSB1C3" target="_blank" title="pSB1C3">pSB1C3</a>. Therefore, making use of an additional RFC was not possible.
+
  </p>
+
</div>
+
<div style="clear:both"></div>
+
 
+
 
+
 
+
<div class="flexbox">
+
  <div class="thumb2 trien" style="width:680px">
+
 
                   <div class="thumbinner">
 
                   <div class="thumbinner">
                       <a href="https://static.igem.org/mediawiki/2015/6/6c/150917_ownMCS_ls.png" class="lightbox_trigger">
+
                       <a href="https://static.igem.org/mediawiki/2015/2/2b/Freiburg_PDMS_with_PDITC.png" class="lightbox_trigger">
                       <img src="https://static.igem.org/mediawiki/2015/6/6c/150917_ownMCS_ls.png" width="600px">   
+
                       <img src="https://static.igem.org/mediawiki/2015/2/2b/Freiburg_PDMS_with_PDITC.png" width="250px">   
 
                         <div class="thumbcaption">
 
                         <div class="thumbcaption">
 
                       </a>
 
                       </a>
                           <p><strong> Figure 1: Self-designed cloning site.</strong> Our cloning site containing the restriction sites <i>Acc</i>65I, <i>Bam</i>HI, <i>Hind</i>III and <i>Afl</i>II, that are assembled in a way that facilitates exchange of tags without getting a frame-shift.</p>
+
                           <p><strong>Figure 1: Scheme of the APTES/PDITC surface.</strong> The PDMS surface is layered with PDITC. This enables the binding of the amino-labeled DNA.</p>
 
                       </div>
 
                       </div>
 
                 </div>
 
                 </div>
 
</div>
 
</div>
</div>
 
<div class="kommentar">
 
Die buchstaben von Restirktionsenzymen immer kursiv - sind abgekürzte Artnamen. Im Text hab ichs geändert, aber nicht in der Abbildung (ps1709)
 
 
</div>
 
</div>
  
 
+
<p>
 
+
The core component of the DiaCHIP is the microfluidic chamber composed of a glass slide for protein immobilization and a PDMS (polydimethylsiloxane) flow cell. The silicone PDMS needs to be activated to enable the generation of the DNA template array by binding of the respective sequences. <a href="https://2015.igem.org/Team:Freiburg/Project/Surface_Chemistry"target="_blank">Oxygen plasma</a> is used to first activate the surface of the PDMS slide. This allows to cover it with the silane APTES and finally apply the <a href="https://2015.igem.org/Team:Freiburg/Project/Surface_Chemistry"target="_blank">crosslinker PDITC</a>. The DNA sequence to be immobilized requires an amino group to be covalently immobilized on the PDITC surface. The structure of this surface is schematically visualized in figure 1. The same surface chemistry can be used to immobilize proteins unspecifically.
 
+
<div class="floatbox left">
+
  <p>
+
The basic idea was to have distinct restriction sites which can be used for the insertion of antigens, while others can be used for the exchange of tags. Finally, this resulted in a cloning site containing <i>Acc</i>65I, <i>Bam</i>HI, <i>Hind</i>III and <i>Afl</i>II restriction sites (figure 1). Using those sites for the assembly of different antigen-tag combinations will never result in a frameshift, if the coding sequence is in frame with the restriction sites flanking it.  
+
 
<br>
 
<br>
The restriction sites have been chosen according to the amino acids that result from the translation of their sequence. <i>Acc</i>65I (G/GTACC) and <i>Bam</i>HI (G/GATCC) are translated into glycine and either serine or threonine.
+
To obtain an expression cassette for GFP with such an amino group, the target sequence was amplified by PCR using an amino-labeled reverse primer. Additionally, the forward primer was labeled by the fluorescent dye Cy3 to enable visualization by fluorescence microscopy. Successful amplification of the target sequence was verified by agarose gel electrophoresis.
        </p>
+
</p>
</div>
+
 
+
<div class="floatbox right"> 
+
        <p>
+
Those are hydrophilic, soluble amino acids, which are commonly used in flexible linkers. The translation of <i>Hind</i>III (A/AGCTT) results in lysine and leucin. Especially lysine is highly hydrophobic, which is why some soluble amino acids should be used as a linker in front of a C-terminal tag. The last restriction site, <i>Afl</i>II (C/TTAAG), is also translated to leucin and lysine. This will not highly affect protein function or folding since these are the last translated codons. Anyways, in order to prevent rapid protein degradation according to the N-end-rule in bacteria<sup><a class="fn_top" href="#fn__2" id="fnt__2" name="fnt__2">2)</a></sup>, a few additional amino acids have been inserted between the <i>Afl</i>II site and the stop codon (TGA).
+
  </p>
+
</div>
+
<div style="clear:both"></div>
+
 
+
            <div class="footnotes">
+
            <div class="fn"><sup><a class="fn_bot" href="#fnt__1" id="fn__1" name="fn__1">1)</a></sup><a class="urlextern" href="http://dspace.mit.edu/handle/1721.1/21168" rel="nofollow" target="_Blank" title="http://dspace.mit.edu/handle/1721.1/21168">Knight T 2003. Idempotent Vector Design for Standard Assembly of BioBricks.</a></div>
+
            <div class="fn"><sup><a class="fn_bot" href="#fnt__2" id="fn__2" name="fn__2">2)</a></sup><a class="urlextern" href="http://www.sciencemag.org/content/254/5036/1374.long" rel="nofollow" target="_Blank" title="http://www.sciencemag.org/content/254/5036/1374.long">Tobias JW 1991. The N-end rule in bacteria. Science.</a></div>
+
            </div>
+
</div>
+
 
+
<!-- EDIT1 SECTION "Cloning site" [3-3437] -->
+
  
<span id="vector_design_anchor" class="anchor"></span>
 
<div id="vector_design" class="content_box">
 
  <h1>2. Design of pET_iGEM</h1>
 
  
 
<div class="image_box right">
 
<div class="image_box right">
  <div class="thumb2 trien" style="width:260px">
+
  <div class="thumb2 trien" style="width:300px">
 
                   <div class="thumbinner">
 
                   <div class="thumbinner">
                       <a href="https://static.igem.org/mediawiki/2015/a/a1/Freiburg_labjournal-cloning-pig15_001neu.jpg" class="lightbox_trigger">
+
                       <a href="https://static.igem.org/mediawiki/2015/thumb/f/f5/Freiburg_spotting_microarrayscanner.png/735px-Freiburg_spotting_microarrayscanner.png" class="lightbox_trigger">
                       <img src="https://static.igem.org/mediawiki/2015/a/a1/Freiburg_labjournal-cloning-pig15_001neu.jpg" width="250px">   
+
                       <img src="https://static.igem.org/mediawiki/2015/thumb/f/f5/Freiburg_spotting_microarrayscanner.png/735px-Freiburg_spotting_microarrayscanner.png" width="250px">   
 
                         <div class="thumbcaption">
 
                         <div class="thumbcaption">
 
                       </a>
 
                       </a>
                           <p><strong>Figure 2: pIG15_001.</strong> <a class="urlextern" href="http://parts.igem.org/Part:pSB1C3" target="_blank" title="pSB1C3">pSB1C3</a> backbone containing an altered cloning site in the middle of an expression cassette for improved assembly of protein coding sequences with different tags (N- or C-terminal), which avoids the formation of frameshifts. Important parts for overexpression of proteins in <i>E. coli</i> were added inside the RFC[10].</p>
+
                           <p><strong>Figure 2: Immobilization of DNA on a PDMS slide.</strong> A: Top view on the slide indicating the spotting pattern. B: Cy3 fluorescence indicating successful immobilization of amino-labeled DNA. As a negative control, Cy3- but not amino-labeled DNA was spotted.</p>
 
                       </div>
 
                       </div>
 
                 </div>
 
                 </div>
Line 241: Line 65:
  
 
<p>
 
<p>
    For protein expression, we designed two vectors based on the submission backbone <a class="urlextern" href="http://parts.igem.org/Part:pSB1C3" target="_blank" title="pSB1C3">pSB1C3</a>. pIG15_001 (figure 2) was supposed to be adapted for inducible protein overexpression in <i>E. coli</i>. Therefore, we inserted main features derived from the commercial expression vector pET22b+ between the BioBrick pre- and suffix of <a href="http://parts.igem.org/Part:pSB1C3" target="_blank">pSB1C3</a>. These include a T7 promoter and terminator, a ribosomal binding site, the self-designed <a class="wikilink1" href="#cloning_site_anchor" title="Cloning site">cloning site</a> and a lacI expression cassette. Additionally, a pelB signal sequence for periplasmic translocation was added 5’ to the cloning site.  
+
Coupling of DNA to the PDMS slide was achieved using a DNA concentration of 25&nbsp;ng/µl. Either 1 or 3 µl were spotted directly onto the slide using a distinct pattern (figure 2A). To verify that immobilization occurs specifically for amino-labeled DNA, we used non-amino-labeled DNA as a negative control and spotted the same amount. The slide was subsequently incubated over night and the DNA solution was dried afterwards at 60°C. After washing the slide, immobilized DNA was visualized by fluorescence microscopy. The resulting fluorescence pattern clearly corresponds to the spotting pattern on the slide, thereby confirming that the immobilization of DNA was successful. Spots that were incubated with amino-labeled DNA show a distinct Cy3 fluorescence signal, whereas DNA that was not labeled with an amino group was not bound to the surface (figure 2B).  
 
</p>
 
</p>
<div class="kommentar">
+
 
Der pIG15002 ist doch für eukaryotische Expression gewesen, nicht für cell-free. Sonst macht der CMV promoter wenig sinn, oder? ich pass den text mal dahingehend an...(ps1709)
+
<h2 class="left">Cell-Free Expression of GFP From Spotted DNA</h2>
</div>
+
 
 
<div class="image_box left">
 
<div class="image_box left">
  <div class="thumb2 trien" style="width:260px">
+
  <div class="thumb2 trien" style="width:300px">
 
                   <div class="thumbinner">
 
                   <div class="thumbinner">
                       <a href="https://static.igem.org/mediawiki/2015/a/ac/Freiburg_labjournal-cloning-pig15_002neu.jpg" class="lightbox_trigger">
+
                       <a href="lightbox_trigger" href="https://static.igem.org/mediawiki/2015/thumb/9/99/Freiburg_20150911_DNA_on_PDMS_7.0_oven30min_expr30min.jpg/794px-Freiburg_20150911_DNA_on_PDMS_7.0_oven30min_expr30min.jpg" class="lightbox_trigger">
                       <img src="https://static.igem.org/mediawiki/2015/a/ac/Freiburg_labjournal-cloning-pig15_002neu.jpg" width="250px">   
+
                       <img src="https://static.igem.org/mediawiki/2015/thumb/9/99/Freiburg_20150911_DNA_on_PDMS_7.0_oven30min_expr30min.jpg/794px-Freiburg_20150911_DNA_on_PDMS_7.0_oven30min_expr30min.jpg" width="250px">   
 
                         <div class="thumbcaption">
 
                         <div class="thumbcaption">
 
                       </a>
 
                       </a>
                           <p><strong>Figure 3: pIG15_002.</strong> For expression in eukaryotic cells the <a class="urlextern" href="http://parts.igem.org/Part:pSB1C3" target="_blank" title="pSB1C3">pSB1C3</a> backbone was altered similarly, but without a pelB secretion signal or lacI coding sequence and with a CMV promoter instead of a T7 promoter.</p>
+
                           <p><strong>Figure 3: Cell-free expressed GFP confirmed by fluorescence microscopy.</strong></p>
 
                       </div>
 
                       </div>
 
                 </div>
 
                 </div>
 
</div>
 
</div>
 
</div>
 
</div>
 
  
 
<p>
 
<p>
The vector for expression in mammalian cells(pIG15_002; figure 3) was designed analogously, but lacking the lacI expression cassette and the signal sequence. The T7 promoter and terminator were exchanged by a CMV promoter and a WPRE terminator region for secretion into the medium.
+
To confirm that DNA was not only bound to the PDMS slide but is also suited for cell-free expression, we flushed the microfluidic chamber described above with our cell-free  expression mix. After incubation for two hours at room temperature the expressed GFP was detected using a standard fluorescence microscope (figure 3).  
<p>
+
Unfortunately, after the first expression experiment in <i>E. coli</i>, we realized that the yields of protein expression are not sufficient for our purposes. Instead of wasting time trying to optimize our own expression vector, we went on using the original vector and modified the cloning site to fit our requirements. The original vector pET22b+ and the modified version pET_iGEM are compared in figure 4.
+
</p>
+
  
<p>
+
More details on the vector design and cloning strategies to generate the needed DNA can be found <a href="https://2015.igem.org/Team:Freiburg/Methods/Cloning">here</a>.  
Using an adapted commercial expression vector finally resulted in sufficiently high protein yields. The advantages of expression vectors like pET22b+ in contrast to cloning vectors like <a class="urlextern" href="http://parts.igem.org/Part:pSB1C3" target="_blank" title="pSB1C3">pSB1C3</a> are discussed in detail on the introduction page for <a class="wikilink1" href="https://2015.igem.org/Team:Freiburg/Description" title=„pOP“>pOP</a>. This is a plasmid backbone we submitted to the iGEM Registry that is optimized for protein overexpression purposes and fully compatible with iGEM idempotent cloning standards of RFC[25].
+
</br>
+
The backbone for cell-free expression was not changed because a PCR product of the expression cassette serves as a template for the actual expression purpose making the vector it is assembled on irrelevant. Using a high-copy plasmid as <a class="urlextern" href="http://parts.igem.org/Part:pSB1C3" target="_blank" title="pSB1C3">pSB1C3</a> rather simplifies cloning efforts.  
+
 
</p>
 
</p>
  
<div class="flexbox">
 
<div class="thumb2 trien" style="width:1000px">
 
                  <div class="thumbinner">
 
                      <a href="https://static.igem.org/mediawiki/2015/b/b9/150917_pETComp_WIKI2neu_LS.png" class="lightbox_trigger">
 
                      <img src="https://static.igem.org/mediawiki/2015/b/b9/150917_pETComp_WIKI2neu_LS.png" width="780px"> 
 
                        <div class="thumbcaption">
 
                      </a>
 
                          <p><strong>Figure 4: Comparison of pET_iGEM and pET22b+.</strong> The two vectors differ in the cloning site that contains only four restriction sites in pET_iGEM (<i>Acc</i>65I, <i>Bam</i>HI, <i>Hind</i>III, <i>Afl</i>II) compared to the more complex multiple cloning site of the original pET22b+ (<i>BamHI</i>, <i>Eco</i>RI, <i>Sac</i>I, <i>Sal</i>I, <i>Hind</i>III, <i>Not</i>I, <i>Ava</i>I, <i>Xho</i>I). The 6xHis-Tag from pET22b+ was also removed to enable easy tag-exchanges with our system.</p>
 
                      </div>
 
                </div>
 
 
</div>
 
</div>
</div>
 
</div>
 
 
 
 
<span id="detailed_cloning_anchor" class="anchor"></span>
 
<div id="detailed_cloning" class="content_box"> 
 
  <h1>3. Detailed Cloning Strategy</h1>
 
  <p>
 
As mentioned before, we established a cloning strategy, which is easy to handle for a team of researchers working together on the same project. It facilitates easy exchange of tags for custom purposes. All our cloning efforts began with either pET_iGEM, the modified version of pET22b+, for <i>E. coli</i>-based protein expression or pIG15_104, where the expression site derived from pET22b+ was inserted into <a class="urlextern" href="http://parts.igem.org/Part:pSB1C3" target="_blank" title="pSB1C3">pSB1C3</a>.
 
 
        <h3>The Basic Constructs (Protein Purification Using <i>E. coli</i>)</h3>
 
        <p>
 
<span class="biobrick_emphasize"><strong>pET_iGEM</strong></span>: To modify the multiple cloning site of pET22b+ for our purposes, we performed a Gibson Assembly with only one fragment. Therefore, we designed primers for the amplification of the whole plasmid, except the MCS. The cloning site we designed ourselves was part of the primer extension.
 
        </p>
 
        <p>
 
<span class="biobrick_emphasize"><strong>pET_803</strong></span>: To insert the very small but commonly used His-tag, we again used Gibson Assembly because classical cloning of such small parts can be a challenging task. The respective primers were designed for amplification of <a class="media" href="http://parts.igem.org/Part:BBa_K1621002" target="_blank" title="BBa_1621002">antigen 8 (Herpes Simplex Virus Type 1, glycoprotein G1)</a> to combine the insertion of the tag and an antigen. While the forward primer was a regular Gibson primer, the reverse primer additionally contained the sequence of a 10xHis-tag. After amplification, the part was inserted into the <i>Bam</i>HI and <i>Afl</i>II digested backbone pET_iGEM resulting in the first antigen with N-terminal His-tag.
 
        </p>
 
        <p>
 
<span class="biobrick_emphasize"><strong>pET_804</strong></span>: Another tag we wanted to use for immobilization of the antigens on the surface is the <a class="media" href="http://parts.igem.org/Part:BBa_K1159201" target="_blank" title="BBa_K1158201">SpyTag</a>. This part of 39 bp length was inserted into pET_iGEM analogous to the 10xHis-tag. The only difference was that the forward primer for amplification of antigen 8 included a standard 6xHis-tag, which enables the purification of the protein. Consistent with our cloning strategy, the amplified part was inserted between <i>Acc</i>65I and <i>Afl</i>II as it contains an N-terminal as well as a C-terminal tag. <i>Bam</i>HI and <i>Hind</i>III restriction sites were retained flanking the antigen making it freely exchangeable.
 
        </p>
 
        <p>
 
<span class="biobrick_emphasize"><strong>pET_805</strong></span>: The only tag we used that was not inserted via Gibson Assembly was the HaloTag. With a length of about 900 bp, classical cloning of this part was no trouble. The <a class="wikilik1" href="https://2015.igem.org/Team:Freiburg/Project/Surface_Chemistry#halo_surface_anchor" titlre="halo">HaloTag</a> exists in two variants, one being optimized for C-terminal tagging of the protein, the other for N-terminal tagging. As the tag we had access to was the C-terminal one, the SpyTag in pET_804 was exchanged using the restriction sites <i>Hind</i>III and <i>Afl</i>II resulting in <b>pET_805</b>.
 
        </p>
 
 
 
<h3 class="sectionedit2">Tagged Constructs (Protein Purification Using <i>E. coli</i>)</h3>
 
<p>
 
We wanted to establish a tag-system, which minimizes unspecific binding of proteins to the chip surface, therefore testing different <a class="wikilink1" href="https://2015.igem.org/Team:Freiburg/Project/Surface_Chemistry" title="tag_systems">tag systems</a>.
 
</p>
 
 
<p>
 
<span class="biobrick_emphasize"><strong>His-tag</strong></span>: Every antigen was genetically fused to a C-terminal 10xHis-tag, which could be used for its immobilization on the surface as well as for its purification. The basic construct for this purpose was pET_803. The <a class="media" href="http://parts.igem.org/Part:BBa_K1621002" target="_blank" title="BBa_1621002">Herpes Simplex Virus derived antigen</a>, which was initially finished cloning, had to be excised by restriction with <i>Bam</i>HI and <i>Hind</i>III. Thus, all the other antigens digested in the same way could be ligated into this backbone.
 
</p>
 
 
<p>
 
<span class="biobrick_emphasize"><strong>SpyTag</strong></span>: Another tag for surface immobilization of the antigen is the <a class="media" href="http://parts.igem.org/Part:BBa_K1159201" target="_blank" title="BBa_K1158201">SpyTag</a>. To enable protein purification via Ni-NTA columns proteins fused to the SpyTag were additionally fused to a C-terminal 6xHis-tag. The basic vector for cloning these constructs was pET_804. Excision of the <a class="media" href="http://parts.igem.org/Part:BBa_K1621002" target="_blank" title="BBa_1621002">Herpes Simplex Virus derived antigen</a> and insertion of other antigens was performed analogous to the antigen exchange in His-tag constructs.
 
</p>
 
 
<p>
 
<span class="biobrick_emphasize"><strong>HaloTag</strong></span>: As a second covalent tag-system for immobilization of the antigens on the surface we used the HaloTag, which specifically binds to a <a class="wikilink1" href="https://2015.igem.org/Team:Freiburg/Project/Surface_Chemistry#halo_surface_anchor" title="halo_surface">chloroalkane surface</a>. Using our own cloning strategy, the HaloTag could easily be inserted between <i>Hind</i>III and <i>Afl</i>II, using pET_803 as basis. Cloning of the HaloTag into pET_803 leads to a new vector, pET_805. This vector is then used to substitute the antigens. As in the SpyTag construct, this new vector contains a C-terminal 6xHis-tag for purification of the antigens.
 
</p>
 
 
 
<h3 class="sectionedit2">Cell-Free Backbone</h3>
 
<p>
 
As described above we decided to use the <a class="media" href="http://parts.igem.org/Part:pSB1C3" target="_blank" title="pSB1C3">pSB1C3</a> standard vector as backbone for our <a class="wikilink1" href="https://2015.igem.org/Team:Freiburg/Project/Cellfree_Expression" title="cellfree">cell-free expression</a> constructs. Inserted between the <a class="wikilink1" href="http://parts.igem.org/Help:Standards/Assembly/RFC10" target="_blank" title="RFC10">RFC 10</a> prefix and suffix is our own cloning site, containing the following restriction sites: <i>Acc</i>65I, <i>Bam</i>HI, <i>Hind</i>III and <i>Afl</i>II. We included a T7 promoter and a ribosomal binding site between the <a class="urlextern" href="http://parts.igem.org/Help:Standards/Assembly/RFC10" target="_blank" title="RFC10">RFC 10</a> prefix and the <i>Acc</i>65I restriction site. A stop codon cassette and a T7 terminator were inserted between the <i>Afl</i>II restriction site and the <a class="urlextern" href="http://parts.igem.org/Help:Standards/Assembly/RFC10" target="_blank" title="RFC10">RFC 10</a> suffix. These similarities to the expression vector facilitate the easy exchange of fragments between the standard expression vector and the cell-free expression vector. Using our cloning site it is rather simple to exchange different tag-combinations. The advantage of the <a class="urlextern" href="http://parts.igem.org/Part:pSB1C3" target="_blank" title="pSB1C3">pSB1C3</a> backbone is the high copy origin, allowing a rapid multiplication and easy cloning. For the cell-free expression itself the vector backbone is dispensable as only the part amplified via PCR between the prefix and the suffix is mandatory for cell-free expression.
 
</p>
 
 
 
<h3 class="sectionedit2">The Basic Constructs (Cell-Free Expression)</h3>
 
<p>
 
<span class="biobrick_emphasize"><strong>pIG15_104</strong></span>: For the first basic construct we ordered a gBlock from <a class="urlextern" href="https://eu.idtdna.com/site" target="_blank" title="IDT">IDT</a> containing the T7 promoter, ribosomal binding site, our cloning site and the T7 terminator with adjoining stop codon cassette. Between <i>Bam</i>HI and <i>Hind</i>III the coding sequence for tYFP and between <i>Hind</i>III and <i>Afl</i>II the SpyTag sequence was inserted. This gBlock was then inserted into the pJET1.2 vector. Afterwards, it was digested out of pJET1.2 and classically cloned into the <a class="urlextern" href="http://parts.igem.org/Part:pSB1C3" target="_blank" title="pSB1C3">pSB1C3</a> backbone resulting in the first basic construct for cell-free expression. We inserted tYFP as default fragment into the cell-free expression backbone because we already had some anti-tYFP antibody available. Hence, first measurements for analyzing the binding of anti-tYFP to tYFP could be performed as soon as the basic construct was finished. Besides, tYFP could be used as reporter. Using <i>Bam</i>HI and <i>Hind</i>III restriction sites tYFP could be excised and replaced by antigen sequences analogous to the cloning system used for the expression vector.
 
</p>
 
 
<p>
 
<span class="biobrick_emphasize"><strong>pIG15_105</strong></span>: Using the <i>Hind</i>III and <i>Afl</i>II restriction sites, the SpyTag sequence was excised from pIG15_104. For our second covalent tag system we inserted the sequence for the HaloTag via classical cloning and thereby producing our next basic construct for cell-free expression, pIG15_105. This backbone again contains tYFP as default insert, this time with a C-terminal HaloTag.<br>
 
Using identical cloning strategies as with the first basic construct (pIG15_104) all antigen sequences could be inserted into this vector using <i>Bam</i>HI and <i>Hind</i>III.
 
</p>
 
 
</div> <!--- End of content box -->
 
  
 
</html>
 
</html>
 +
<!-- Labjournal content ends here -->
 
{{Freiburg/wiki_content_end}}
 
{{Freiburg/wiki_content_end}}

Revision as of 16:20, 18 September 2015

""

Cell-Free Expression of Immobilized DNA

An important advantage of the DiaCHIP is the possibility to ship and store information encoded by DNA. From a DNA template array protein arrays can be produced on demand. In order to obtain this template, DNA is fixed on a silicone slide forming one side of our microfluidic chamber. Making use of a cell-free expression system, the DNA can then be transcribed and translated into the respective proteins resulting in the final protein array. The coding sequence of the proteins is genetically fused to a tag allowing their binding to a specific surface on the opposite side of the chamber.

Successful binding of DNA to the Silicone Slide

Figure 1: Scheme of the APTES/PDITC surface. The PDMS surface is layered with PDITC. This enables the binding of the amino-labeled DNA.

The core component of the DiaCHIP is the microfluidic chamber composed of a glass slide for protein immobilization and a PDMS (polydimethylsiloxane) flow cell. The silicone PDMS needs to be activated to enable the generation of the DNA template array by binding of the respective sequences. Oxygen plasma is used to first activate the surface of the PDMS slide. This allows to cover it with the silane APTES and finally apply the crosslinker PDITC. The DNA sequence to be immobilized requires an amino group to be covalently immobilized on the PDITC surface. The structure of this surface is schematically visualized in figure 1. The same surface chemistry can be used to immobilize proteins unspecifically.
To obtain an expression cassette for GFP with such an amino group, the target sequence was amplified by PCR using an amino-labeled reverse primer. Additionally, the forward primer was labeled by the fluorescent dye Cy3 to enable visualization by fluorescence microscopy. Successful amplification of the target sequence was verified by agarose gel electrophoresis.

Figure 2: Immobilization of DNA on a PDMS slide. A: Top view on the slide indicating the spotting pattern. B: Cy3 fluorescence indicating successful immobilization of amino-labeled DNA. As a negative control, Cy3- but not amino-labeled DNA was spotted.

Coupling of DNA to the PDMS slide was achieved using a DNA concentration of 25 ng/µl. Either 1 or 3 µl were spotted directly onto the slide using a distinct pattern (figure 2A). To verify that immobilization occurs specifically for amino-labeled DNA, we used non-amino-labeled DNA as a negative control and spotted the same amount. The slide was subsequently incubated over night and the DNA solution was dried afterwards at 60°C. After washing the slide, immobilized DNA was visualized by fluorescence microscopy. The resulting fluorescence pattern clearly corresponds to the spotting pattern on the slide, thereby confirming that the immobilization of DNA was successful. Spots that were incubated with amino-labeled DNA show a distinct Cy3 fluorescence signal, whereas DNA that was not labeled with an amino group was not bound to the surface (figure 2B).

Cell-Free Expression of GFP From Spotted DNA

Figure 3: Cell-free expressed GFP confirmed by fluorescence microscopy.

To confirm that DNA was not only bound to the PDMS slide but is also suited for cell-free expression, we flushed the microfluidic chamber described above with our cell-free expression mix. After incubation for two hours at room temperature the expressed GFP was detected using a standard fluorescence microscope (figure 3). More details on the vector design and cloning strategies to generate the needed DNA can be found here.