Coding

Part:BBa_K197029

Designed by: John Wang   Group: iGEM09_Berkeley_Wetlab   (2009-10-21)
Revision as of 04:55, 22 October 2009 by JCAnderson (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

gly-ser-repeats

This part encode repeats of GlySer-coding sequence. It can be used as a spacer element to improve the display of passenger proteins.


This part is a cell-surface displayer spacer part. A spacer is used to improve the display of passenger domains.

For successful cell surface display of proteins, there must be an effective protein localization mechanism. Gram-negative bacteria such as E. Coli have two membranes, which present a problem for transporting proteins synthesized in the cytoplasm to the outside of the cell. Various transport schemes exist in gram-negative bacteria to effectively localize proteins to the outermembrane. The most common schemes are TypeI, TypeIII, and TypeV secretion.

HeatMapBerkeley.jpg

The heat map above points to an interesting trend made clear by the streptavidin and mgfp-5 data. Although all constructs contain short linkers between the displayers and passengers, the inclusion of spacer elements for both systems appears to enhance functional surface display of the passengers. Moreover, the identity of the spacer element is an important parameter determining display efficiency. There is an increase in functional display when the INP repeats spacer is added between the displayers and the strep tag as is seen in the increase in lighter blocks in the map. This trend is especially evident in the mgfp data in which there are several weak signals (many dark blocks in the map) for mgfp displayed on its own. With the addition of several spacer elements, a significant general increase in signal for almost 100% of the systems is observed.


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