Difference between revisions of "Loop Assembly"
m |
m |
||
| Line 1: | Line 1: | ||
| − | iGEM | + | As we prepare for iGEM 2019, I have been trying to decide how to support Type IIS assembly methods for the Registry and the 2019 iGEM Competition. Since 2016, iGEM has allowed teams to submit parts in the PhytoBricks (Type IIS Golden Gate) standard, but have not fully supported any IIS standard. |
Our current proposal is as follows: | Our current proposal is as follows: | ||
| − | <q>iGEM fully adopts the Loop Assembly standard (link) with Level 0 (basic) parts adhering to the MoClo and/or PhytoBricks Golden Gate assembly standards. This includes giving teams full credit for submitting samples in this standard, updating the Registry software to support the standard, creating documentation for our users, and distributing a collection of basic parts and cloning vectors in the 2019 Distribution Kit. | + | <q>iGEM fully adopts the Loop Assembly standard (link) with Level 0 (basic) parts adhering to the MoClo and/or PhytoBricks Golden Gate assembly standards. This includes giving teams full credit for submitting samples in this standard, updating the Registry software to support the standard, creating documentation for our users, and distributing a collection of basic parts and cloning vectors in the 2019 Distribution Kit. iGEM would, of course, continue to support and send out BioBrick parts for the foreseeable future.
</q> |
| − | + | Before we finalize the plans for adopting Loop, I would like to collect input from our community. If you have any comments or thoughts on iGEM adopting and supporting Loop (including the MoClo and/or PhytoBricks assembly standards), please send an email to: | |
Revision as of 16:13, 29 November 2018
As we prepare for iGEM 2019, I have been trying to decide how to support Type IIS assembly methods for the Registry and the 2019 iGEM Competition. Since 2016, iGEM has allowed teams to submit parts in the PhytoBricks (Type IIS Golden Gate) standard, but have not fully supported any IIS standard.
Our current proposal is as follows:
iGEM fully adopts the Loop Assembly standard (link) with Level 0 (basic) parts adhering to the MoClo and/or PhytoBricks Golden Gate assembly standards. This includes giving teams full credit for submitting samples in this standard, updating the Registry software to support the standard, creating documentation for our users, and distributing a collection of basic parts and cloning vectors in the 2019 Distribution Kit. iGEM would, of course, continue to support and send out BioBrick parts for the foreseeable future.
Before we finalize the plans for adopting Loop, I would like to collect input from our community. If you have any comments or thoughts on iGEM adopting and supporting Loop (including the MoClo and/or PhytoBricks assembly standards), please send an email to: