Difference between revisions of "Template:FAQ/Part Submission/Requirements"

Revision as of 18:07, 17 September 2014

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

The requirements for submission (as of 2014)...

• 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.
• A completed submission form.
• For iGEM teams: Parts must arrive at iGEM HQ by the deadline.

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

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.

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 (RFC 10) 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...

• user 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

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

Why do my parts need to be submitted in pSB1C3

• Your part sample will be flanked by the BioBrick prefix and suffix on the backbone</li>
• 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
• Users can easily and reliably move or assemble the part into another plasmid backbone

My part cannot be submitted in pSB1C3 because of ______

First, contact iGEM HQ (hq (at) igem . org)! You may be eligible to receive an exemption for that part.

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

• The part contains chloramphenicol resistance
• The part is toxic to cells in a high copy plasmid backbone

Why is compatibility important?

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 (RFC 10) 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.

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).