Team:UNIPV-Pavia/Project/solution
From 2010.igem.org
(→Tag) |
m (→Integrative standard vector for E. coli) |
||
(5 intermediate revisions not shown) | |||
Line 141: | Line 141: | ||
{| align='center' | {| align='center' | ||
- | |[[Image:pv_curva_od_stilizzata.png| | + | |[[Image:pv_curva_od_stilizzata.png|500px|thumb|center|Figure 9: behaviour of self-inducible device library members. Each device is able to initiate the synthesis of the recombinant protein of interest at a specific cell density.]] |
|} | |} | ||
Line 150: | Line 150: | ||
</html> | </html> | ||
- | =Integrative standard vector for E. coli= | + | =Integrative standard vector for ''E. coli''= |
The integration of the genetic circuits of interest into the microbial host genome can eliminate the need of expensive selection techniques, such as antibiotics or auxotrophic media, in cell cultures. | The integration of the genetic circuits of interest into the microbial host genome can eliminate the need of expensive selection techniques, such as antibiotics or auxotrophic media, in cell cultures. | ||
Line 159: | Line 159: | ||
{|align=center | {|align=center | ||
- | |valign=top|[[Image:k300000.jpg|thumb|500px|center|Figure 10: BioBrick integrative base vector BBa_K300000.]] | + | |valign=top|[[Image:k300000.jpg|thumb|500px|center|Figure 10: BioBrick integrative base vector <partinfo>BBa_K300000</partinfo>.]] |
|[[Image:glossary300000.jpg|thumb|300px|center|Figure 11: Parts notation.]] | |[[Image:glossary300000.jpg|thumb|300px|center|Figure 11: Parts notation.]] | ||
|} | |} | ||
Line 252: | Line 252: | ||
This integration method is applicable when the host strain does not have prophages in the att(Phi80) locus. TOP10 (<partinfo>BBa_V1009</partinfo>) and DH5alpha (<partinfo>BBa_V1001</partinfo>) strains have the Phi80 prophage and so their chromosome cannot be engineered with this procedure. | This integration method is applicable when the host strain does not have prophages in the att(Phi80) locus. TOP10 (<partinfo>BBa_V1009</partinfo>) and DH5alpha (<partinfo>BBa_V1001</partinfo>) strains have the Phi80 prophage and so their chromosome cannot be engineered with this procedure. | ||
- | The genomic integration of the desired BioBrick part into the attP(Phi80) locus has to be mediated by co-transforming a helper plasmid, such as the Amp-resistant <partinfo>BBa_J72008</partinfo> plasmid | + | The genomic integration of the desired BioBrick part into the attP(Phi80) locus has to be mediated by co-transforming a helper plasmid, such as the Amp-resistant <partinfo>BBa_J72008</partinfo> plasmid, which carries the IntPhi80 site-specific integrase gene under the control of a thermoinducible promoter (see Fig.14). The helper plasmid also has a heat-sensitive replication origin, whose replication can be inhibited at temperatures of 37-42°C, while a permissive temperature for this vector is 30°C. For this reason, it can be cured at high temperatures, when the integrase expression is triggered at the same time. |
The Phi80 integrase mediates the site-specific recombination between the attP site in the integrative vector and the attB site in the bacterial genome (for a schematic description of this process, see Fig.15 and http://partsregistry.org/Recombination). | The Phi80 integrase mediates the site-specific recombination between the attP site in the integrative vector and the attB site in the bacterial genome (for a schematic description of this process, see Fig.15 and http://partsregistry.org/Recombination). | ||
Line 291: | Line 291: | ||
Here, a detailed description of the integrative vector for the yeast ''S. cerevisiae'' is reported. | Here, a detailed description of the integrative vector for the yeast ''S. cerevisiae'' is reported. | ||
- | The structure of the designed vector, here named BBa_K300001, is shown in Fig.17. Most of its features have been inspired by the pUG6 plasmid (GenBank: AF298793.1), constructed by [Guldener U et al., 1996]. The parts notation is reported in Fig.18. | + | The structure of the designed vector, here named <partinfo>BBa_K300001</partinfo>, is shown in Fig.17. Most of its features have been inspired by the pUG6 plasmid (GenBank: AF298793.1), constructed by [Guldener U et al., 1996]. The parts notation is reported in Fig.18. |
{|align=center | {|align=center | ||
- | |valign=top|[[Image:k300001base.jpg|thumb|500px|center|Figure 17: BioBrick integrative base vector BBa_K300001.]] | + | |valign=top|[[Image:k300001base.jpg|thumb|500px|center|Figure 17: BioBrick integrative base vector <partinfo>BBa_K300001</partinfo>.]] |
|[[Image:glossary300001.jpg|thumb|300px|center|Figure 18: Parts notation.]] | |[[Image:glossary300001.jpg|thumb|300px|center|Figure 18: Parts notation.]] | ||
|} | |} | ||
Line 375: | Line 375: | ||
<img src="https://static.igem.org/mediawiki/2010/7/74/UNIPV_Pavia_Icona_Bioplastica.GIF" width="75px" height="75px"/></a> | <img src="https://static.igem.org/mediawiki/2010/7/74/UNIPV_Pavia_Icona_Bioplastica.GIF" width="75px" height="75px"/></a> | ||
</html> | </html> | ||
+ | |||
=Self-cleaving affinity tags to easily purify proteins= | =Self-cleaving affinity tags to easily purify proteins= | ||
Conventional affinity-based protein purification methods rely on specific binding of the fusion tag to an immobilized ligand, but they are affected by severe limitations, as explained in the Motivation section. Briefly, they imply the use of expensive proteases for tag removal from the fusion protein, requiring the appropriate aminoacidic sequence to be included between the tag and the target protein. Moreover, the cost of the affinity resins used in the process is far from negligible, especially on industrial scale. | Conventional affinity-based protein purification methods rely on specific binding of the fusion tag to an immobilized ligand, but they are affected by severe limitations, as explained in the Motivation section. Briefly, they imply the use of expensive proteases for tag removal from the fusion protein, requiring the appropriate aminoacidic sequence to be included between the tag and the target protein. Moreover, the cost of the affinity resins used in the process is far from negligible, especially on industrial scale. | ||
Line 421: | Line 422: | ||
---- | ---- | ||
- | Thus, it is possible to create an engineered protein purification system that uses the tag construct and relies on Intein self-cleaving capabilities. | + | Thus, it is possible to create an engineered protein purification system that uses the tag construct and relies on Intein self-cleaving capabilities. Fig.24 shows a generic purification tag, composed by Phasins and Intein, as an example. |
- | [[Image:UNIPV10_generic_purification.jpg|thumb|400px|center|Figure | + | [[Image:UNIPV10_generic_purification.jpg|thumb|400px|center|Figure 24: Generic purification system.]] |
Protein purification takes place as follows: | Protein purification takes place as follows: | ||
- | :1. Affinity tag (and consequently fused protein) binding to PolyHydroxyAlkanoates. | + | :1. Affinity tag (and consequently fused protein) binding to PolyHydroxyAlkanoates (Fig.25). |
- | [[Image:UNIPV10_binding_activity.png|thumb|400px|center|Figure | + | [[Image:UNIPV10_binding_activity.png|thumb|400px|center|Figure 25: ''In vivo'' binding activity.]] |
:2. Cells lysis. | :2. Cells lysis. | ||
:3. Recovery of the fused protein, bound with PHA granules, by centrifugation. | :3. Recovery of the fused protein, bound with PHA granules, by centrifugation. | ||
- | :4. Elution | + | :4. Elution in the supernatant of the target protein by Intein cleavage through a pH or heat stimulus (Fig.26). |
- | [[Image:UNIPV10_purification_step.png|thumb|150px|center|Figure | + | [[Image:UNIPV10_purification_step.png|thumb|150px|center|Figure 26: Purification.]] |
Latest revision as of 17:20, 26 October 2010
|
Several solutions were explored in this project to potentially improve the industrial production of recombinant proteins. Self-inducible promoters were considered to avoid the usage of inducible systems especially in large-scale industrial bioprocesses, in which protein production has to be triggered by expensive inducer molecules. Standard and user friendly integrative vectors for E. coli and S. cerevisiae were designed to stably integrate the expression systems of interest in the microbial host genome and to eliminate the need of expensive selection techniques, such as antibiotics or auxotrophic media. Finally, an "in-cell" protein purification system was implemented using BioBrick parts: PolyHydroxyAlkanoate (PHA) granules were used as a substrate for PHA-binding peptides (Phasins) fused to the target protein, while a pH-based self-cleaving peptide (Intein) was used instead of a protease cleavage site. This solution can thus replace the usage of expensive affinity resins/columns and proteases.
Thus, these BioBrick parts can be used to express recombinant proteins without adding an inducer to trigger the transcription initiation of downstream genes; in large-scale production of such proteins this strategy can be cost saving and ease the entire process. Users can rationally choose the cell density at which the initiation has to occur by selecting a self-inducible device library member.
Integrative standard vector for E. coliThe integration of the genetic circuits of interest into the microbial host genome can eliminate the need of expensive selection techniques, such as antibiotics or auxotrophic media, in cell cultures. In order to simplify the engineering of the host genome, two standard and modular integrative vectors have been designed for Escherichia coli and Saccharomyces cerevisiae, two commonly used hosts for industrial protein production. Here, a detailed description of the integrative vector for E. coli is reported, while the following section deals with the integrative vector for yeast. The parts notation is reported in Fig.11.
This vector can be considered as a base vector, which can be specialized to target the desired integration site in the host genome. The default version of this backbone has the bacteriophage Phi80 attP (<partinfo>BBa_K300991</partinfo>) as integration site. This vector enables multiple integrations in different positions of the same genome.
GlossaryThe passenger is the desired DNA part to be integrated into the genome. The guide is the DNA sequence that is used to target the passenger into a specific locus in the genome.
Design featuresThe main design features for vector engineering and for the genome integration of the vector are reported below. Vector engineering features:
Genome integration features:
How to use it<partinfo>BBa_K300000</partinfo> can be:
How to propagate it before performing genome integrationThe default version of this vector contains the <partinfo>BBa_I52002</partinfo> insert, so it *must* be propagated in a ccdB-tolerant strain such as DB3.1 (<partinfo>BBa_V1005</partinfo>). After the insertion of the desired BioBrick part in the cloning site, this vector does not contain a standard replication origin anymore, so it *must* be propagated in a pir+ or pir-116 strain such as BW25141 (<partinfo>BBa_K300984</partinfo>) or BW23474 (<partinfo>BBa_K300985</partinfo>) that can replicate the R6K conditional origin (<partinfo>BBa_J61001</partinfo>).
How to engineer itThe DNA guide can be changed as follows:
How to perform genome integrationThe integration into the E. coli chromosome can exploit the bacteriophage attP-mediated integration or the homologous recombination. Detailed protocols about attP-mediated integration can be found here:
Detailed protocols about homologous recombination can be found here:
This integration method is applicable when the host strain does not have prophages in the att(Phi80) locus. TOP10 (<partinfo>BBa_V1009</partinfo>) and DH5alpha (<partinfo>BBa_V1001</partinfo>) strains have the Phi80 prophage and so their chromosome cannot be engineered with this procedure. The genomic integration of the desired BioBrick part into the attP(Phi80) locus has to be mediated by co-transforming a helper plasmid, such as the Amp-resistant <partinfo>BBa_J72008</partinfo> plasmid, which carries the IntPhi80 site-specific integrase gene under the control of a thermoinducible promoter (see Fig.14). The helper plasmid also has a heat-sensitive replication origin, whose replication can be inhibited at temperatures of 37-42°C, while a permissive temperature for this vector is 30°C. For this reason, it can be cured at high temperatures, when the integrase expression is triggered at the same time. The Phi80 integrase mediates the site-specific recombination between the attP site in the integrative vector and the attB site in the bacterial genome (for a schematic description of this process, see Fig.15 and http://partsregistry.org/Recombination). Thanks to its R6K conditional replication origin, the integrative vector cannot be replicated in common E. coli strains, so the Chloramphenicol resistant bacteria are actual integrants. In the Materials and Methods section (https://2010.igem.org/Team:UNIPV-Pavia/Project/results), a detailed protocol to target the desired BioBrick part into the Phi80 locus is reported. How to perform multiple integrations in the same genomeWhen this vector is integrated in the genome, the desired passenger should be maintained into the host, as well as the Chloramphenicol resistance marker and the R6K conditional replication origin. The CmR and the R6K can be excised from the genome by exploiting the two FRT recombination sites that flank them. The Flp recombinase protein mediates this recombination event (for a schematic description of this process, see Fig.16 and http://partsregistry.org/Recombination), so it has to be expressed by a helper plasmid, such as pCP20 (CGSC#7629). This enables the sequential integration of several parts using the same antibiotic resistance marker, which can be each time eliminated.
Detailed protocols about homologous recombination can be found here:
Integrative standard vector for yeastHere, a detailed description of the integrative vector for the yeast S. cerevisiae is reported. The structure of the designed vector, here named <partinfo>BBa_K300001</partinfo>, is shown in Fig.17. Most of its features have been inspired by the pUG6 plasmid (GenBank: AF298793.1), constructed by [Guldener U et al., 1996]. The parts notation is reported in Fig.18. This is an integrative vector which can be used to insert the desired RFC10-compatible BioBrick parts/devices/systems into the genome of S. cerevisiae. This vector can also be specialized to target the desired integration site in the host genome. The default version of this backbone targets the Gal system of the S288C strain (<partinfo>BBa_K300979</partinfo>) through the two homologous regions <partinfo>BBa_K300986</partinfo> and <partinfo>BBa_K300987</partinfo>. The Gal system is not essential for yeast survival if the strain is grown on carbon sources other than galactose. This vector enables multiple integrations in different positions of the same genome. The usage of the KanMX dominant selection marker can avoid the usage of auxotrophic markers. In the industrial framework auxotrophies are usually deleterious for the process productivity because they affect the growth rate of cells. For this reason, this vector can be a concrete solution for the design of industrial yeast strains with novel user-defined functions.
GlossaryA HR (Homologous Region) is a sequence that can recombine with the host genome. As explained for the integrative vector for E. coli, the passenger is the desired DNA part to be integrated into the genome. Design featuresThis vector backbone was designed as a modular integrative vector for S. cerevisiae. In this section, the main design features for vector engineering and for the genome integration of the vector are reported.
How to use it<partinfo>BBa_K300001</partinfo> can be:
How to propagate it before performing genome integrationThis vector can be easily propagated in E. coli thanks to the high-copy replication origin and the Ampicillin resistance selection marker, both derived from the <partinfo>pSB1A2</partinfo> vector backbone.
How to integrate a BioBrick into the yeast genome
Users can change the integration site by engineering the vector: <partinfo>BBa_K300986</partinfo> and <partinfo>BBa_K300987</partinfo> are flanked by two AvrII and two NheI respectively and for this reason the two Homologous Regions can be excided. New homologous sequences compatible with RFC10 can be digested with XbaI-SpeI and assembled because AvrII, NheI, XbaI and SpeI have compatible sticky ends. Note that this assembly is not directional and the correct orientation can be validated through sequencing with standard VF2 and VR primers.
How to perform the KanMX marker excisionThe KanMX dominant selection marker is flanked by two loxP recombination sites and for this reason it can be excided upon Cre recombinase activity (Fig.22). The Cre recombinase has to be expressed by a helper plasmid.
Self-cleaving affinity tags to easily purify proteinsConventional affinity-based protein purification methods rely on specific binding of the fusion tag to an immobilized ligand, but they are affected by severe limitations, as explained in the Motivation section. Briefly, they imply the use of expensive proteases for tag removal from the fusion protein, requiring the appropriate aminoacidic sequence to be included between the tag and the target protein. Moreover, the cost of the affinity resins used in the process is far from negligible, especially on industrial scale. The use of self-cleaving protein elements coupled with innovative affinity tags has been recently proposed to overcome these limitations. For all these reasons, in this section a technique compliant to the BioBrick assembly standard and based on self-splicing affinity tags derived from the fusion of Phasins, Inteins and a short flexible linker is proposed. TagPhasinPhasins are proteins involved in formation and stabilization of PolyHydroxyAlkanoates (PHA), intracytoplasmic inclusions in microorganisms like Ralstonia eutropha which serve as carbon and energy storage. As such, Phasins exhibit highly specific binding to PHA granules and can be used to create tags for proteins, while PHB can be used as the affinity matrix. In literature, it has also been shown that the Phasin-tagged fusion protein's affinity with PHA granules can be improved by increasing the number of Phasins in the fusion protein. The Ralstonia eutropha‘s Phasin coding sequence, <partinfo>K208001</partinfo>, was already present in the Registry in Silver standard. However, at the end of this gene there was a TGA stop codon which prevents the usage of this Phasin as a head or internal domain. In order to overcome this problem, <partinfo>K208001</partinfo> has been improved for fusion protein applications by mutagenesis through PCR using custom primers. Two new BioBrick parts were built and submitted to the Registry:
These two new parts allow the construction of composite synthetic affinity tags, built by assembling an arbitrary number of Phasins (it has been shown that a better affinity is achieved by fusing of two or more Phasins). In this work a flexible linker sequence (<partinfo>BBa_K105012</partinfo>) that connects the Phasins has also been used in order to test if it can improve or facilitate the binding and folding of the tag. PHA productionPHA production in R. eutropha is achieved by the PhaCAB operon, which contains three genes, phbC, phbA and phbB, each encoding for an enzyme essential for the formation of polyhydroxybutyrate (PHB, a kind of polyhydroxyalkanoate) inclusions. In literature, the production of PHB has already been achieved in E. coli by incorporating the PhaCAB operon. The PHB granules produced by engineered E. coli can be used as an affinity matrix for Phasin-based affinity tags and the binding of the Phasin-tagged protein of interest can occur in vivo. Several parts for PHB production are present in the Registry: in the past iGEM editions, the Duke (2008 and 2009), Hawaii (2008), Tsinghua (2008), Virginia (2008) teams worked on it and submitted a set of BioBrick parts for PHB synthesis. However, the complete phaCAB operon is not available in the Registry. Because a lot of work about PHB has already been done and because our short term goal was not to optimize the PHB granules productions, an existing engineered E. coli strain able to produce PHB was used as a proof-of-concept affinity matrix producer. This strain comes from the DSMZ public collection and is named DMSZ15372. Taking advantage of the natural affinity of Phasins to PHB, it is possible to engineer strains in which PHB and the Phasin-tagged protein of interest are co-produced and the binding can occur. The overall yield and specificity of the process depends on the structure of the Phasin-based tags, which can be easily constructed or modified by using BioBrick parts compatible with the common RFC10 and RFC23 standards to perform in-frame assemblies. For this reason these tags are modular and can be freely expanded; a generic one is shown in Fig.23. Protein purification systemPhasins and PHB granules can replace the common affinity tags and matrix respectively. However, expensive proteases are still essential to remove the tag after the Phasins-PHB binding. A novel engineered inducible Intein can be used to complete the purification process by removing the affinity tag, thus replacing proteases. InteinInteins (Intervening Proteins) are sequences capable of self-exciding from a precursor protein through a process known as self-splicing, forming a peptide bond between the flanking proteins (exteins). Many so-called mini-Inteins have been engineered, whose key feature is the capability to completely release a flanking extein (the target protein) in response to a simple stimulus, either chemical or physical, with no need of expensive proteases. In literature, one mini-Intein was obtained through mutagenesis of Mycobacterium tuberculosis Mtu RecA Intein. The sequence of this Intein, referred to as ΔI-CM, allows for pH/heat-controlled C-terminal cleavage. Thanks to this feature, the ΔI-CM Intein can be fused downstream of an affinity tag and upstream of the protein coding sequence of interest in order to enable a cheap cleavage process to remove the N-terminal tag. In this project, the ΔI-CM Intein sequence was designed according to [Wood DW et al., 1999] and codon-optimized for E. coli to yield <partinfo>BBa_K300004</partinfo>. This part was designed as an internal domain (prefix and suffix compatible with Silver standard) in order to enable protein coding sequence assemblies to generate the desired synthetic self-cleavable affinity tags for protein purification. Thus, it is possible to create an engineered protein purification system that uses the tag construct and relies on Intein self-cleaving capabilities. Fig.24 shows a generic purification tag, composed by Phasins and Intein, as an example. Protein purification takes place as follows:
|