"
Judging/Variance/Guelph
From 2008.igem.org
| Line 63: | Line 63: | ||
Guelph iGEM Team | Guelph iGEM Team | ||
| + | |||
| + | Dear David: | ||
| + | |||
| + | Please do not submit the commercial cloning vectors pJET and pDRIVE to the registry. However, when you do submit your standard biobrick plasmids, please document in the registry that you have the parts available on those commercial vectors also. That way others can request them from your lab in the future. If those requests become frequent, then we would encourage you to propose a new standard vector for the registry. | ||
| + | |||
| + | Sincerely, | ||
| + | iGEM judging | ||
Revision as of 04:03, 3 October 2008
Request
Dear iGEM Judges,
I’m writing on behalf of the 2008 Guelph iGEM Team to request permission to submit non-biobrick parts to the registry for this year’s Jamboree.
For the first year of our school's participation in the competition, the Guelph iGEM team is building a synthetic operon for co-expression of a large number of carotenoid metabolic genes necessitating a slightly divergent cloning technique for straigtforward, multipart sequential ligations. We generated biobrick parts with appropriate restriction sites in commercial cloning vectors, but have also included non standard biobrick REs to allow us to serially ligate several genes into a synthetic operon and RNAi conformations.
Our strategy begins to generate a promoter with the start codon friendly restriction site Nde driving GFP expression in the promoter testing device, pSB1A3-E0240. The GFP is removed and the CrtE gene is inserted next to the promoter with the Nde while the Xba in the 3' end is fused to the vector's SpeI and nullified. This first gene included SpeI and XhoI sites in its 3' UTR, allowing the next gene to be inserted using Xba and Xho, while it carries SpeI and XhoI sites as well. And so on. Using this strategy we believe it possible to extend the synthetic operon to a large number of genes. Obviously if we had used a biobrick RE like Not1 instead of Xho, Biobrick parts we would've made would include the Xba or Spe sites inside the NotI sites flanking the Biobrick.
Likewise, we have used a modified RE scheme for construction of our second project - an RNAi generating Biobrick for silencing plant genes using bacteria. In order to enable use of any pre-existing Biobrick in the registry, we ordered a construct with Biobrick RE in an altered orientation. Eco and Spe together on one side of the corn actin1 intron, and Not and Xba on the other side. To the 3' end we included a synthetic terminator followed by the PstI site, and the MfeI and NdeI sites at the 5' end which allowed us to non-conservatively insert the construct into the Biobrick vector pSB1A2, eliminating the MfeI site (compatible ends with EcoRI) and allowing us again to cut with the NdeI to fuse to the strong constitutive promoter we are using. Our target vector for this project has NdeI and PstI sites we plan to use to conveniently insert this RNAi constuct into. Part of our strategy is to use a broad host range plasmid which will accept a number of different inserts, and the NdeI and PstI sites are ideal for this.
In the spirit of iGEM, we hope to share these parts with the community, and to facilitate this transfer, we have all our parts in two commercial cloning vectors, pJET from Fermentas, and pDRIVE from Quiagen. If requested of the committee, we can transfer these parts to Biobrick vectors but would also like to know if submission of these sequenced parts will be acceptable as is. Much of this is outlined on our wiki with diagrams. We hope you will accept our constructs for this year's competition and let us know what changes to our plan will be necessary.
Thank you for your consideration,
David Johnston
Guelph iGEM Team
Dear David:
Please do not submit the commercial cloning vectors pJET and pDRIVE to the registry. However, when you do submit your standard biobrick plasmids, please document in the registry that you have the parts available on those commercial vectors also. That way others can request them from your lab in the future. If those requests become frequent, then we would encourage you to propose a new standard vector for the registry.
Sincerely, iGEM judging
