|
|
| (37 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | {{WHU-China}}
| |
| − | <html>
| |
| | | | |
| − |
| |
| − |
| |
| − | <div class="column full_size">
| |
| − | <h1>Description</h1>
| |
| − |
| |
| − | <p>Tell us about your project, describe what moves you and why this is something important for your team.</p>
| |
| − |
| |
| − |
| |
| − | <h5>What should this page contain?</h5>
| |
| − | <ul>
| |
| − | <li>Halogenated phenols are a group of organic molecules, characterized by benzene rings with hydroxyl groups and halogen atoms. In general, halogenated phenols tend to be more toxic and less biodegradable than their nonhalogenated counterparts, to note that phenols, cresols, and catechols do not bioaccumulate to any great extent. Used in large quantities for diverse purposes and moderately soluble in water, fugitive phenolics are inevitable and these can be moved around readily by water. It’s been reported that halogenated phenols have accumulated in various anoxic subsurface environments as a consequence of improper disposal. What’s even worse, increasing levels of halogenated phenol detected in humans and wildlife are of particular concern. With an original dehalogenase named RdhANP from Nitratireductor pacificus, we aim to engineer selected microbes to build a dehalogenater, to remove halogen atoms from halogenated phenols, thus reducing their toxicity and facilitate their subsequent treatment. Compared with other enzymes in the dehalogenase subfamily, which are usually membrane-associated and oxygen-sensitive, RdhANP is a soluble, oxygen-tolerant reductive dehalogenase depending on cobalamin (B12) and electron donors (i.e NADPH) for its catalytic activity. After successful heterologous expression of RdhANP, we’d design our dehalogenator to function efficiently in suitable devices.</li>
| |
| − |
| |
| − | </ul>
| |
| − |
| |
| − |
| |
| − | </div>
| |
| − |
| |
| − | <div class="column full_size" >
| |
| − |
| |
| − | <h5>Advice on writing your Project Description</h5>
| |
| − |
| |
| − | <p>
| |
| − | 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 consist, accurate and unambiguous in your achievements.
| |
| − | </p>
| |
| − |
| |
| − | <p>
| |
| − | Judges like to read your wiki and know exactly what you have achieved. This is how you should think about these sections; from the point of view of the judge evaluating you at the end of the year.
| |
| − | </p>
| |
| − |
| |
| − | </div>
| |
| − |
| |
| − |
| |
| − | <div class="column half_size" >
| |
| − |
| |
| − | <h5>References</h5>
| |
| − | <p>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.</p>
| |
| − |
| |
| − | </div>
| |
| − |
| |
| − |
| |
| − | <div class="column half_size" >
| |
| − | <h5>Inspiration</h5>
| |
| − | <p>See how other teams have described and presented their projects: </p>
| |
| − |
| |
| − | <ul>
| |
| − | <li><a href="https://2016.igem.org/Team:Imperial_College/Description">2016 Imperial College</a></li>
| |
| − | <li><a href="https://2016.igem.org/Team:Wageningen_UR/Description">2016 Wageningen UR</a></li>
| |
| − | <li><a href="https://2014.igem.org/Team:UC_Davis/Project_Overview"> 2014 UC Davis</a></li>
| |
| − | <li><a href="https://2014.igem.org/Team:SYSU-Software/Overview">2014 SYSU Software</a></li>
| |
| − | </ul>
| |
| − | </div>
| |
| − |
| |
| − |
| |
| − |
| |
| − | </html>
| |
