Difference between revisions of "Part:BBa K4144010"

Line 10: Line 10:
 
         <div class="col-lg" style="margin:auto;text-align:center;">
 
         <div class="col-lg" style="margin:auto;text-align:center;">
 
                 <img style="margin:20px auto 5px auto;" src="https://static.igem.wiki/teams/4144/wiki/same-part/bba-k414410/picture1.png" width="80%">
 
                 <img style="margin:20px auto 5px auto;" src="https://static.igem.wiki/teams/4144/wiki/same-part/bba-k414410/picture1.png" width="80%">
                 <p style="color:Gray; padding:0px 30px 10px;">Figure. 1 Enzymatic Reaction catalyzed by opSam2</p>
+
                 <p style="color:Gray; padding:0px 30px 10px;">Figure. 1 Linker addition design into opPet8p::sfGFP recombined protein</p>
 
         </div>
 
         </div>
 
</html>
 
</html>

Revision as of 07:34, 8 October 2022


Improved recombined SAMe transporter opPet8p fused with linker

Usage and Biology

Linkers can be classified into three groups: flexible, rigid and cleavable. Flexible linkers are generally composed of small, non-polar or polar residues such as Gly, Ser and Thr. The most common is the (Gly4Ser)n linker (Gly–Gly–Gly–Gly–Ser)n, where n indicates the number of repeats of the motif. Polyglycine linkers have also been evaluated, but the addition of a polar residue such as serine can reduce linker–protein interactions and preserve protein function. Due to their flexibility, these linkers are unstructured and thus provided limited domain separation in a previous study.

We WHU-China plan to use such linker to contact opPet8p and sfGFP in order to avoid the opPet8p membrane localization disruption by adding a sfGFP tag.

Figure. 1 Linker addition design into opPet8p::sfGFP recombined protein

Sequence and Features


Assembly Compatibility:
  • 10
    COMPATIBLE WITH RFC[10]
  • 12
    INCOMPATIBLE WITH RFC[12]
    Illegal NheI site found at 520
  • 21
    INCOMPATIBLE WITH RFC[21]
    Illegal BglII site found at 390
    Illegal BamHI site found at 1018
  • 23
    COMPATIBLE WITH RFC[23]
  • 25
    INCOMPATIBLE WITH RFC[25]
    Illegal AgeI site found at 1642
  • 1000
    COMPATIBLE WITH RFC[1000]