Difference between revisions of "Part:BBa K4061115"

 
 
Line 6: Line 6:
  
 
Teams are recommended to use SWISS-MODEL or any protein modelling software to confirm whether this part interferes with the parent protein sequence. Since scaffold protein has a Leucine zipper ligand with a high affinity, the scaffold may still competitively bind to the domain.
 
Teams are recommended to use SWISS-MODEL or any protein modelling software to confirm whether this part interferes with the parent protein sequence. Since scaffold protein has a Leucine zipper ligand with a high affinity, the scaffold may still competitively bind to the domain.
 +
 +
This part is yet to be characterised, wet lab work is in progress
  
 
<!-- Add more about the biology of this part here
 
<!-- Add more about the biology of this part here

Latest revision as of 12:40, 21 October 2021


Leucine Zipper domain with linker

This part can be put in 3' end of the desired protein CDS. A protein engineered with this domain should be used together with another protein modified with SH3 domain (BBa_K4061110). Upon the expression of a scaffold protein (BBa_K4061015), the interaction between these two proteins can be enhanced. Our team used these domains on the EnvZ and OmpR proteins to enhance their interaction and prevent cross-talk from other TCS species present in E. coli. This part was put with OmpR while the SH3 domain (BBa_K4061110) was put along with EnvZ. This protein contains an inert peptide chain of 12 amino acid Glycine-Serine that is meant to separate the additional domain from the parent protein and provide flexibility to the domain for interacting with the scaffold. This part was inspired from Whitaker, W. R. (2012) "Engineering robust control of two-component system phosphotransfer using modular scaffolds".

Teams are recommended to use SWISS-MODEL or any protein modelling software to confirm whether this part interferes with the parent protein sequence. Since scaffold protein has a Leucine zipper ligand with a high affinity, the scaffold may still competitively bind to the domain.

This part is yet to be characterised, wet lab work is in progress

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
    INCOMPATIBLE WITH RFC[1000]
    Illegal SapI.rc site found at 55