Team:Austin UTexas/Parts

Parts

pH Sensors

Possessing the ability to monitor the brewing process of kombucha without disturbing the microenvironment and using a very visible color reporter would allow for greater insights as to how the populations of organisms and pH may change due to competition amongst other bacteria and yeast in the beverage and SCOBY of the kombucha. The byproducts produced by the kombucha as it brews causes the tea to become more acidic, leading to our team searching for pH sensitive promoters, and for ways to implement these into kombucha.

Though an acidic sensor was what was required for our kombucha analysis, the identification of sensors in other areas of the pH spectrum were explored as well. Three sequences were identified, the CadC operon for the acidic range, CpxA-CpxR complex for the neutral range, and the P-atp2 promoter from the BioBrick Registry (BBa_K1675021) for the basic range. Each sequence was paired with a unique corresponding reporter sequence so that if each pH sensitive plasmid were in the same environment, the specific pH of the system could be seen. The reporters used were, BBa_E1010 for the CadC construct, BBa_K1033916 for the CpxA-CpxR complex, and BBa_K592009 for the P-atp2 promoter.

CadC

The CadC operon is a native pathway in E. coli, involved in the cadaverine synthesis pathway. The protein CadC protein on the operon is produced and activates segments downstream of the operon on the CadBA receptors. The CadC protein is pH sensitive to an external pH 5.5 and below, as well as lysine dependent. A point mutation on codon 265, in which argenine is converted to cystine, causes the CadC protein to become lysine independent (Dell, Neely, Olson, 1994).

Unfortunately, we have been unable to grow the modified CadC operon in E. coli suggesting some form of cell toxicity. Due to this apparent toxicity, no data regarding this mutant CadC could be collected. Alternative candidates are being explored for other pH sensors that sense in the acidic range.

CpxA-CpxR

CpxA-CpxR is a two-component mechanism that is activated at pH 7.4 and repressed at pH 6.0. CpxA is an intermembrane protein that autophosphorylates at a certain external pH, CpxR (a kinase) then gets phosphorylated by CpxA and acts as a transcription factor. This system originally is a transcription factor for the virF gene, but we replaced virF with the Reporter. The original sequence was found in Shigella sonnei, but E. coli has a homolog of these proteins so all that is required on the construct is the appropriate prefix/suffix and CpxR binding site.

Cpx_pH_Culture_Tubes

The order from left to right is Control pH 6-9 and then Experimental pH 6-9. These are showing the gradient change in expression accordingly with the change of pH due to a pH-dependent promotor compared to consistent expression accordingly with a promoter that is always "on". The main point is that the Control at pH 6 has more expression of the Yellow-Green Chromoprotein than the Experimental at pH 6. The pH-Dependent promoter of the Experimental group is down-regulated at pH 6 whereas the control is not. Also, there is an increase in YGCP expression between the Experiment pH 7 and pH 8 that is not seen in the Control between pH 7 and pH 8. The normalized data is below shows the relative expression of YGCP. The construct can be found on the iGEM registry as: Bba_K2097000.

pH_Dependent_Promoter

P-atp2

The P-atp2 promoter, native to the bacterium Corynebacterium glutamicum is reportedly induced at pH 7, to pH 9 (BIT-China-2015 and BBa_K1675021). Utilizing the blue chromoprotein (BBa_K592009), a test was designed in which a plasmid containing the P-atp2 promoter with the blue chromoprotein was grown alongside an E. coli line that contained a plasmid with just the blue chromoprotein. We expected to see constant blue chromoprotein production in the control series (those that lacked P-atp2) and a visual increase in blue chromoprotein as the pH was raised from 6 to 9 in the cells that contained the P-atp2 construct.

Patp2Results

Each team will make new parts during iGEM and will submit them to the Registry of Standard Biological Parts. The iGEM software provides an easy way to present the parts your team has created. The <groupparts> tag (see below) will generate a table with all of the parts that your team adds to your team sandbox.

Remember that the goal of proper part documentation is to describe and define a part, so that it can be used without needing 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.


Note

Note that parts must be documented on the <a href="http://parts.igem.org/Main_Page"> Registry</a>. This page serves to showcase the parts you have made. Future teams and other users and are much more likely to find parts by looking in the Registry than by looking at your team wiki.



Adding parts to the registry

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.

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 you will remember all the details about your parts. Remember, you don't need to send us the DNA sample before you create an entry for a part on the Registry. (However, you do need to send us the DNA sample before the Jamboree. If you don't send us a DNA sample of a part, that part will not be eligible for awards and medal criteria.)



What information do I need to start putting my parts on the Registry?

The information needed to initially create a part on the Registry is:

  • Part Name
  • Part type
  • Creator
  • Sequence
  • Short Description (60 characters on what the DNA does)
  • Long Description (Longer description of what the DNA does)
  • Design considerations

We encourage you to put up much more 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.


Inspiration

We have a created a <a href="http://parts.igem.org/Well_Documented_Parts">collection of well documented parts</a> that can help you get started.

You can also take a look at how other teams have documented their parts in their wiki:

Part Table


</html> <groupparts>iGEM2016 Example</groupparts>