Composite

Part:BBa_K2442202

Designed by: Ailish O   Group: iGEM17_Glasgow   (2017-09-07)
Revision as of 22:37, 1 November 2017 by Frazer-B (Talk | contribs)


Ptet + RBS + MtlR

This part contains the mtlR coding sequence along with the ptet promoter. mtlR coding sequence is derived from the mannitol operon from Pseudomonas Fluorescens. The ptet promoter is the well characterised part R0040. This Biobrick was used in conjunction with BBa_K2442203. By splitting the regulatory protein (mtlR) from the promoter it regulates (pmtle) allowed for greater control over the expression of GFP.


Usage and Biology

The mtlR regulatory protein is found naturally in Pseudomonas fluorescens. The mtlR protein has been described as a multi-sugar transcriptional regulator. There is some evidence to suggest that the protein functions as a dimer. Naturally this multi-sugar regulator functions to switch on sugar metabolism genes in P.Flourescens in the presence of organic sugars.

The aim of our project was to harness the natural regulatory abilities of the mtlR protein and use this alongside the promoter that it regulates (pmtle). We also aimed to combine this regulatory system with a reporter construct BBa_K2442203 to evoke GFP response. We used the sequence of the P.Flourescens mtlR gene to construct a coding sequence that was regulated upstream by the ptet promoter. By cotrasnforming E.coli cells with BBa_K2442202 and BBa_K2442203 we were able to create a sugar responsive assay that produced GFP via induction by sugars.

Characterisation

We constructed two plasmid constructs- the regulatory plasmid BBa_K2442202 responsible for the transcription and translation of the MtlR protein, and the reporter plasmid which would allow for a measurable response to the MtlR-xylulose interaction. mtlR coding sequence was ordered as a G-block construct from IDT and was ligated into pSB1C3. As this was to be under the control of a tet promoter, the tet promoter and medium RBS B0032 were ordered as oligos from IDT and were ligated into a separate pSB1C3 plasmid. In order for the mtlR sequence to be behind the promoter and RBS, mtlR was restriction digested from its plasmid and ligated into the promoter plasmid. This produced our final regulatory plasmid.

The reporter plasmid was constructed by first ligating the mtlE promoter into pSB1C3. We ordered the sequence Liu et al (2015) [1] used, which contained the native promoter and RBS. We also decided to experiment with a variety of RBS in order to find the optimal one for our genetic circuit. We used the male promoter ligated to two different RBS, one stronger (B0034) and one weaker (B0032). Overall we created three reporter constructs, the wild type reporter plasmid (BBa_K2442203), and two variants, BBa_K2442204 and BBa_K2442205. These variants were ordered as single-stranded oligonucleotides, annealed together (to make double-stranded oligonucleotides) and then ligated into pSB1C3. We then used GFP from the kitplate (E0040). This was restriction digested out of the plasmid and ligated behind Ptet and the various RBS.

In order to test in the presence of both plasmids, the gene construct present in the reporter plasmid was built in pSB1C3 and then digested and ligated into a new plasmid, pSB3K3. This ensured both plasmids had a different origin of replication and therefore could both be present in one cell. It also ensured we could select for cells which contained both the plasmids required to carry out testing. These sugars were selected based on previous work with the mannitol operon and other similar sugars available in the lab were used. We tested these combinations with 6 different sugars; mannitol, sorbitol, sucrose, xylose, ribose, and fructose. Our controls were DH5α empty cells, fresh LB, and each plasmid alone. The two constructs were individually tested with a variety of sugars in order to record the fluorescence in the absence of MtlR. Controls were set up without the constructs in order to measure the basal level of GFP fluorescence. Our results showed:




Sequence and Features


Assembly Compatibility:
  • 10
    COMPATIBLE WITH RFC[10]
  • 12
    COMPATIBLE WITH RFC[12]
  • 21
    COMPATIBLE WITH RFC[21]
  • 23
    COMPATIBLE WITH RFC[23]
  • 25
    COMPATIBLE WITH RFC[25]
  • 1000
    COMPATIBLE WITH RFC[1000]


[edit]
Categories
Parameters
None