Difference between revisions of "Team:Washington/Parts"

m
Line 145: Line 145:
 
     <div id="contentContainer">
 
     <div id="contentContainer">
  
<h2> Part Documentation</h2>
+
<h2>
 
+
            <div id="Biobrick"> Biobricks </div>
<p>Each team will make new parts during iGEM and will submit them to the Registry of Standard Biological Parts. The iGEM software provides an easy way to present the parts your team has created. The <code>&lt;groupparts&gt;</code> tag (see below) will generate a table with all of the parts that your team adds to your team sandbox.</p>
+
        </h2>
<p>Remember that the goal of proper part documentation is to describe and define a part, so that it can be used without needing to refer to the primary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper references to acknowledge previous authors and to provide for users who wish to know more.</p>
+
 
+
 
+
<div class="highlightBox">
+
<h4>Note</h4>
+
<p>Note that parts must be documented on the <a href="http://parts.igem.org/Main_Page"> Registry</a>. This page serves to <i>showcase</i> the parts you have made. Future teams and other users and are much more likely to find parts by looking in the Registry than by looking at your team wiki.</p>
+
</div>
+
 
+
  
 
<h4>Parts in the registry</h4>
 
<h4>Parts in the registry</h4>
Line 166: Line 158:
 
<html><h1 id='Sources'><p align=right><a href="#Sources"><font size="3">[Top]</font></h1></html>
 
<html><h1 id='Sources'><p align=right><a href="#Sources"><font size="3">[Top]</font></h1></html>
  
      <h2>
+
      <h2>Apatazyme</h2>
            <div id="Biobrick"> Biobricks </div>
+
        </h2>
+
  
 
<h2>yeVenus-TheoA; Coding sequence for enhanced YFP and theophylline-sensative aptazyme</h2>
 
<h2>yeVenus-TheoA; Coding sequence for enhanced YFP and theophylline-sensative aptazyme</h2>
Line 180: Line 170:
 
<p>This part, yeVenus-PEST-TheoA, contains the coding sequence for a hybrid protein made of yeast enhanced yellow fluorescent protein (yeVenus) fused in frame with the CDS of the PEST-rich 178 c-terminal residues of Cln2, which targets the protein for ubiquitin dependent degradation. These coding sequences are fused with a gene for a theophylline sensitive riboswitch aptazyme. The aptazyme portion of the transcript self-cleaves in the absence of theophylline and no YFP should be produced. The theophylline bound state stabilizes the transcript, which translates to the protein and fluorescence should be observed.</p>
 
<p>This part, yeVenus-PEST-TheoA, contains the coding sequence for a hybrid protein made of yeast enhanced yellow fluorescent protein (yeVenus) fused in frame with the CDS of the PEST-rich 178 c-terminal residues of Cln2, which targets the protein for ubiquitin dependent degradation. These coding sequences are fused with a gene for a theophylline sensitive riboswitch aptazyme. The aptazyme portion of the transcript self-cleaves in the absence of theophylline and no YFP should be produced. The theophylline bound state stabilizes the transcript, which translates to the protein and fluorescence should be observed.</p>
  
<h4>What information do I need to start putting my parts on the Registry?</h4>
 
<p>The information needed to initially create a part on the Registry is:</p>
 
<ul>
 
<li>Part Name</li>
 
<li>Part type</li>
 
<li>Creator</li>
 
<li>Sequence</li>
 
<li>Short Description (60 characters on what the DNA does)</li>
 
<li>Long Description (Longer description of what the DNA does)</li>
 
<li>Design considerations</li>
 
</ul>
 
 
<p>
 
We encourage you to put up <em>much more</em> information as you gather it over the summer. If you have images, plots, characterization data and other information, please also put it up on the part page. </p>
 
 
 
 
 
 
 
<h4>Inspiration</h4>
 
<p>We have a created  a <a href="http://parts.igem.org/Well_Documented_Parts">collection of well documented parts</a> that can help you get started.</p>
 
 
<p> You can also take a look at how other teams have documented their parts in their wiki:</p>
 
<ul>
 
<li><a href="https://2014.igem.org/Team:MIT/Parts"> 2014 MIT </a></li>
 
<li><a href="https://2014.igem.org/Team:Heidelberg/Parts"> 2014 Heidelberg</a></li>
 
<li><a href="https://2014.igem.org/Team:Tokyo_Tech/Parts">2014 Tokyo Tech</a></li>
 
</ul>
 
 
 
 
<h4>Part Table </h4>
 
</html>
 
<groupparts>iGEM015 Example</groupparts>
 
<html>
 
  
  

Revision as of 03:27, 19 September 2015



Biobricks

Parts in the registry

<groupparts>iGEM015 Washington</groupparts>

We also have an automatically generated Team Parts page.

[Top]

Apatazyme

yeVenus-TheoA; Coding sequence for enhanced YFP and theophylline-sensative aptazyme

<a href="http://parts.igem.org/Part:BBa_K1711001">http://parts.igem.org/Part:BBa_K1711001</a>

The part contains the coding sequence for yeast enhanced yellow fluorescent protein (yeVenus), linked to it is a gene for a theophylline sensitive riboswitch aptazyme. The aptazyme portion of the transcript self-cleaves in the absence of theophylline and no YFP should be produced. The theophylline bound state stabilizes the transcript, which translates to the protein and fluorescence should be observed.

yeVenus-PEST-TheoA; Coding sequence for destabilized YFP Venus and theophylline-sensitive aptazyme

<a href="http://parts.igem.org/Part:BBa_K1711002">http://parts.igem.org/Part:BBa_K1711002</a>

This part, yeVenus-PEST-TheoA, contains the coding sequence for a hybrid protein made of yeast enhanced yellow fluorescent protein (yeVenus) fused in frame with the CDS of the PEST-rich 178 c-terminal residues of Cln2, which targets the protein for ubiquitin dependent degradation. These coding sequences are fused with a gene for a theophylline sensitive riboswitch aptazyme. The aptazyme portion of the transcript self-cleaves in the absence of theophylline and no YFP should be produced. The theophylline bound state stabilizes the transcript, which translates to the protein and fluorescence should be observed.


</div> </div> </html>