Difference between revisions of "Team:Duke/Description"
| Line 3: | Line 3: | ||
| − | <p><b>Adam, Trudy, and Joe</b></p> | + | <p><b>Adam, Maria, Trudy, and Joe</b></p> |
<br> <br> <br> | <br> <br> <br> | ||
Revision as of 20:25, 13 October 2018
Adam, Maria, Trudy, and Joe
Description
Tell us about your project, describe what moves you and why this is something important for your team.
Project Description
We are engineering E. coli to produce taxol from an intermediate (10-Deacetylbaccatin III) in the taxol synthesis pathway. We are using a modular approach to link the five necessary genes together onto a single DNA strand so that our design can be easily adapted for next generation taxanes in the future. Each gene in the pathway will be equipped with a T7 promoter of various strengths from a promoter library, fitted to the genes using the ePathOptimize approach for metabolic engineering. The project's end goal is to analyze the activity of produced taxol and evaluate this taxol biosynthesis design's feasibility in industrially relevant conditions. Homology modeling is used to develop protein models for the five necessary genes to determine active site architecture and catalytic functions. These models will then be considered when mutating the genes to produce next generation taxane products.
Why is Taxol important?
Taxol is a cancer drug that works by inhibiting microtubule disassembly during cell division. ....
Why is biosynthesis of Taxol necessary?
Taxol is currently produced...the problem with this is...
What are we doing?
Our project aims to engineer E. coli to produce Taxol. Mention building on the work of the 2016 Duke iGEM team.
References
Stuff
What should this page contain?
- A clear and concise description of your project.
- A detailed explanation of why your team chose to work on this particular project.
- References and sources to document your research.
- Use illustrations and other visual resources to explain your project.
Inspiration
See how other teams have described and presented their projects:
Advice on writing your Project Description
We encourage you to put up a lot of information and content on your wiki, but we also encourage you to include summaries as much as possible. If you think of the sections in your project description as the sections in a publication, you should try to be concise, accurate, and unambiguous in your achievements.
References
iGEM teams are encouraged to record references you use during the course of your research. They should be posted somewhere on your wiki so that judges and other visitors can see how you thought about your project and what works inspired you.