Template:FAQ/Part Submission/Requirements

What are the requirements for submitting a part sample to the Registry?

The requirements for submission...

• The part must be added and documented on the Registry.
• The part must be BioBrick RFC10 compatible.
• The part sample must be in pSB1C3, the Registry's shipping plasmid backbone.
• The part sample must be flanked by the full BioBrick prefix and suffix on pSB1C3.
• A completed submission form.
• Parts must be shipped in the provided Submission Kit.
• For iGEM teams: [http://2016.igem.org/Calendar Parts must arrive at iGEM HQ by the deadline].

Please see the Registry's submission requirements page for more information.

Why do parts sent to the Registry need to be BioBrick RFC10 compatible

iGEM and the Registry are built on standard parts which is vital to making biology easier (and more predictable) to engineer, for high school teams & university teams to research labs. It is also why iGEM has made BioBrick RFC10 compatibility a requirement; the parts that we receive from teams and labs can be used and assembled by everyone easily and reliably, without the need to substantially alter, experiment, or research alternate methods.

BioBrick RFC10 compatibility ensures that...

• users can assemble these parts with 3A Assembly to build new devices and projects
• part samples can be easily moved from one plasmid backbone to another (for shipping, measurement, operation etc.)
• the Registry can test and maintain all part samples it receives in the same way

Does the Registry only allow BioBrick RFC10 compatible parts?

If you are submitting a physical sample of a part to the Registry, that part must be BioBrick RFC10 compatible. iGEM teams are required to send part samples to the Registry to fulfill medal requirements and be eligible for awards. These parts must be BioBrick RFC10 compatible

The parts you add and document on the Registry do not need to be BioBrick RFC10 compatible. The Registry supports multiple assembly standards and is also open to integrating new ones. You can easily see what Registry supported assembly standards your part is compatible with, by taking a look at the Sequence & Features box.

My part is not BioBrick compatible

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

• Synthesize your part to remove any illegal restriction sites, through synonymous substitutions (silent mutations).
  • Synthesis is also useful, since you can synthesize your part with the BioBrick prefix and suffix, so it is ready for shipping to the Registry. See our synthesis offer with IDT
• Use site-specific mutagenesis to remove any illegal restriction sites, through synonymous substitutions (silent mutations).

Currently, the Registry only accepts parts samples that are BioBrick compatible. If you have questions about this requirement, please don't hesitate to contact iGEM HQ (hq (at) igem . org)! Contact us early and we may be able to address your concerns.

Why do my parts need to be submitted in pSB1C3

Having a shipping standard backbone lets the Registry receive and handle all parts in the same way: using the same growth conditions and quality control measures. With over 1000 new parts submitted each year, this improves our ability to handle, maintain, and test new parts. When anyone uses the part, they'll know exactly what to expect. They can easily unpackage it from the shipping plasmid backbone, and transfer it into a different backbone for a specific use.

Shipping in pSB1C3 ensures...

• Your part sample will be flanked by the BioBrick prefix and suffix on the backbone
• users can assemble these parts with 3A Assembly to build new devices and projects
• The Registry can test and maintain all parts in the same way (sequence all parts using VF2 and VR primer sites).
• pSB1C3 is a high-copy plasmid, which improves miniprep yields for parts
• part samples can be easily moved from one plasmid backbone to another (for shipping, measurement, operation etc.)

My part cannot be submitted in pSB1C3 because of ______

First, contact iGEM HQ (hq (at) igem . org)! Contact us early and we may be able to address your concerns.

There may be a reason why a part sample cannot be submitted in pSB1C3. For example...

• The part contains chloramphenicol resistance. Contact iGEM HQ first. You must use pSB1K3 instead.
• The part is toxic to cells in a high copy plasmid backbone. Contact iGEM HQ first. You must use pSB3C5 instead.

My part is not meant to be used/operated in pSB1C3, can I use ______ instead

Unfortunately, no. Please remember, that the shipping standard backbone lets the Registry receive and handle all parts in the same way. In turn, when these samples are distributed to users, they'll know exactly what to expect. They can easily unpackage it from the shipping plasmid backbone, and transfer it into a different backbone for a specific use.

We've created a new plasmid backbone. How can we submit it to the Registry?

While the Registry does not specialize in plasmids, you can send your plasmid backbone with BBa_J04450, the Registry's default insert. Your plasmid backbone must be able to replicate in E. coli.

Can we send part samples after the deadline?

If you're an iGEM Lab, you can send part samples at anytime.

If you're an iGEM Team, your part samples must arrive on or before the deadline on the Calendar, in order to be evaluated for the competition. Teams can continue to submit part samples after the deadline, however these parts will not be evaluated by the iGEM judges and are not eligible for medal criteria or awards.

For iGEM 2016, we have changed the deadline to reflect a send by date of [http://2016.igem.org/Calendar October 21st]. Parts must be sent out on or before October 21st. Shipments must have a tracking number, as that will let us know when parts shipped, and when to expect arrival.