Scar

Part:BBa_K1824890

Designed by: Wenbo Xu   Group: iGEM15_XJTLU-CHINA   (2015-09-07)

The Sequence of the SpeI/XbaI scar in BioBricks standard assembly.

In most cases, designers tend to embed an appropriate spacer sequence between one individual part and another. The 3A assembly, a commonly used manipulation method, creating scars between biobricks and, this unique scar usually served as default transcription spacer sequence.

XJTLU-CHINA 2015 used Gibson assembly instead of conventional 3A assembly to create complex parts. If the reader have any interest to read the assembly diagram that the team promoted, they would find out that Gibson assembly was the ideal choices for the project.

Though XJTLU-CHINA used Gibson assembly, which means parts could directly attach to one another without scars, the team still preserved the usually used scar sequence as the spacer. If readers looked through the assembly diagram that the team provided, they would find out that, for the constructs like a promoter part + a RBS part, the team not only embedded the spacer between the promoter and the RBS but also attach a spacer at the end of the RBS part.

However, this design became problematical when the team registries the parts. Take the mentioned a promoter part + a RBS part as an instance, a promoter + a RBS is usually registered as a composite part. What designers usually do is to enter part number they used in order and generate the new composite part with scars. Nevertheless, for the parts of XJTLU-CHINA, this operation is not applicable because if a promoter part + a RBS part was outputted as a new composite part with scars, there would be no scar remained at the end of RBS part.

To fix this problem, we have to registry several spacer parts and put them into our composite parts in the manner of generating blunt end.


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