Difference between revisions of "Team:Toronto/Parts"

(Prototype team page)
 
Line 1: Line 1:
−
{{Toronto}}
 
 
<html>
 
<html>
 +
<!-- ####################################################### -->
 +
<!-- #  This html was produced by the igemwiki generator  # -->
 +
<!-- #  https://github.com/igemuoftATG/generator-igemwiki  # -->
 +
<!-- ####################################################### -->
  
 +
<!-- repo for this wiki: https://github.com/igemuoftATG/wiki2016 -->
 +
<!-- file built: Mon Oct 17 2016 23:59:11 GMT-0400 (EDT) -->
  
 +
</html>
 +
{{Toronto/head}}
 +
<html>
  
−
 
+
<div id="navigation">
−
 
+
<ul>
−
 
+
<li><a href="https://2016.igem.org/Team:Toronto"><span>home</span></a></li>
−
<div class="column full_size">
+
</li>
−
 
+
<li><a href="#"><span>team</span></a>
−
 
+
<ul>
−
<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>
+
<li><a href="https://2016.igem.org/Team:Toronto/Team"><span>team</span></a></li>
 +
</li>
 +
<li><a href="https://2016.igem.org/Team:Toronto/Collaborations"><span>collaborations</span></a></li>
 +
</li>
 +
</ul>
 +
<li><a href="#"><span>project</span></a>
 +
<ul>
 +
<li><a href="https://2016.igem.org/Team:Toronto/Description"><span>description</span></a></li>
 +
</li>
 +
<li><a href="https://2016.igem.org/Team:Toronto/Design"><span>design</span></a></li>
 +
</li>
 +
<li><a href="https://2016.igem.org/Team:Toronto/Experiments"><span>experiments</span></a></li>
 +
</li>
 +
<li><a href="https://2016.igem.org/Team:Toronto/Proof"><span>proof</span></a></li>
 +
</li>
 +
<li><a href="https://2016.igem.org/Team:Toronto/Demonstrate"><span>demonstrate</span></a></li>
 +
</li>
 +
<li><a href="https://2016.igem.org/Team:Toronto/Results"><span>results</span></a></li>
 +
</li>
 +
<li><a href="https://2016.igem.org/Team:Toronto/Notebook"><span>notebook</span></a></li>
 +
</li>
 +
</ul>
 +
<li class="active"><a href="#"><span>parts</span></a>
 +
<ul>
 +
<li class="active"><a href="https://2016.igem.org/Team:Toronto/Parts"><span>parts</span></a></li>
 +
</li>
 +
<li><a href="https://2016.igem.org/Team:Toronto/Basic_Part"><span>basic_part</span></a></li>
 +
</li>
 +
<li><a href="https://2016.igem.org/Team:Toronto/Composite_Part"><span>composite_part</span></a></li>
 +
</li>
 +
<li><a href="https://2016.igem.org/Team:Toronto/Part_Collection"><span>part_collection</span></a></li>
 +
</li>
 +
</ul>
 +
<li><a href="https://2016.igem.org/Team:Toronto/Safety"><span>safety</span></a></li>
 +
</li>
 +
<li><a href="https://2016.igem.org/Team:Toronto/Attributions"><span>attributions</span></a></li>
 +
</li>
 +
<li><a href="#"><span>human_practices</span></a>
 +
<ul>
 +
<li><a href="https://2016.igem.org/Team:Toronto/Human_Practices"><span>human_practices</span></a></li>
 +
</li>
 +
<li><a href="https://2016.igem.org/Team:Toronto/HP-Silver"><span>silver</span></a></li>
 +
</li>
 +
<li><a href="https://2016.igem.org/Team:Toronto/HP-Gold"><span>gold</span></a></li>
 +
</li>
 +
<li><a href="https://2016.igem.org/Team:Toronto/Integrated_Practices"><span>integrated_practices</span></a></li>
 +
</li>
 +
<li><a href="https://2016.igem.org/Team:Toronto/Engagement"><span>engagement</span></a></li>
 +
</li>
 +
</ul>
 +
<li><a href="#"><span>awards</span></a>
 +
<ul>
 +
<li><a href="https://2016.igem.org/Team:Toronto/Entrepreneurship"><span>entrepreneurship</span></a></li>
 +
</li>
 +
<li><a href="https://2016.igem.org/Team:Toronto/Hardware"><span>hardware</span></a></li>
 +
</li>
 +
<li><a href="https://2016.igem.org/Team:Toronto/Software"><span>software</span></a></li>
 +
</li>
 +
<li><a href="https://2016.igem.org/Team:Toronto/Measurement"><span>measurement</span></a></li>
 +
</li>
 +
<li><a href="https://2016.igem.org/Team:Toronto/Model"><span>model</span></a></li>
 +
</li>
 +
</ul>
 +
</ul>
 +
</div>
 +
<div class="content">
 +
<div class="content" id="content-main"><div class="row"><div class="col col-lg-8 col-md-12"><div class="content-main"><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>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>
 
<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>
−
 
+
<h5 id="note">Note</h5>
−
 
+
<p>Note that parts must be documented on the <a href="http://parts.igem.org/Main_Page">Registry</a>. This page serves to <em>showcase</em> 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>
+
<h5 id="adding-parts-to-the-registry">Adding parts to the registry</h5>
−
 
+
−
 
+
−
 
+
−
 
+
−
 
+
−
<div class="column half_size">
+
−
<div class="highlight">
+
−
<h5>Note</h5>
+
−
<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>
+
−
</div>
+
−
 
+
−
 
+
−
 
+
−
 
+
−
<div class="column half_size">
+
−
 
+
−
<h5>Adding parts to the registry</h5>
+
 
<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>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>
+
<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&#39;t need to send us the DNA sample before you create an entry for a part on the Registry. (However, you <strong>do</strong> need to send us the DNA sample before the Jamboree. If you don&#39;t send us a DNA sample of a part, that part will not be eligible for awards and medal criteria.)</p>
−
</div>
+
<h5 id="what-information-do-i-need-to-start-putting-my-parts-on-the-registry-">What information do I need to start putting my parts on the Registry?</h5>
−
 
+
−
 
+
−
 
+
−
 
+
−
 
+
−
<div class="column half_size">
+
−
 
+
−
<h5>What information do I need to start putting my parts on the Registry?</h5>
+
 
<p>The information needed to initially create a part on the Registry is:</p>
 
<p>The information needed to initially create a part on the Registry is:</p>
 
<ul>
 
<ul>
Line 54: Line 102:
 
<li>Design considerations</li>
 
<li>Design considerations</li>
 
</ul>
 
</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>
−
<p>
+
<h5 id="inspiration">Inspiration</h5>
−
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>
+
<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>
−
</div>
+
−
 
+
−
 
+
−
<div class="column half_size">
+
−
 
+
−
<h5>Inspiration</h5>
+
−
<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>
 
<ul>
−
<li><a href="https://2014.igem.org/Team:MIT/Parts"> 2014 MIT </a></li>
+
<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:Heidelberg/Parts">2014 Heidelberg</a></li>
 
<li><a href="https://2014.igem.org/Team:Tokyo_Tech/Parts">2014 Tokyo Tech</a></li>
 
<li><a href="https://2014.igem.org/Team:Tokyo_Tech/Parts">2014 Tokyo Tech</a></li>
 
</ul>
 
</ul>
 +
<h5 id="part-table">Part Table</h5>
 +
</div></div><div id="tableofcontents" class="tableofcontents affix sidebar col-lg-4 hidden-xs hidden-sm hidden-md visible-lg-3"><ul class="nav">
 +
<li><a href="#adding-parts-to-the-registry">Adding parts to the registry</a></li>
 +
<li><a href="#what-information-do-i-need-to-start-putting-my-parts-on-the-registry-">What information do I need to start putting my parts on the Registry?</a></li>
 +
<li><a href="#inspiration">Inspiration</a></li>
 +
<li><a href="#part-table">Part Table</a></li>
 +
</ul>
 +
</div></div></div>
 
</div>
 
</div>
−
 
−
<div class="column full_size">
 
−
<h5>Part Table </h5>
 
−
<div class="highlight">
 
−
 
−
 
−
</html>
 
−
<groupparts>iGEM2016 Example</groupparts>
 
−
<html>
 
−
</div>
 
−
</div>
 
−
 
−
 
−
 
−
 
 
</html>
 
</html>
 +
{{Toronto/footer}}

Revision as of 04:00, 18 October 2016

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 <groupparts> tag (see below) will generate a table with all of the parts that your team adds to your team sandbox.

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.

Note

Note that parts must be documented on the Registry. This page serves to showcase 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.

Adding parts to the registry

You can add parts to the Registry at our Add a Part to the Registry link.

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 do 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.)

What information do I need to start putting my parts on the Registry?

The information needed to initially create a part on the Registry is:

  • Part Name
  • Part type
  • Creator
  • Sequence
  • Short Description (60 characters on what the DNA does)
  • Long Description (Longer description of what the DNA does)
  • Design considerations

We encourage you to put up much more 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.

Inspiration

We have a created a collection of well documented parts that can help you get started.

You can also take a look at how other teams have documented their parts in their wiki:

Part Table