Difference between revisions of "Team:Bielefeld-CeBiTec/Description"

m (added footer)
 
(19 intermediate revisions by one other user not shown)
Line 1: Line 1:
{{Bielefeld-CeBiTec}}
+
{{Team:Bielefeld-CeBiTec/Head}}
 
+
{{Team:Bielefeld-CeBiTec/Header}}
{{Team:Bielefeld-CeBiTec/CSS}}
+
 
<html>
 
<html>
 
+
<body>
 
+
<div class="container">
 
+
        <div class="contentbox">
<div class="column full_size">
+
<div class="bevel tr"></div>
<h1>Description</h1>
+
<div class="content">
 
+
<h1> Expanding the Genetic Code </h1>
<p>Tell us about your project, describe what moves you and why this is something important for your team.</p>
+
<article>
 
+
We are exploring the application of unnatural base pairs as an expansion of the genetic code. To prevent loss of unnatural base pairs during replication, we will utilize several systems including CRISPR/Cas9. The expanded genetic code allows for the ribosomal incorporation of multiple non-canonical amino acids (ncAAs) into peptides. With their broad chemical and functional diversity, ncAAs provide a variety of promising applications including protein labeling, photocaging, structure analysis, and specific protein interactions. Therefore, our innovative toolkit for the translational incorporation of ncAAs in E. coli is a valuable contribution to iGEM. Directed evolution of tRNA/aminoacyl-tRNA synthetase pairs enables the site-specific incorporation of ncAAs into peptides. This approach results in an optimal orthogonality to the autologous translation apparatus and a high flexibility concerning the incorporation of multiple ncAAs. As proof of concept, we are developing a rapid test for prions and a new chromatography method for mild protein elution.  
 
+
<br>
<h5>What should this page contain?</h5>
+
<p>For more information visit our <b><a href="https://www.researchgate.net/publication/318084694_Expansion_of_the_genetic_code_for_the_translational_incorporation_of_non-canonical_amino_acids">project poster</a></b> on reasearch gate</p>
<ul>
+
</article>
<li> A clear and concise description of your project.</li>
+
        </div>
<li>A detailed explanation of why your team chose to work on this particular project.</li>
+
<div class="bevel bl"></div>
<li>References and sources to document your research.</li>
+
    </div>
<li>Use illustrations and other visual resources to explain your project.</li>
+
</div>
</ul>
+
</body>
 
+
<script>
 
+
$("#project").addClass("navbar active");
</div>
+
</script>
 
+
<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 be 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>
 
</html>
 
 
{{Team:Bielefeld-CeBiTec/Footer}}
 
{{Team:Bielefeld-CeBiTec/Footer}}

Latest revision as of 20:51, 27 August 2017

Expanding the Genetic Code

We are exploring the application of unnatural base pairs as an expansion of the genetic code. To prevent loss of unnatural base pairs during replication, we will utilize several systems including CRISPR/Cas9. The expanded genetic code allows for the ribosomal incorporation of multiple non-canonical amino acids (ncAAs) into peptides. With their broad chemical and functional diversity, ncAAs provide a variety of promising applications including protein labeling, photocaging, structure analysis, and specific protein interactions. Therefore, our innovative toolkit for the translational incorporation of ncAAs in E. coli is a valuable contribution to iGEM. Directed evolution of tRNA/aminoacyl-tRNA synthetase pairs enables the site-specific incorporation of ncAAs into peptides. This approach results in an optimal orthogonality to the autologous translation apparatus and a high flexibility concerning the incorporation of multiple ncAAs. As proof of concept, we are developing a rapid test for prions and a new chromatography method for mild protein elution.

For more information visit our project poster on reasearch gate