Part:BBa_K3710000

SouR: sarcosine-responsive transcriptional regulator

This part encodes the sarcosine-responsive transcriptional regulator SouR, optimised for E. coli codon usage.

Pseudomonas aeruginosa encodes a sarcosine oxidase catabolic operon (sox) comprising the sarcosine oxidase genes involved in the creatinine degradation pathway [1]. Sarcosine (N-methylglycine) is generated from a number of catabolic pathways including the creatinine metabolism and serves as both a carbon and nitrogen source for growth. During pathogenesis and within its environment P. aeruginosa is able to metabolise sarcosine precursors including the herbicide glyphosate and creatine into sarcosine.

The Sarcosine Oxidation and Utilization Regulator (SouR) was first identified by Willsey et al. (2016) using a transposon-based genetic screen of the sox operon in Pseudomonas aeruginosa and confirmed by β-galactosidase reporter assays. SouR is the first bacterial transcriptional regulator showing a selective and tight induction in response to sarcosine or structurally related compounds (e.g. ethylglycine). SouR is a member of the glutamine amidotransferase I-like transcription regulator (GATR) subfamily of the AraC regulator family (CD03137) and is encoded by the PA4184 gene of P. aeruginosa. Willsey et al. (2016) demonstrated that SouR is essential for growth on sarcosine as an energy source and binds within the -210 and -158 bp upstream region from the glya1 translational start site. Although little is known about SouR and sox genes in gram negative bacteria besides their widespread distribution, it is likely that creatinine or creatine could also act as an inducing ligand of SoxR.

References:

[1] Willsey, G. G., & Wargo, M. J. (2016). Sarcosine catabolism in Pseudomonas aeruginosa is transcriptionally regulated by SouR. Journal of Bacteriology, 198(2), 301-310.

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
  INCOMPATIBLE WITH RFC[25]

  Illegal AgeI site found at 440
  
• 1000
  COMPATIBLE WITH RFC[1000]