Difference between revisions of "Team:TecCEM/Parts"

m
Line 1: Line 1:
 
{{TecCEM}}
 
{{TecCEM}}
 
<html>
 
<html>
 +
<style>
 +
    div.parts-div a:vistied,
 +
    div.parts-div a:hover {
 +
        color: #333333 !important;
 +
        text-decoration: none !important;
 +
    }
  
 +
    div.parts-div a:hover {
 +
        font-weight: 500;
 +
    }
  
−
<div class="column full_size">
+
    div.parts-div a {
−
<h1>Parts</h1>
+
        color: #ff9d33;
−
<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>
+
</style>
−
</div>
+
<div id="gif-title" class="text-red">
−
 
+
    <img src="https://static.igem.org/mediawiki/2018/a/aa/T--TecCEM--Cells.gif" alt="Cell Gif">
−
<div class="column full_size">
+
    <h1>Parts Overview</h1>
−
<div class="highlight decoration_background">
+
−
<h3>Note</h3>
+
−
<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="wrapper">
 +
    <nav class="sidebar-index d-none d-md-block">
 +
        <div class="sidebar-header">
 +
            <h3>Parts/ Overview</h3>
 +
        </div>
 +
        <a href="#partsSubmenu" data-toggle="collapse" aria-expanded="false" data-offset="100" data-change="sidemenu">
 +
            <span data-change="el" class="d-inline-block open"></span>
 +
            Index
 +
        </a>
 +
        <ul class="collapse list-unstyled" id="partsSubmenu">
 +
            <li>
 +
                <a data-target="#K2719000">BBa_K2719000</a>
 +
            </li>
 +
            <li>
 +
                <a data-target="#K2719001">BBa_K2719001</a>
 +
            </li>
 +
            <li>
 +
                <a data-target="#K2719002">BBa_K2719002</a>
 +
            </li>
 +
            <li>
 +
                <a data-target="#K2719003">BBa_K2719003</a>
 +
            </li>
 +
            <li>
 +
                <a data-target="#K2719004">BBa_K2719004</a>
 +
            </li>
 +
            <li>
 +
                <a data-target="#K2719006">BBa_K2719006</a>
 +
            </li>
 +
            <li>
 +
                <a data-target="#K2719008">BBa_K2719008</a>
 +
            </li>
 +
        </ul>
 +
    </nav>
 +
    <div class="content parts-div">
 +
        <div class="container">
 +
            <div class="row">
 +
                <div class="col">
 +
                    <h1>Parts</h1>
 +
                    <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>
 +
                </div>
 +
            </div>
 +
        </div>
 +
    </div>
 
</div>
 
</div>
  
−
<div class="clear extra_space"></div>
 
−
<div class="line_divider"></div>
 
−
<div class="clear extra_space"></div>
 
  
−
 
−
 
−
 
−
 
−
<div class="column two_thirds_size">
 
−
<div class="highlight decoration_B_full">
 
−
 
−
<h3>Adding parts to the registry</h3>
 
−
<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>
 
−
<div class="button_link">
 
−
<a href="http://parts.igem.org/Add_a_Part_to_the_Registry">
 
−
ADD PARTS
 
−
</a>
 
−
</div>
 
−
 
−
</div>
 
−
</div>
 
−
 
−
 
−
 
−
<div class="column third_size">
 
−
<div class="highlight decoration_A_full">
 
−
<h3>Inspiration</h3>
 
−
<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>
 
−
</div>
 
−
</div>
 
−
 
−
 
−
<div class="clear extra_space"></div>
 
−
 
−
 
−
 
−
 
−
<div class="column full_size">
 
−
 
−
<h3>What information do I need to start putting my parts on the Registry?</h3>
 
−
<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>
 
−
 
−
</div>
 
−
 
−
 
−
<div class="clear extra_space"></div>
 
−
<div class="line_divider"></div>
 
−
<div class="clear extra_space"></div>
 
−
 
−
<div class="column full_size">
 
−
<h3>Part Table </h3>
 
−
 
−
<p>Please include a table of all the parts your team has made during your project on this page. Remember part characterization and measurement data must go on your team part pages on the Registry. </p>
 
−
 
−
</html>
 
−
<groupparts>iGEM18 TecCEM</groupparts>
 
−
<html>
 
−
</div>
 
 
</html>
 
</html>
 
{{TecCEM/Footer}}
 
{{TecCEM/Footer}}

Revision as of 23:03, 11 October 2018

Cell Gif

Parts Overview

Parts

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.