Part:BBa_K1824889

A Transcriptional Spacer Sequence

In most cases, designers usually tend to embedded an appropriate spacer sequence between one individual part and the other. The 3A assembly, a commonly used manipulation method, creating scar 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 persevered 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. If the readers know the mechanism of Gibson assembly, they would know that it is for the one of the greatest feature of Gibson assembly, scarless manipulation.

However, this design became problematical when the team registry the parts. Take the mentioned a promoter part + a RBS part as a 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]