Team:Heidelberg/Parts

From 2014.igem.org

(Difference between revisions)
(Prototype team page)
(Undo revision 385449 by Bunnech (talk))
 
(50 intermediate revisions not shown)
Line 1: Line 1:
-
{{CSS/Main}}
+
{{:Team:Heidelberg/Templates/IncludeCSS|:Team:Heidelberg/css/boxes}}
-
 
+
<html><style type="text/css">
-
 
+
.subtitle h2 {
 +
color: white;
 +
padding-left: 15px;
 +
}
 +
</style></html>
 +
{{:Team:Heidelberg/templates/wikipage_new|
 +
|
 +
container-style=background-color: black; background-image: url(/wiki/images/6/6a/Heidelberg_epic_background.jpg); background-repeat: no-repeat; background-size: 100% auto;
 +
|
 +
title=PARTS
 +
|
 +
white=true
 +
|
 +
red-logo=true
 +
|
 +
subtitle=Discover our workpieces and standards
 +
|
 +
abstract=
 +
|
 +
content=
<html>
<html>
-
<style type="text/css">
+
<div class="col-lg-3 col-md-2 hidden-sm hidden-xs" style="text-align: center;">
-
#groupparts {text-align: center; margin-left: auto; margin-right: auto;}
+
<img src="https://static.igem.org/mediawiki/2014/4/4b/Heidelberg_Parts_bg.png" class="img-responsive" />
-
</style>
+
</div>
-
<!--main content -->
+
<div class="col-lg-9 col-md-10 col-sm-12 col-xs-12">
-
<table width="70%" align="center">
+
<div class="col-lg-12" style="margin: -15px; margin-bottom:15px;">
 +
  <div class="boxes-table">
 +
      <div class="cell" style="width:60%;">
 +
        <a href="https://2014.igem.org/Team:Heidelberg/Parts/RFC" class="box" style="margin-bottom:15px; display:block;">
 +
          <h3>New <span>RFC</span> iGEM_HD14</h3>
 +
        To use inteins as easy and standarized tools to modify proteins after translation we developed a new RFC for the iGEM community. Take a closer look on our new intein standard!
 +
        </a>
 +
        <a href="#Intein Library" class="box" style="display:block;">
 +
          <h3>The <span>Intein</span> Library</h3>
 +
          Protein splicing by inteins is a natural process in which the catalytically active polypeptide termed intein excises itself from a precursor protein leaving the flanking chains reconnected. Deployed in our system inteins are modular instruments for several protein modifications. In our intein library you can find a list of all inteins we used, popular and really fast ones.
 +
        </a>
 +
      </div>
 +
      <div class="cell" style="width:60%;">
 +
     
 +
      <a href="#Favorite Parts" class="box" style="display:block; position:relative; margin-bottom:15px;">
 +
        <h3>Our <span>favorite</span> Parts</h3>
 +
          The intein toolbox built by the iGEM Team Heidelberg includes three basic mechanisms. With our favorite parts we want to introduce you to the constructs enabling these priciples!
 +
      <img src="/wiki/images/9/9b/Heidelberg_Favoriteparts_star.png" class="star" alt="Favorite Parts Image" /> 
 +
      </a>
-
 
+
      <a href="#Sample Data Page" class="box" style="display:block;">
-
<!--welcome box -->
+
        <h3>Sample <span>Data</span> Page</h3>
-
<tr>
+
        Take a look at our favorite Parts for circularization, fusion or tagging and see how our system works in the living cell. For that visit our Sample Data Page.      
-
<td style="border:1px solid black;" colspan="3" align="center" height="150px" bgColor=#FF404B>
+
      </a>
-
<h1 >WELCOME TO iGEM 2014! </h1>
+
      </div>
-
<p>Your team has been approved and you are ready to start the iGEM season!
+
  </div>
-
<br>On this page you can document your project, introduce your team members, document your progress <br> and share your iGEM experience with the rest of the world! </p>
+
  <div class="boxes-table">
-
<br>
+
      <a href="#allParts" class="box cell" style="width: 55%;">
-
<p style="color:#E7E7E7"> <a href="https://2014.igem.org/wiki/index.php?title=Team:Heidelberg/Parts&action=edit"style="color:#FFFFFF"> Click here  to edit this page!</a> </p>
+
        <h3>Our <span>BioBricks</span></h3>
-
</td>
+
        Creating a new standard and basic constructs of our toolbox, we sent in 67 new Parts for the Registry of Biological parts! Next to parts for intein-splicing we built sortase constructs to modify proteins post-translationally, too. Here you can find a List of all Parts!</a>
-
</tr>
+
      <a href="#Backbones" class="box cell" >
-
 
+
        <h3>Our <span>Backbones</span></h3>
-
<tr> <td colspan="3"  height="5px"> </td></tr>
+
        Creating a new series of Backbones including a T7 promoter with a lac operon, expressing our constructs and sharing them with other iGEM teams, you have to take a closer look on BBa_K1362091-97! Read more about it under Collaborations.
-
<!-- end welcome box -->
+
      </a>
-
<tr>
+
  </div>
-
 
+
  <div class="boxes-table">
-
<!--navigation menu -->
+
      <a href="https://2014.igem.org/Team:Heidelberg/Parts/Part_Improvement" class="box cell" style="padding-right:100px;position:relative;" >
-
<td align="center" colspan="3">
+
        <h3><span>Improving</span> an existing Part</h3>
-
 
+
        Standardization and building up on existing parts are the fundaments of iGEM. We improved a Xylanase (wood degrading enzyme) by improving its sequence for the expression in <i>E. coli</i> and further characterized its function in respect to heat stability.  
-
<table width="100%">
+
        <img class="small-igem-logo" src="/wiki/images/7/79/IGEM_logo_red.png" alt="igem-icon" />
-
<tr heigth="15px"></tr>
+
      </a>
-
<tr heigth="75px">
+
  </div>
-
 
+
</div>
-
 
+
</div>
-
<td style="border:1px solid black;" align="center" height ="45px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7> 
+
</div></div><!-- close container div of template -->
-
<a href="https://2014.igem.org/Team:Heidelberg"style="color:#000000">Home </a> </td>
+
<div class="container" style="background-color:white;margin-top:75px;">
-
 
+
<div class="col-lg-12">
-
<td style="border:1px solid black;" align="center" height ="45px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7>  
+
<!-- für meine allerliebste Charlotte <3 -->
-
<a href="https://2014.igem.org/Team:Heidelberg/Team"style="color:#000000"> Team </a> </td>
+
-
 
+
-
<td style="border:1px solid black;" align="center"  height ="45px"  onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7>  
+
-
<a href="https://igem.org/Team.cgi?year=2014&team_name=Heidelberg"style="color:#000000"> Official Team Profile </a></td>
+
-
 
+
-
<td style="border:1px solid black" align="center"  height ="45px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7> 
+
-
<a href="https://2014.igem.org/Team:Heidelberg/Project"style="color:#000000"> Project</a></td>
+
-
 
+
-
<td style="border:1px solid black;" align="center"  height ="45px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7>  
+
-
<a href="https://2014.igem.org/Team:Heidelberg/Parts"style="color:#000000"> Parts</a></td>
+
-
 
+
-
<td style="border:1px solid black;" align="center" height ="45px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7>
+
-
<a href="https://2014.igem.org/Team:Heidelberg/Modeling"style="color:#000000"> Modeling</a></td>
+
-
 
+
-
<td style="border:1px solid black;" align="center" height ="45px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7> 
+
-
<a href="https://2014.igem.org/Team:Heidelberg/Notebook"style="color:#000000"> Notebook</a></td>
+
-
 
+
-
<td style="border:1px solid black;" align="center"  height ="45px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7>  
+
-
<a href="https://2014.igem.org/Team:Heidelberg/Safety"style=" color:#000000"> Safety </a></td>
+
-
 
+
-
<td style="border:1px solid black;" align="center"  height ="45px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7>
+
-
<a href="https://2014.igem.org/Team:Heidelberg/Attributions"style="color:#000000"> Attributions </a></td>
+
-
 
+
-
 
+
-
<td align ="center"> <a href="https://2014.igem.org/Main_Page"> <img src="https://static.igem.org/mediawiki/igem.org/6/60/Igemlogo_300px.png" width="55px"></a> </td>
+
-
</tr>
+
-
</table>
+
-
 
+
-
<!--end navigation menu -->
+
-
</tr>
+
-
 
+
-
 
+
-
</tr>
+
-
+
-
 
+
-
 
+
-
 
+
-
 
+
-
</td>
+
-
 
+
-
<tr> <td colspan="3"  height="15px"> </td></tr>
+
-
<tr><td bgColor="#e7e7e7" colspan="3" height="1px"> </tr>
+
-
<tr> <td colspan="3"  height="5px"> </td></tr>
+
-
 
+
-
 
+
-
<!--Parts Submitted to the Registry  -->
+
-
<tr><td > <h3> Parts Submitted to the Registry </h3></td>
+
-
<td ></td >
+
-
<td > <h3>What information do I need to start putting my parts on the Registry? </h3></td>
+
-
</tr>
+
-
<tr>
+
-
<td width="45%"  valign="top">
+
-
<p>
+
-
An important aspect of the iGEM competition is the use and creation of standard  biological parts. Each team will make new parts during iGEM and will submit them to the <a href="http://partsregistry.org"> Registry of Standard Biological Parts</a>. The iGEM software provides an easy way to present the parts your team has created. The "groupparts" tag will generate a table with all of the parts that your team adds to your team sandbox. 
+
-
 
+
-
<p>
+
-
<strong>Note that if you want to document a part you need to document it on the <a href="http://partsregistry.org Registry"> Registry</a>, not on your team wiki.</strong> Future teams and other users and are much more likely to find parts on the Registry than on your team wiki.
+
-
</p>
+
-
 
+
-
<p>
+
-
Remember that the goal of proper part documentation is to describe and define a part, so that it can be used without a need to refer to the primary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper references to acknowledge previous authors and to provide for users who wish to know more.
+
-
</p>
+
-
 
+
-
 
+
-
 
+
-
<h3>When should you put parts into the Registry?</h3>
+
-
 
+
-
<p>
+
-
As soon as possible! We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The sooner you put up your parts, the better recall you will have of all details surrounding your parts. Remember you don't need to send us the DNA to create an entry for a part on the Registry. However, you must send us the sample/DNA before the Jamboree. Only parts for which you have sent us samples/DNA are eligible for awards and medal requirements.
+
-
</p>
+
-
</td>
+
-
 
+
-
<td > </td>
+
-
<td width="45%" valign="top">
+
-
 
+
-
<p>
+
-
The information needed to initially create a part on the Registry is:
+
-
</p>
+
-
<ol>
+
-
 
+
-
<li>Part Name</li>
+
-
<li>Part type</li>
+
-
<li>Creator</li>
+
-
<li>Sequence</li>
+
-
<li>Short Description (60 characters on what the DNA does)</li>
+
-
<li>Long Description (Longer description of what the DNA does)</li>
+
-
<li>Design considerations</li>
+
-
</ol>
+
-
 
+
-
<p>
+
-
We encourage you to put up <em>much more</em> information as you gather it over the summer. If you have images, plots, characterization data and other information, please also put it up on the part page. Check out part <a href="http://parts.igem.org/Part:BBa_K404003">BBa_K404003</a> for an excellent example of a highly characterized part.
+
-
</p>
+
-
 
+
-
<p>
+
-
You can add parts to the Registry at our <a href="http://parts.igem.org/Add_a_Part_to_the_Registry"> Add a Part to the Registry</a> link.
+
-
</p>
+
-
</td>
+
-
</tr>
+
-
 
+
-
 
+
-
<tr> <td colspan="3" height="15px"> </td></tr>
+
-
 
+
-
<tr><td colspan="3" > <h3> Parts Table</h3></td></tr>
+
-
 
+
-
 
+
-
<tr><td width="45%" colspan="3"  valign="top">
+
-
Any parts your team has created will appear in this table below:</td></tr>
+
-
 
+
-
</table>
+
</html>
</html>
-
 
+
{{:Team:Heidelberg/pages/Parts}}
-
<groupparts>iGEM013 Heidelberg</groupparts>
+
<html>
 +
</div>
 +
</div>
 +
</html>
 +
|
 +
header-img=
 +
|
 +
header-bg=
 +
|
 +
red=
 +
|
 +
titles=
 +
|
 +
white-logo=
 +
}}

Latest revision as of 01:57, 18 October 2014

– Discover our workpieces and standards

Favorite Parts.

The iGEM Team Heidelberg 2014 had built a new biological system for the iGEM community integrating split-inteins. Intein splicing is a natural process that excises one part of a protein and leaves the remaining parts irreversibly attached. This great function allows you to modify your protein in numerous ways.

Creating a toolbox including all great functions and possibilities of inteins, we need a new standard for the scientific world of iGEM. This standard, the RFC of the iGEM Team Heidelberg 2014, allows us to easily and modulary work with split inteins.

Our favorite Parts represent the basic constructs of our toolbox – the Assembly and the Circularization construct, which are both tested in many methods and applications.

In the following we present you BBa_K1362000, the construct for circularization, BBa_K1362100 and BBa_K1362101, the N- and the C-construct for assembly. Take a look and visit the Partsregistry to read the associated documentation.



Circularization Construct. BBa_K1362000

BBa_K1362000

This part is an element of the Team Heidelberg 2014 intein toolbox and can be used as described in the new RFC[i]. The purpose of this tool is to provide an easy way to circularize any linear protein. While conserving the functionality of their linear counterpart, circular proteins can be superior in terms of thermostability, resistance against chemical denaturation and protection from exopeptidases. Moreover, a circular backbone can improve in vivo stability of therapeutical proteins and peptides. Using this part, Xylanase, lambda lysozyme and DNA methyltransferase (DNMT1) were successfully circularized.
Circularization Construct

Assembly Constructs. BBa_K1362100 and BBa_K1362101

BBa_K1362100

This intein assembly construct is part of our strategy for cloning with split inteins. Inteins are naturally occuring peptide sequences that splice out of a precursor protein and attach the remaining ends together to form a new protein. When splitting those intein sequence into an N-terminal and a C-terminal split intein one is left with a powerful tool to post-translationally modify whole proteins on the amino-acid sequence level. This construct was designed to express any protein of interest fused to the Nostoc punctiforme DnaE N-terminal split intein.

Assembly Constructs

BBa_K1362101

BBa_K1362101 is the corresponding C-terminal construct to BBa_K1362100. Upon coexpression or mixture of the N- and C-constructs protein splicing takes place and the N- and C-terminal proteins of interest are irreversibly assembled via a newly formed peptide bond.

This mechanism can be applied for a variety of different uses such as the activation of a protein through reconstitution of individually expressed split halves. See our split sfGFP experiment set a foundation that you guys can build on!

Assembly Constructs
Circularization Construct

Sample Data Page for our favorite Parts.

Circularization Construct. BBa_K1362000


Circularization Construct
This part represents an easy way to circularize any protein. In a single step you can clone your protein in the split intein circularization construct. Exteins, RFC [i] standard overhangs and BsaI sites have to be added to the coding sequence of the protein to be circularized without start- and stop codons by PCR. By Golden Gate assembly, the mRFP selection marker has to be replaced with the protein insert. If the distance of the ends of your protein of interest aren't close enough to connect them you will need a linker. BBa_K1362000, the split intein circularization construct, includes a strong T7 RBS (BBa_K1362090), we sent to the parts registry as well, and the split intein Npu DnaE. The T7 RBS derived from the T7 phage gene 10a (major capsid protein).
The resulting plasmid can be used to express the protein of interest with the obligatory linker and the N- and C-intein.
In an autocatalytic in vivo reaction, the circular protein is formed. To read more about the trans-splicing reaction visit our Intein Background page. If corresponding split inteins are added to both termini of a protein, the trans-splicing reaction results in a circular backbone.
Circular proteins offers many advantages. While conserving the functionality of their linear counterpart, circular proteins can be superior in terms of thermostability, resistance against chemical denaturation and protection from exopeptidases. Moreover, a circular backbone can improve in vivo stability of therapeutical proteins and peptides.

Assembly Construct. BBa_K1362100 and BBa_K1362101



Assembly Constructs
These parts represent an easy way to build fusion constructs of intein parts with any protein or peptide of interest (POI). In a single step you can fuse your protein to a split intein part. Desired extein residues, RFC [i] standard overhangs and BsaI sites generating these overhangs have to be added to the coding sequence of the POI by PCR. Facilitating the highly efficient GoldenGate assembly reaction, the mRFP selection marker can be replaced with the POI insert.
The resulting parts can be concatenated using standard BioBrick cloning into an expression backbone to coexpress the POIs fused to a N- and a C-intein.
In an auto catalytic in vivo reaction, the inteins will cleave themselves out and ligate the exteins - here your POIs - together. For example we used this mechanism to reconstitute the fluorescence of split sfGFP . To read more about the trans-splicing reaction visit our Intein Background page. The whole process becomes significant more interesting with conditional protein trans splicing.
If performing experiments with split inteins make sure you always have a non-splicing negative control. Check out our non splicing assembly constructs (with part names ending with 2 or 3) for example: BBa_K1362102 and BBa_K1362103
Circularization Construct

Intein Library.


Inteins are the basic unity of our toolbox. They are integrated as extraneous polypeptide sequences into habitual proteins and do not follow the original protein function. Inteins perform an autocatalytic splicing reaction, where they excite themselves out of the host protein while reconnecting the remaining chains on both end, so called N and C exteins, via a new peptide bond. Read more about it in our project background!

To characterize the different types and groups of split-inteins and inteins we collect many details about them to develop a intein library. It gives you a great and clear overview about the most important facts.

Split intein Special features Size N [aa] Size C [aa] Reaction properties Origin References
Npu DnaEfast; robust at high temperature range and high-yielding trans-splicing activity, well characterised requirements10236t1/2 = 63s , 37°C , k=~1x10^-2 (s^-1); activity range 6 to 37°CS1 natural split intein, Nostoc punctiforme[1] [2]
Ssp DnaXcross-reactivity with other N-inteins, transsplicing in vivo and in vitro, high yields1276k=~1.7x10^-4(s^-1); efficiency 96%engineered from Synechocystis species[3] [4]
Ssp GyrB very short Nint facilitates trans-splicing of synthetic peptides6150k=~1x10^-4(s^-1), efficiency 40-80%S11 split intein enginered from Synechocystis species, strain PCC6803[4] [5]
Ter DnaE3trans-splicing activity with high yields10236k=~2x10^-4(s^-1), efficiency 87%natural split intein, Trichodesmium erythraeum[4] [6]
Ssp DnaBrelatively fastt1/2=12min, 25°C, k=~1x10^-3(s^-1)engineered from Synechocystis species, strain PCC6803[2]
Gp41-1fastes known reaction 8838t1/2=20-30s, 37°C, k=~1.8x10^-1 (s^-1); activity range 0 to 60°Cnatural split intein, Cyanophage[7] [8]

References

[1] Iwai, H., Züger, S., Jin, J. & Tam, P.-H. Highly efficient protein trans-splicing by a naturally split DnaE intein from Nostoc punctiforme. FEBS Lett. 580, 1853–8 (2006).

[2] Zettler, J., Schütz, V. & Mootz, H. D. The naturally split Npu DnaE intein exhibits an extraordinarily high rate in the protein trans-splicing reaction. FEBS Lett. 583, 909–14 (2009).

[3] Song, H., Meng, Q. & Liu, X.-Q. Protein trans-splicing of an atypical split intein showing structural flexibility and cross-reactivity. PLoS One 7, e45355 (2012).

[4] Lin, Y. et al. Protein trans-splicing of multiple atypical split inteins engineered from natural inteins. PLoS One 8, e59516 (2013).

[5] Appleby, J. H., Zhou, K., Volkmann, G. & Liu, X.-Q. Novel Split Intein for trans-Splicing Synthetic Peptide onto C Terminus of Protein. J. Biol. Chem. 284, 6194–6199 (2009).

[6] Liu, X.-Q. & Yang, J. Split dnaE genes encoding multiple novel inteins in Trichodesmium erythraeum. J. Biol. Chem. 278, 26315–8 (2003).

[7] Carvajal-Vallejos, P., Pallissé, R., Mootz, H. D. & Schmidt, S. R. Unprecedented rates and efficiencies revealed for new natural split inteins from metagenomic sources. J. Biol. Chem. 287, 28686–96 (2012).

[8] Dassa, B., London, N., Stoddard, B. L., Schueler-Furman, O. & Pietrokovski, S. Fractured genes: a novel genomic arrangement involving new split inteins and a new homing endonuclease family. Nucleic Acids Res. 37, 2560–73 (2009).

Our Backbones.

Standard BioBrick cloning is a universal way of putting two BioBrick parts together to build a new BioBrick part. Despite several alternative cloning methods allow the assembly of multiple parts at one its simplicity and the broad availability of compatible parts keep it the 'de facto' standard of the iGEM-community.

Using standard BioBrick cloning, the generation of translationally active parts requires often more than one round of cloning. The ability to easily test the functionality of a protein before cloning them into complicated circuits has the potential to prevent many unsuccessful experiments of iGEM teams and may improve the characterization of the parts in the parts registry. However the extra amount of work required to clone such an additional construct may inhibit this behavior. We therefore improved the standard plasmids pSB1X3 and pSB4X5 by inserting a lacI repressible T7 promoter directly upstream to the BioBrick prefix of those plasmids. This promoter is completely inactive in 'E. coli' strains lacking a T7 RNA polymerase such as TOP10 or DH10beta bute inducible in strains carrying the T7 RNA polymerase under a lacI repressible promoter such as DE3 strains. This enables the use of the same backbone for cloning and over expression. Using 3A assembly a translational active part can be cloned from an RBS and a coding part in one step while maintaining the full flexibility of standard BioBrick assembly. These new RFC 10 conform backbones eliminate one cloning step needed for the expression and thus the characterization of a newly BioBricked protein. Version number 30 was claimed for the high copy variants and version number 50 for the low copy variants.

High copy BioBrick expression backbone:

  • pSB1A30(Part:BBa_K1362091): High copy BioBrick cloning/expression backbone carrying Amp resistance
  • pSB1C30(Part:BBa_K1362092): High copy BioBrick cloning/expression backbone carrying Cm resistance
  • pSB1K30(Part:BBa_K1362093): High copy BioBrick cloning/expression backbone carrying Kan resistance
  • pSB1T30(Part:BBa_K1362094): High copy BioBrick cloning/expression backbone carrying Tet resistance

Low copy BioBrick expression backbone:

  • pSB4A50(Part:BBa_K1362095): High copy BioBrick cloning/expression backbone carrying Amp resistance
  • pSB4C50(Part:BBa_K1362096): High copy BioBrick cloning/expression backbone carrying Cm resistance
  • pSB4K50(Part:BBa_K1362097): High copy BioBrick cloning/expression backbone carrying Kan resistance

Because of the great experience we had using our expression vectors, we sent them to the iGEM team Aachen and Tuebingen. We helped them solving their problems with the expression of their products.

Circularization Construct

List of Parts

Loading...

Retrieved from "http://2014.igem.org/Team:Heidelberg/Parts"