Difference between revisions of "Team:GreatBay China/Part Collection"

 
Line 11: Line 11:
 
   ================================================== -->
 
   ================================================== -->
 
<meta charset="utf-8">
 
<meta charset="utf-8">
−
   <!--[if lt IE 9]>
+
    
−
    <script src="http://html5shim.googlecode.com/svn/trunk/html5.js"></script>
+
−
  <![endif]-->
+
−
  <!-- Mobile Specific Metas
+
−
  ================================================== -->
+
 
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=0">
 
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=0">
 
<!-- css bootstrap -->
 
<!-- css bootstrap -->
 
<link rel="stylesheet" type="text/css" href="https://2018.igem.org/wiki/index.php?title=Template:GreatBay_China/css/bootstrap.css&amp;action=raw&amp;ctype=text/css" />
 
<link rel="stylesheet" type="text/css" href="https://2018.igem.org/wiki/index.php?title=Template:GreatBay_China/css/bootstrap.css&amp;action=raw&amp;ctype=text/css" />
 
<!-- js jquery -->
 
<!-- js jquery -->
−
<script type="text/javascript" src="https://2018.igem.org/wiki/index.php?title=Template:GreatBay_China/js/jquery.min.js&amp;action=raw&amp;ctype=text/javascript"></script>
+
<script type="text/javascript" src="https://2018.igem.org/wiki/index.php?title=Template:GreatBay_China/js/jquery.min.js&action=raw&ctype=text/javascript"></script>
−
  <link rel="stylesheet" href="https://cdn.bootcss.com/bootstrap/3.3.7/css/bootstrap.min.css">
+
<script type="text/javascript" src="https://2018.igem.org/wiki/index.php?title=Template:GreatBay_China/bootstrap/3.3.7/js/bootstrap.min.js&action=raw&ctype=text/javascript"></script>
−
  <script src="https://cdn.bootcss.com/jquery/2.1.1/jquery.min.js"></script>
+
−
  <script src="https://cdn.bootcss.com/bootstrap/3.3.7/js/bootstrap.min.js"></script>
+
 
<!-- js menu -->
 
<!-- js menu -->
 
<script type="text/javascript">
 
<script type="text/javascript">
Line 58: Line 52:
 
</script>
 
</script>
 
<!-- font -->
 
<!-- font -->
−
<link rel="stylesheet" type="text/css" href="http://fonts.googleapis.com/css?family=Delius" />
+
<style>
 +
/* latin */
 +
@font-face {
 +
  font-family: 'Delius';
 +
  font-style: normal;
 +
  font-weight: 400;
 +
  src: local('Delius-Regular'), url(https://static.igem.org/mediawiki/2018/a/af/T--GreatBay_China--font.woff) format('woff');
 +
  unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+2000-206F, U+2074, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
 +
}
 +
</style>
 
<!-- css main -->
 
<!-- css main -->
 
<style>
 
<style>

Latest revision as of 02:11, 18 October 2018

GBC-Part_Collection


mCATNIP2018@outlook.com
@Igem2018C

Part Collection:
Transcription-activator-like effector (TALE) Stabilised Promoter Family



Transcription-activator-like-effector stabilised promoters (TALEsp) are a type of promoters able to untie gene expression level from gene copy number. They differ in the TALE used for repression and the core promoter which the TALE represses. In this study, we have used two TALE proteins reported previously: TALE1 and TALE2. Through mutating core promoters of existing TALEsp, and adding TALE binding sites to the classical consensus promoter J23119, we created six more TALEsp, and have added all of twelve TALEsps to the iGEM Registry.








TALE1:


TALE2:


Table. 1 The source of all promoters in the library


All promoters are placed on the standard biobrick assembly compatible backbone pSB1C3, with a RBS (BBa_B0034) reporter gene sfGFP (BBa_K1679038) downstream of the promoters in between the restriction sites of SpeI and PstI. So teams can change reporter genes as they wish.




For TALE stabilised promoters repressed by the same TALE, the only difference between them is the sequence of the core promoter which the TALE binds to. By replacing this promoter, new TALE stabilised promoters could then be easily created. For making the process more convenient, we designed this composite part in which a genetic circuit encoding for amilCP, a blue pigment, replaces the core promoter sequence, and downstream are a RBS, a coding sequence of sfGFP, and a terminator. Two restriction sites of BsaI are put on the two ends of the amilCP circuit. By adding the same digestion sites on the promoter to be assembled, the amilCP circuit could be substituted by Golden Gate. The blue colour of amilCP and green colour of sfGFP provide a rapid distinguishment of the successful construct. If the amilCP circuit is not replaced, the colony grown would be blue as amilCP is being expressed. But if a promoter sequence substitutes amilCP circuit, sfGFP would be expressed instead of amilCP, making the colony fluorescent and easy to recognise.


Except for TALE1sp1 and TALE2sp1 which were synthesized de novo by Genscript, we assembled the rest of TALEsps by first obtaining core promoters using SOE PCR then replacing the amilCP circuit with them.


Characterization


In order to verify the stabilization effect of the TALE promoter family, we assembled all promoter members onto three backbones:



pUC20: copy number ≈ 500
pR6K: copy number ≈ 15
pSC101: copy number ≈ 1


An identical sfGFP is placed downstream of all promoters as a reporter gene. Three constitutive promoters: J23119, J23101, J23105, with the same sfGFP downstream were characterized along with the TALE promoters as a reference of promoter strength. The green fluoresce was measured by flow cytometry. (see methods in our Notebook).





To decide whether TALE can perform as expected in metabolic pathways, maintaining the pre-set ratio of production enzymes for ensuring optimal flux to the product, we tested TALE1 sp1 and TALE2 sp1 by comparison to pTac, a frequently-used IPTG inducible promoter, an geraniol synthesis operon (Part:BBa_K2753015) containing a GPPS (Part:BBa_K2753002) and a GES (Part:BBa_K2753003). Similar to the characterisation of green fluorescence, three backbones: pUC20, pR6K, pSC101 are used.