Difference between revisions of "Team:Michigan/Parts"

(Prototype team page)
 
Line 2: Line 2:
 
<html>
 
<html>
  
−
<h2> Part Documentation</h2>
+
<style="css/text">
  
−
<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>
+
      p {
−
<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>
+
            margin: 10px;
 +
      }
  
 +
  
−
<div class="highlightBox">
+
</style>
−
<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>Adding parts to the registry</h4>
+
−
<p>You can add parts to the Registry at our <a href="http://parts.igem.org/Add_a_Part_to_the_Registry">Add a Part to the Registry</a> link.</p>
+
−
<p>We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The sooner you put up your parts, the better you will remember all the details about your parts. Remember, you don't need to send us the DNA sample before you create an entry for a part on the Registry. (However, you <b>do</b> need to send us the DNA sample before the Jamboree. If you don't send us a DNA sample of a part, that part will not be eligible for awards and medal criteria.)</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>
+
  
 +
<h2> Part Documentation</h2>
  
 +
<p>Switch 1.0 (adapted for thrombin) with additional cut sites and a GFP reporter was submitted as a part.  This part has been demonstrated as an RNA toehold switch, which responds to a specific DNA trigger and expresses GFP, with low background, as seen in Figure 1 of the results (LINK) section.  This provides a starting point for other teams looking to adapt toehold switches.<br><br>
  
−
<h4>Part Table </h4>
+
In order to ease the cloning process for future teams, an additional HindIII cut site was added between the switch and GFP.  The HindIII cut site combined with the iGEM cut sites that surround the switch makes it easy to substitute the reporter.<br><br>
−
</html>
+
−
<groupparts>iGEM015 Example</groupparts>
+
−
<html>
+
  
 +
Additionally, the part submitted gives the many other teams inspired by the same publications, an easy control for in vitro translation reactions.  Since it already contains a full switch and reporter, it can be transformed and purified and then used directly with a cell-free expression system, without any further cloning.  The trigger is short enough to be quickly and cheaply bought as a DNA oligo.  Thus, future teams exploring cell-free expression systems can test their systems induced with a DNA oligo (positive reaction control) and without (negative reaction control).
  
  
−
</div>
 
 
</html>
 
</html>

Revision as of 00:53, 19 September 2015

p { margin: 10px; }

Part Documentation

Switch 1.0 (adapted for thrombin) with additional cut sites and a GFP reporter was submitted as a part. This part has been demonstrated as an RNA toehold switch, which responds to a specific DNA trigger and expresses GFP, with low background, as seen in Figure 1 of the results (LINK) section. This provides a starting point for other teams looking to adapt toehold switches.

In order to ease the cloning process for future teams, an additional HindIII cut site was added between the switch and GFP. The HindIII cut site combined with the iGEM cut sites that surround the switch makes it easy to substitute the reporter.

Additionally, the part submitted gives the many other teams inspired by the same publications, an easy control for in vitro translation reactions. Since it already contains a full switch and reporter, it can be transformed and purified and then used directly with a cell-free expression system, without any further cloning. The trigger is short enough to be quickly and cheaply bought as a DNA oligo. Thus, future teams exploring cell-free expression systems can test their systems induced with a DNA oligo (positive reaction control) and without (negative reaction control).