Difference between revisions of "Team:Freiburg/Project/pOP-vector"

(Blanked the page)
 
(28 intermediate revisions by 9 users not shown)
Line 1: Line 1:
{{Freiburg/CSS}}
 
{{Freiburg/Menubar}}
 
  
{{Freiburg/wiki_content_start}}
 
<html>
 
 
<div class="kommentar">
 
<strong>Geneious-Plasmid-Map oder eigenes Bild?</strong>
 
Eigene Schemazeichnung (Stefan)
 
</div>
 
 
<div class="content_box">
 
<h1 class="sectionedit1">pOP – Protein Expression meets iGEM Standards</h1>
 
<div class="level1">
 
<p>
 
<br/>
 
 
All the constructs we cloned for this year’s iGEM competition were meant to be used for overexpression of the respective proteins, either in a cell-free expression system or in an <em>E. coli</em> expression strain. Usually, vectors that are optimized for protein overexpression are low- to medium-copy plasmids. In contrast to cloning purposes, this is sufficient for protein expression. When a certain copy number is reached, the expression machinery of the cell is saturated and a further increase will not result in higher expression yields. High copy plasmids rather result in lower expression rates because more metabolic capacity is shared for replication. <br/>
 
<br/>
 
 
Many <em>E. coli</em> strains optimized for overexpression carry a chloramphenicol resistance gene as a selective marker. Plasmids carrying the same marker are not suitable for protein expression for two reasons. First, double selection for successfully transformed colonies on a medium with two antibiotics is not possible. Second, there is no selective pressure which makes it an advantage for the cell to even keep the plasmid.<br/>
 
 
The iGEM standard vector pSB1C3 was designed for cloning purposes and thus is provided with an origin of replication yielding high plasmid copy numbers. Moreover, it carries a chloramphenicol resistance gene as selection marker which makes it a tough task to use this vector for expression purposes.<br/>
 
<br/>
 
 
Using a modified version of pSB1C3 (plasmid map pIG15_001) for overexpression resulted in an unsatisfying protein amount (link to an early SDS gel by ProtPur?). Thus, we decided to use a common expression vector for further experiments. <br/>
 
 
Obviously, it is a lot of work to clone every part we want to send to the registry into an expression vector and additionally into pSB1C3 which exhibits a completely different cloning site. For those reasons, we aimed to add an improved vector backbone to the iGEM registry which is suitable for efficient protein overexpression and compatible for cloning parts derived from the registry in a standardized procedure. <br/>
 
 
</p>
 
<div class="flexbox">
 
<div class="thumb2 trien" style="width:610px"><div class="thumbinner"><a class="media" href="https://static.igem.org/mediawiki/2015/e/ee/Freiburg_labjournal-cloning-pop1.jpg" title="labjournal:cloning:pop1.jpg"><img alt="" class="mediabox2" src="https://static.igem.org/mediawiki/2015/e/ee/Freiburg_labjournal-cloning-pop1.jpg" width="600"/></a><div class="thumbcaption"><div class="magnify"><a class="internal" href="https://static.igem.org/mediawiki/2015/e/ee/Freiburg_labjournal-cloning-pop1.jpg" title="vergrößern"><img alt="" height="11" src="/igem2015/lib/plugins/imagebox/magnify-clip.png" width="15"/></a></div>Fig. 1: pOP (plasmid for Overexpression of Proteins). Expression vector based on pET22b+ that is fitted to iGEM standards by incorporation of RFC25 and removal of forbidden restriction sites.</div></div></div></div>
 
<p>
 
 
</p>
 
 
<div class="flexbox">
 
<div class="thumb2 trien" style="width:900px"><div class="thumbinner"><a class="media" href="https://static.igem.org/mediawiki/2015/f/f6/2015_Freiburg_POPai.jpg"><img align="center" alt="pOPai" src="https://static.igem.org/mediawiki/2015/f/f6/2015_Freiburg_POPai.jpg" width="900px"></a><div class="thumbcaption">
 
<p><strong>Fig. 1</strong>: pOP (plasmid for Overexpression of Proteins). Expression vector based on pET22b+ that is fitted to iGEM standards by incorporation of RFC25 and removal of forbidden restriction sites.</p></div></div></div>
 
</div>
 
 
<p>
 
 
<br/>
 
 
The new vector, called pOP – plasmid for Overexpression of Proteins (Fig. 1) - combines features needed for efficient overexpression of proteins with standardized elements derived from pSB1C3. Based on the commonly used expression vector pET22b+, some changes had to be applied to fit all the iGEM standards.<br/>
 
 
First, one of the standard cloning sites had to be inserted instead of the original multiple cloning site. <acronym title="Request for Comments">RFC</acronym>[25] seemed to be the most suitable for protein expression purposes, because it allows the assembly of several coding sequences because the scar which is left between the sequences does not result in a frameshift or a stop codon. This is advantageous for expression of fusion proteins on the one hand and enables to genetically fuse the protein of interest to a specific tag for affinity purification on the other hand. Additionally, signal sequences can be added to cause secretion of the protein which is a commonly used tool for simplification of protein purification. <br/>
 
 
Next, recognition sites for restriction enzymes which are used for the insertion of coding sequences had to be eliminated in the backbone, so those enzymes (namely AgeI, EcoRI, NgoMIV, NotI, SpeI, PstI and XbaI) remain single cutters. <br/>
 
 
To allow sequence analysis in a standardized way, the binding sites of the primers VF2 and VR as they are used by the iGEM registry have been inserted in an appropriate distance to the insertion site.<br/>
 
<br/>
 
 
The final vector was designed theoretically based on pET22b+. Because the sites where adaptations had to be applied were distributed all over the vector, a multi-step mutagenesis approach was difficult. Instead, the vector was divided into five fragments which were pieced together in two steps by Gibson Assembly. The resulting plasmid is shown in figure x.<br/>
 
<br/>
 
 
Taken together, we designed a new plasmid for the overexpression of proteins that is compatible with iGEM cloning standards. We are happy to provide this new backbone to the iGEM registry and help future iGEM teams to reach high expression yields in an easy way.
 
</p>
 
<div class="tags"><span>
 
<a class="wikilink1" href="/igem2015/doku.php?id=tag:info&amp;do=showtag&amp;tag=info" rel="tag" title="tag:info">info</a>
 
</span></div>
 
</div>
 
 
</div>
 
</html>
 
{{Freiburg/wiki_content_end}}
 

Latest revision as of 12:50, 17 September 2015