Team:UIUC-Illinois/Project

From 2011.igem.org

(Difference between revisions)
(Prototype team page)
 
(19 intermediate revisions not shown)
Line 1: Line 1:
-
<!-- *** What falls between these lines is the Alert Box!  You can remove it from your pages once you have read and understood the alert *** -->
+
{{Template:UIUC Illinois Header}}
-
 
+
<html>
<html>
-
<div id="box" style="width: 700px; margin-left: 137px; padding: 5px; border: 3px solid #000; background-color: #fe2b33;">
+
    <!--Define Start-->  
-
<div id="template" style="text-align: center; font-weight: bold; font-size: large; color: #f6f6f6; padding: 5px;">
+
 
-
This is a template page. READ THESE INSTRUCTIONS.
+
    <div id="define-block">
-
</div>
+
 
-
<div id="instructions" style="text-align: center; font-weight: normal; font-size: small; color: #f6f6f6; padding: 5px;">
+
      <div class="title"><center>E. chiver</center></div>
-
You are provided with this team page template with which to start the iGEM season. You may choose to personalize it to fit your team but keep the same "look." Or you may choose to take your team wiki to a different level and design your own wiki.  You can find some examples <a href="https://2008.igem.org/Help:Template/Examples">HERE</a>.
+
 
-
</div>
+
    </div>
-
<div id="warning" style="text-align: center; font-weight: bold; font-size: small; color: #f6f6f6; padding: 5px;">
+
 
-
You <strong>MUST</strong> have a team description page, a project abstract, a complete project description, a lab notebook, and a safety page.  PLEASE keep all of your pages within your teams namespace. 
+
    <!--Define End-->  
-
</div>
+
 
-
</div>
+
    <!--Content Start-->  
 +
 
 +
    <div class="core-content-block">  
 +
 
 +
      <div id="core-content-block-t2r-left">  
</html>
</html>
 +
{{Template:UIUC Illinois ProjectNav}}
-
<!-- *** End of the alert box *** -->
+
{{Template:UIUC Illinois WhoWeAre}}
 +
<html>
 +
      </div>
-
{|align="justify"
+
      <div id="core-content-block-t2r-right">
-
|You can write a background of your team here.  Give us a background of your team, the members, etc.  Or tell us more about something of your choosing.
+
-
|[[Image:UIUC-Illinois_logo.png|200px|right|frame]]
+
-
|-
+
-
|
+
-
''Tell us more about your project.  Give us background.  Use this is the abstract of your project.  Be descriptive but concise (1-2 paragraphs)''
+
-
|[[Image:UIUC-Illinois_team.png|right|frame|Your team picture]]
+
-
|-
+
-
|
+
-
|align="center"|[[Team:UIUC-Illinois | Team Example]]
+
-
|}
+
-
<!--- The Mission, Experiments --->
+
        <div class="desc">Track Selection: New Application</div>
-
{| style="color:#1b2c8a;background-color:#0c6;" cellpadding="3" cellspacing="1" border="1" bordercolor="#fff" width="62%" align="center"
+
        <div class="title">Abstract</div>
-
!align="center"|[[Team:UIUC-Illinois|Home]]
+
-
!align="center"|[[Team:UIUC-Illinois/Team|Team]]
+
-
!align="center"|[https://igem.org/Team.cgi?year=2010&team_name=UIUC-Illinois Official Team Profile]
+
-
!align="center"|[[Team:UIUC-Illinois/Project|Project]]
+
-
!align="center"|[[Team:UIUC-Illinois/Parts|Parts Submitted to the Registry]]
+
-
!align="center"|[[Team:UIUC-Illinois/Modeling|Modeling]]
+
-
!align="center"|[[Team:UIUC-Illinois/Notebook|Notebook]]
+
-
!align="center"|[[Team:UIUC-Illinois/Safety|Safety]]
+
-
!align="center"|[[Team:UIUC-Illinois/Attributions|Attributions]]
+
-
|}
+
 +
        <div class="desc">Our project, E. chiver, drew inspiration from the commonly used CRIM system, a series of plasmids that allows the user to integrate constructs into lambdoid phage sites common to many bacterial chromosomes.  Our E. chiver system adds several elements yielding new applications.  Our team designed two E. chiver constructs utilizing Lambda and P21 machinery.  Each can in theory be used to shuttle a plasmid construct between two forms:  a single chromosomal insert and a high copy number plasmid.  In their current designs the systems must function separately, but possible routes have been identified by our team to make the co-functioning of these systems possible.  We can see elements of our project being used in drug delivery systems as a method to keep a gene of interest dormant unless in the correct condition/location, and with further exploration into the co-functioning routes it may be used to create a ‘bacterial filing cabinet’.</div>
 +
        <div class="title">Project Goal:</div>
 +
        <div class="desc">To create a system that allows a construct to be expressed at a high copy number when induced, but then file back into the chromosome as a stable integrant for energetically favorable storage. The ultimate end goal is to create a bacterial filing system, E. chiver, which allows the coexistence of multiple constructs with their copy number and integration tied to a unique inducer.</div>
-
== '''Overall project''' ==
+
        <div class="title">Illustrative Overview of Goal:</div>
-
Your abstract
+
        <div class="desc"><center><img src="https://static.igem.org/mediawiki/2011/4/43/Uiuc_general_goal.jpg" /></center></div>
 +
        <div class="title">Analogy:</div>
 +
        <div class="desc">
 +
          <p>A simple analogy for our E. chiver project is a filing cabinet.  The following are the basic components of the system and their workplace analogues.</p>
 +
          <p>Construct = Shuttle Plasmid = File</p>
 +
          <p>Gene of interest = File Contents</p>
 +
          <p>Chromosome = Filing Cabinet</p>
-
== Project Details==
+
        </div>
 +
        <div class="title">Background/Tools:</div>
 +
        <div class="desc">
 +
          <p>Luckily for us, the basic machinery we need for our E. chiver design already exists.  The machinery is that of the Lambdiod phage family (i.e. λ, P21, P22, HK022, φ80), as well as the conditional R6K origin of replication and its trans-acting factor pir. The following are basic descriptions of how these parts function. </p>
 +
          <p>Lambdoid phage machinery:  Our main interest is the phage proteins excisionase (Xis) and integrase (Int), as well as the phage genetic element attP (phage attachment site) and the bacterial genetic element attB (bacterial attachment site).  Xis and Int are responsible for the site-specific recombination event between attP and attB.  The recombination event is reversible. The direction depends on the combination of proteins being expressed (see diagram below).</p>
-
=== Part 2 ===
+
        </div>
 +
        <div class="desc"><center><img src="https://static.igem.org/mediawiki/2011/8/89/Uiuc_plasmid_integration.jpg" /></center></div>
 +
        <div class="desc">
 +
          <p>R6K origin and pir:  The <i>pir</i> gene encodes the trans-acting protein that allows replication of an R6K origin2.  When pir is turned on, a plasmid containing the R6K origin will be allowed to replicate, but when pir is not expressed the plasmid becomes a suicide vector (cannot replicate).  The CRIM system takes advantage of this by placing an attP site in the R6K vector.  When pir is off, the vector must insert into the chromosome or be lost.</p>
 +
        </div>
-
=== The Experiments ===
+
        <div class="desc"><center><img src="https://static.igem.org/mediawiki/2011/e/e9/Uiuc_pir_state.jpg" /></center></div>
 +
        <div class="desc">
 +
          <p>CRIM (Conditional-Replication, Integration, Modular) plasmids utilize these factors and provide the current means of shuttling a construct into and out of a bacterial chromosome1.  However, the design of this system requires manual labor in the form of helper plasmid transformations and subsequent selection procedures each time we wish to excise or integrate our construct (see below figure).  In our design we rewire the CRIM machinery to place the integration and excision events under chemical inducers to eliminate this manual process.  To tie back into the filing cabinet analogy, we are reworking the system to make the process of removing and replacing a file easier, and taking the first step toward allowing this system to be utilized outside of the laboratory by placing the filing system under environmental signals rather than laboratory procedures.</p>
 +
        </div>
-
=== Part 3 ===
+
        <div class="desc"><center><img src="https://static.igem.org/mediawiki/2011/5/5f/Uiuc_integration_scenario.jpg" /></center></div>
 +
        <div class="desc"><center><img src="https://static.igem.org/mediawiki/2011/7/74/Uiuc_plasmid_excision.jpg" /></center></div>
 +
        <div class="desc">
 +
          <p><i>Caption: The CRIM system uses phage machinery placed on helper plasmids to promote integration and excision events.  Preparation of competent cells, transformation of the appropriate helper plasmid, and a multi-step selection process must be performed for each integration and excision event.  The helper plasmids contain a temperature sensitive origin (oriR101) and may be cured via 37C incubation.</i></p>
-
== Results ==
+
        </div>
 +
 
 +
        <div class="title">The Design:</div>
 +
 
 +
        <div class="desc">
 +
 
 +
          <p>The design of our E. chiver system seeks to obtain the following goals:  1) Link integration, excision, and replication of the construct (file) to the presence or absence of a chemical inducer.  2) Allow for modularity of the chemical inducer and gene of interest (file contents).  3) Ensure energetically favorable storage of construct by integration as a single copy (avoid multiple integration events).  4) Enable the system to report which machinery is being expressed.  5) Ultimately allow for the coexistence of multiple files to create a bacterial filing cabinet.</p>
 +
 
 +
          <p>A single File contains two major components</p>
 +
 
 +
          <div class="indent">
 +
 
 +
            <p><b>Shuttle Construct (File) </b></p>
 +
 
 +
            <p>This is the plasmid that shuttles in and out of the chromosome.  It contains the following elements:</p>
 +
 
 +
            <p><i>R6K Origin</i>, for control over replication (see <i>pir</i> component)</p>
 +
 
 +
            <p><i>attP site</i>, for integration into chromosome in absence of inducer</p>
 +
 
 +
            <p><i>Modular Biobrick site</i>, for choosing the controlling chemical inducer and for insertion of the gene of interest <b>(File Contents)</b></p>
 +
 
 +
            <p><i>pir gene</i> (controlled by inducer), for replication of shuttle construct during presence of inducer</p>
 +
 
 +
            <p><i>CI repressor</i> (controlled by inducer), for repression of Integrase machinery (see helper construct) during presence of chemical inducer</p>
 +
 
 +
            <p><i>Reversed Constitutive Promoter</i>, for repression of Integrase machinery after initial integration event (absence of inducer).  This element is essential for addressing goal 3, avoiding multiple integration events.</p>
 +
 
 +
            <p><b>Helper Construct (Filing Cabinet):</b></p>
 +
 
 +
            <p>This is a modified chromosomal attB site. Our E. chiver strain must have genetically engineered attB sites in order to function.  The construct contains the following elements:</p>
 +
 
 +
            <p>Xis/Int/RFP operon (under chemical inducer), for excision of an integrated construct during the presence of the inducer.  As soon as the construct is excised, however, this operon is switched off.</p>
 +
 
 +
            <p>CI repressor, which is under the control of the shuttle construct’s Reversed Constitutive Promoter only when the shuttle construct is integrated.  The CI repressor, in this situation, acts to turn off the adjacent integrase machinery to prevent multiple integrations (see goal 3).</p>
 +
 
 +
            <p>CI Promoter/Int/YFP, for expression of the integration machinery under the conditions that 1) no inducer is present, AND 2) no shuttle construct is integrated.</p>
 +
 
 +
          </div>
 +
 
 +
            <p>For our example of a single file design (addressing goals 1-4) we used lambda phage machinery.  However, any Lambdoid phage machinery can be by replaced into this system in order to change the site of chromosomal integration.  Follow the link below for a walk through of our single file design and an explanation of how it obtains goals 1-4.</p>
 +
 
 +
            <p>Our design addressing goal 5, allowing for multiple files to coexist (a true filing cabinet), was explored by adding an analogous second filing system under the control of P21 phage machinery and the conditional replication of origin OriV to our original Lambda system.  The other difference in this P21 construct is the use of the CII repressor to repress the P21 integrase gene when appropriate.  In order to create a multi-file system each analogous construct (file) must have 1) a unique origin of replication, 2) a separate Lambdoid phage system whose activity does not overlap with other Lambdoid phage sites (i.e. the combination of HK022 and Lambda phage files is not recommended because HK022 recognizes Lambda attachment sites as well as it’s own), 3) no two files may have their helper construct integrase gene under the same repressor (i.e. lambda system utilizes cI while P21 system utilizes cII).  These three requirements are necessary to prevent crosstalk between two files.  Click on the link below to view a walk through of the multi-file, Lambda and P21, system. </p>
 +
 
 +
        <div class="title">References</div>
 +
 
 +
          <p>1. Haldimann, A., Wanner, B. L. 2001. Conditional-Replication, Integration, Excision, and Retrieval Plasmid-Host Systems for Gene Structure-Function Studies of Bacteria. Journal of Bacteriology. 183:21 6384-6393. 2. Metcalf, W. W., Weihong, J., Wanner, B. L. 1994. Use of the rep technique for allele replacement to construct new Escherichia coli hosts for maintenance of R6Kϒ origin plasmids at different copy numbers. Gene. 138: 1-7.</p>
 +
 
 +
          <p>2. Metcalf, W. W., Weihong, J., Wanner, B.  L.  1994.  Use of the rep technique for allele replacement to construct new Escherichia coli hosts for maintenance of R6Kϒ origin plasmids at different copy numbers.  Gene.  138:  1-7.</p>
 +
 
 +
        </div>
 +
 
 +
      </div>
 +
 
 +
    </div>
 +
 
 +
    <!--Content End-->
 +
</html>
 +
{{Template:UIUC Illinois Footer}}

Latest revision as of 04:19, 29 September 2011

University of Illinois iGEM Team
E. chiver
Project Navigation

Who We Are
Amanda Chang
"A watched gel never runs"
Track Selection: New Application
Abstract
Our project, E. chiver, drew inspiration from the commonly used CRIM system, a series of plasmids that allows the user to integrate constructs into lambdoid phage sites common to many bacterial chromosomes. Our E. chiver system adds several elements yielding new applications. Our team designed two E. chiver constructs utilizing Lambda and P21 machinery. Each can in theory be used to shuttle a plasmid construct between two forms: a single chromosomal insert and a high copy number plasmid. In their current designs the systems must function separately, but possible routes have been identified by our team to make the co-functioning of these systems possible. We can see elements of our project being used in drug delivery systems as a method to keep a gene of interest dormant unless in the correct condition/location, and with further exploration into the co-functioning routes it may be used to create a ‘bacterial filing cabinet’.
Project Goal:
To create a system that allows a construct to be expressed at a high copy number when induced, but then file back into the chromosome as a stable integrant for energetically favorable storage. The ultimate end goal is to create a bacterial filing system, E. chiver, which allows the coexistence of multiple constructs with their copy number and integration tied to a unique inducer.
Illustrative Overview of Goal:
Analogy:

A simple analogy for our E. chiver project is a filing cabinet. The following are the basic components of the system and their workplace analogues.

Construct = Shuttle Plasmid = File

Gene of interest = File Contents

Chromosome = Filing Cabinet

Background/Tools:

Luckily for us, the basic machinery we need for our E. chiver design already exists. The machinery is that of the Lambdiod phage family (i.e. λ, P21, P22, HK022, φ80), as well as the conditional R6K origin of replication and its trans-acting factor pir. The following are basic descriptions of how these parts function.

Lambdoid phage machinery: Our main interest is the phage proteins excisionase (Xis) and integrase (Int), as well as the phage genetic element attP (phage attachment site) and the bacterial genetic element attB (bacterial attachment site). Xis and Int are responsible for the site-specific recombination event between attP and attB. The recombination event is reversible. The direction depends on the combination of proteins being expressed (see diagram below).

R6K origin and pir: The pir gene encodes the trans-acting protein that allows replication of an R6K origin2. When pir is turned on, a plasmid containing the R6K origin will be allowed to replicate, but when pir is not expressed the plasmid becomes a suicide vector (cannot replicate). The CRIM system takes advantage of this by placing an attP site in the R6K vector. When pir is off, the vector must insert into the chromosome or be lost.

CRIM (Conditional-Replication, Integration, Modular) plasmids utilize these factors and provide the current means of shuttling a construct into and out of a bacterial chromosome1. However, the design of this system requires manual labor in the form of helper plasmid transformations and subsequent selection procedures each time we wish to excise or integrate our construct (see below figure). In our design we rewire the CRIM machinery to place the integration and excision events under chemical inducers to eliminate this manual process. To tie back into the filing cabinet analogy, we are reworking the system to make the process of removing and replacing a file easier, and taking the first step toward allowing this system to be utilized outside of the laboratory by placing the filing system under environmental signals rather than laboratory procedures.

Caption: The CRIM system uses phage machinery placed on helper plasmids to promote integration and excision events. Preparation of competent cells, transformation of the appropriate helper plasmid, and a multi-step selection process must be performed for each integration and excision event. The helper plasmids contain a temperature sensitive origin (oriR101) and may be cured via 37C incubation.

The Design:

The design of our E. chiver system seeks to obtain the following goals: 1) Link integration, excision, and replication of the construct (file) to the presence or absence of a chemical inducer. 2) Allow for modularity of the chemical inducer and gene of interest (file contents). 3) Ensure energetically favorable storage of construct by integration as a single copy (avoid multiple integration events). 4) Enable the system to report which machinery is being expressed. 5) Ultimately allow for the coexistence of multiple files to create a bacterial filing cabinet.

A single File contains two major components

Shuttle Construct (File)

This is the plasmid that shuttles in and out of the chromosome. It contains the following elements:

R6K Origin, for control over replication (see pir component)

attP site, for integration into chromosome in absence of inducer

Modular Biobrick site, for choosing the controlling chemical inducer and for insertion of the gene of interest (File Contents)

pir gene (controlled by inducer), for replication of shuttle construct during presence of inducer

CI repressor (controlled by inducer), for repression of Integrase machinery (see helper construct) during presence of chemical inducer

Reversed Constitutive Promoter, for repression of Integrase machinery after initial integration event (absence of inducer). This element is essential for addressing goal 3, avoiding multiple integration events.

Helper Construct (Filing Cabinet):

This is a modified chromosomal attB site. Our E. chiver strain must have genetically engineered attB sites in order to function. The construct contains the following elements:

Xis/Int/RFP operon (under chemical inducer), for excision of an integrated construct during the presence of the inducer. As soon as the construct is excised, however, this operon is switched off.

CI repressor, which is under the control of the shuttle construct’s Reversed Constitutive Promoter only when the shuttle construct is integrated. The CI repressor, in this situation, acts to turn off the adjacent integrase machinery to prevent multiple integrations (see goal 3).

CI Promoter/Int/YFP, for expression of the integration machinery under the conditions that 1) no inducer is present, AND 2) no shuttle construct is integrated.

For our example of a single file design (addressing goals 1-4) we used lambda phage machinery. However, any Lambdoid phage machinery can be by replaced into this system in order to change the site of chromosomal integration. Follow the link below for a walk through of our single file design and an explanation of how it obtains goals 1-4.

Our design addressing goal 5, allowing for multiple files to coexist (a true filing cabinet), was explored by adding an analogous second filing system under the control of P21 phage machinery and the conditional replication of origin OriV to our original Lambda system. The other difference in this P21 construct is the use of the CII repressor to repress the P21 integrase gene when appropriate. In order to create a multi-file system each analogous construct (file) must have 1) a unique origin of replication, 2) a separate Lambdoid phage system whose activity does not overlap with other Lambdoid phage sites (i.e. the combination of HK022 and Lambda phage files is not recommended because HK022 recognizes Lambda attachment sites as well as it’s own), 3) no two files may have their helper construct integrase gene under the same repressor (i.e. lambda system utilizes cI while P21 system utilizes cII). These three requirements are necessary to prevent crosstalk between two files. Click on the link below to view a walk through of the multi-file, Lambda and P21, system.

References

1. Haldimann, A., Wanner, B. L. 2001. Conditional-Replication, Integration, Excision, and Retrieval Plasmid-Host Systems for Gene Structure-Function Studies of Bacteria. Journal of Bacteriology. 183:21 6384-6393. 2. Metcalf, W. W., Weihong, J., Wanner, B. L. 1994. Use of the rep technique for allele replacement to construct new Escherichia coli hosts for maintenance of R6Kϒ origin plasmids at different copy numbers. Gene. 138: 1-7.

2. Metcalf, W. W., Weihong, J., Wanner, B. L. 1994. Use of the rep technique for allele replacement to construct new Escherichia coli hosts for maintenance of R6Kϒ origin plasmids at different copy numbers. Gene. 138: 1-7.

Retrieved from "http://2011.igem.org/Team:UIUC-Illinois/Project"