Difference between revisions of "Part:BBa K2324001"

Line 2: Line 2:
 
__NOTOC__
 
__NOTOC__
 
<partinfo>BBa_K2324001 short</partinfo>
 
<partinfo>BBa_K2324001 short</partinfo>
 
+
<p>The literature has shown that the terminal pili protein FimH (Le Trong et al 2010) can be modified by inserting heterologous sequences at position 225 and 258 (Pallesen et al 1995, Shembri et al 1999). However these two amino acids are in the pilin binding domain which may present difficulties when attempting to introduce large modifications. Harvard iGEM 2015 also introduced modifications at position 225 of the mature FimH protein.</p>
CDS which codes for a FimH protein fused with a sfGFP at residue 225 after cleavage of the signal peptide. For characterisation with promoter, RBS and terminator please see https://parts.igem.org/Part:BBa_K2324011
+
<p>
 +
CDS which codes for a FimH protein fused with a sfGFP at residue 225 after cleavage of the signal peptide. For characterisation with promoter, RBS and terminator please see https://parts.igem.org/Part:BBa_K2324011</p>
  
 
<!-- Add more about the biology of this part here
 
<!-- Add more about the biology of this part here

Revision as of 19:52, 1 November 2017


FimH+sfGFP at residue 225

The literature has shown that the terminal pili protein FimH (Le Trong et al 2010) can be modified by inserting heterologous sequences at position 225 and 258 (Pallesen et al 1995, Shembri et al 1999). However these two amino acids are in the pilin binding domain which may present difficulties when attempting to introduce large modifications. Harvard iGEM 2015 also introduced modifications at position 225 of the mature FimH protein.

CDS which codes for a FimH protein fused with a sfGFP at residue 225 after cleavage of the signal peptide. For characterisation with promoter, RBS and terminator please see https://parts.igem.org/Part:BBa_K2324011

Sequence and Features


Assembly Compatibility:
  • 10
    COMPATIBLE WITH RFC[10]
  • 12
    COMPATIBLE WITH RFC[12]
  • 21
    INCOMPATIBLE WITH RFC[21]
    Illegal BglII site found at 185
  • 23
    COMPATIBLE WITH RFC[23]
  • 25
    COMPATIBLE WITH RFC[25]
  • 1000
    COMPATIBLE WITH RFC[1000]