Difference between revisions of "Template:FAQ/Part Submission/Requirements"
m |
m |
||
| Line 1: | Line 1: | ||
| − | |||
====What are the requirements for submitting a part sample to the Registry?==== | ====What are the requirements for submitting a part sample to the Registry?==== | ||
| − | The requirements for submission | + | The requirements for submission... |
*The part must be added and documented on the Registry. | *The part must be added and documented on the Registry. | ||
| − | *The part must be BioBrick RFC10 compatible. | + | *The part must be [[Help:Assembly_Compatibility|BioBrick RFC10 compatible]]. |
| − | *The part sample must be in pSB1C3, the Registry's shipping plasmid backbone. | + | *The part sample must be in pSB1C3, the [[Help:Shipping | Registry's shipping plasmid backbone]]. |
| − | *The part sample must be flanked by the full BioBrick prefix and suffix. | + | *The part sample must be flanked by the full [[Help:Prefix-Suffix|BioBrick prefix and suffix]]. |
| − | *A completed submission form. | + | *A [[Help:Submission/Form|completed submission form]]. |
| − | *'''For iGEM teams:''' Parts must arrive at iGEM HQ by the deadline. | + | *'''For iGEM teams:''' [http://2014.igem.org/Calendar_of_Events Parts must arrive at iGEM HQ by the deadline]. |
Please see the [[Help:Sending_Parts|Registry's submission requirements]] page for more information. | Please see the [[Help:Sending_Parts|Registry's submission requirements]] page for more information. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| Line 22: | Line 15: | ||
BioBrick RFC10 compatibility ensures that... | 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.) | *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 | *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 | + | |
| + | ====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 [[Help:Assembly_Compatibility|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 [https://parts.igem.org/partsdb/scars.cgi 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 [[Help:Sequence_Features|Sequence & Features box]]. | ||
====Why do my parts need to be submitted in pSB1C3==== | ====Why do my parts need to be submitted in pSB1C3==== | ||
| − | *Your part sample will be flanked by the [ | + | 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 [[Help:Prefix-Suffix|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 [https://parts.igem.org/Part:BBa_G00100 VF2] and [https://parts.igem.org/Part:BBa_G00101 VR] primer sites). | *The Registry can test and maintain all parts in the same way (sequence all parts using [https://parts.igem.org/Part:BBa_G00100 VF2] and [https://parts.igem.org/Part:BBa_G00101 VR] primer sites). | ||
*pSB1C3 is a high-copy plasmid, which improves miniprep yields for parts | *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.) |
| Line 40: | Line 42: | ||
There may be a reason why a part sample cannot be submitted in pSB1C3. For example... | There may be a reason why a part sample cannot be submitted in pSB1C3. For example... | ||
| − | *The part contains chloramphenicol resistance | + | *The part contains chloramphenicol resistance. <b>Contact iGEM HQ first.</b> You can use <partinfo>pSB1K3</partinfo> instead. |
| − | *The part is toxic to cells in a high copy plasmid backbone | + | *The part is toxic to cells in a high copy plasmid backbone. <b>Contact iGEM HQ first.</b> You can use <partinfo>pSB3C5</partinfo> instead. |
| − | + | ||
| − | + | ||
| − | + | ||
| − | iGEM | + | |
====My part is not BioBrick compatible==== | ====My part is not BioBrick compatible==== | ||
| − | Before working with your part in the lab (characterizing/measuring), make sure it is [[Help: | + | Before working with your part in the lab (characterizing/measuring), make sure it is [[Help:Assembly_Compatibility|BioBrick compatible]]. If not... |
| − | *'''[ | + | *'''[[DNA_Synthesis| 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 [ | + | **Synthesis is also useful, since you can synthesize your part with the [[Help:Prefix-Suffix|BioBrick prefix and suffix]], so it is ready for shipping to the Registry. [[DNA_Synthesis|See our synthesis offer with IDT]] |
*Use site-specific mutagenesis 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). | ||
Revision as of 18:23, 17 September 2014
Contents
- 1 What are the requirements for submitting a part sample to the Registry?
- 2 Why do parts sent to the Registry need to be BioBrick RFC10 compatible
- 3 Does the Registry only allow BioBrick RFC10 compatible parts?
- 4 Why do my parts need to be submitted in pSB1C3
- 5 My part cannot be submitted in pSB1C3 because of ______
- 6 My part is not BioBrick compatible
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.
- A completed submission form.
- For iGEM teams: [http://2014.igem.org/Calendar_of_Events 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 (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...
- 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.
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)! 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. Contact iGEM HQ first. You can use pSB1K3 instead.
- The part is toxic to cells in a high copy plasmid backbone. Contact iGEM HQ first. You can use pSB3C5 instead.
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).