Help:Assembly Compatibility


Add a Part to the Registry: Help Pages
  • Add a Basic Part - A tutorial on how to add a basic part
  • Add a Composite Part - A tutorial on how to add a composite part
  • Synthesis - Things to keep in mind if you're adding and documenting a part you've synthesized
  • Assembly Compatibility - Your new part must be BioBrick compatible!
  • Twins - Parts are twins if they have the same sequence
  • Document Parts - Recommendations on how to document your parts
  • Make a Contribution - Improve existing parts

Ready to add your part? Go to the Add a Part page.
Have questions on adding a part to the Registry? Send an email to hq (at) igem . org.

Help Pages: Assembly Standards || Assembly Compatibility || Supported Assembly Systems || Scars

Accepted Standards: BioBrick RFC[10] | iGEM Type IIS RFC[1000]

Depracated Standards: BioBrick BB-2 RFC[12] | Berkeley RFC[21] | Silver RFC[23] | Freiburg RFC[25]

Assembly Compatibility

Choose your method, support the standard

Choose your method and assemble your parts with a variety of assembly technologies. You can use 3A Assembly, Type IIS, synthesis, Gibson, and more.

Support the standard. Although, the Registry supports several standards, BioBrick RFC[10] and Type IIS are the Registry's current de facto standards; all parts on the Registry that will be considered for the iGEM competition (medals, awards, etc.) must be BioBrick compatible or Type IIS compatible.


In previous years, samples of BioBrick parts were required to be shipped in the shipping plasmid backbone, pSB1C3. Standard parts and samples ensured that the Registry could maintain and test all new parts samples in the same way.

In 2019, sample submission is no longer required. However, ensuring your parts are assembly compatible allows the Registry to synthesize your parts in BioBrick and/or Type IIS format. Registry members can easily and reliably use and assemble these parts in the future.


How is a part compatible?

The part's sequence must not contain illegal restriction sites (or other specified sequences) as defined by the assembly standard.

BioBrick compatible parts must not have the following restriction sites:

Sequence Type Enzyme Note
gaattc Illegal EcoRI
tctaga Illegal XbaI
actagt Illegal SpeI
ctgcag Illegal PstI
gcggccgc Avoid NotI

All of these restriction sites belong to the prefix and suffix of the BioBrick assembly standard.


Supported Standards

By supporting an assembly standard, the Registry software can detect and understand the assembly process for parts. This includes:

  • Detection of illegal restriction sites in a part's sequence
  • Recognizing assembly scars in composite parts
  • Identification of a sample's assembly standard, through sequence verification of the sample's prefix and suffix
    • Remember, a part can have many samples in the Registry's Repository. Those samples can be in plasmid backbones of different assembly standards.


View the Assembly Systems Page to see exactly what the Registry software looks for in these supported assembly standards

Click below to view the supported assembly standards as specified by their original RFC



FAQ

Why is compatibility important?

The iGEM Registry is built on Standard Biological Parts.

  • Assembly Standards are one of the facets of the standardization of biology
    • All users can easily and reliably assemble and use these parts. They are not conducting an experiment when putting them together.
  • BioBrick and Type IIS compatibility allows the Registry to test and maintain all received parts in the same way.


My part is not BioBrick or Type IIS compatible

Before working with your part in the lab (characterizing/measuring), make sure it is BioBrick compatible or Type IIS compatible. If not...

  • Synthesize your part to remove any illegal restriction sites, through synonymous substitutions (silent mutations).
  • Use site-specific mutagenesis to remove any illegal restriction sites, through synonymous substitutions (silent mutations).