Team:Example C/Parts

From 2014.igem.org

(Difference between revisions)
Line 31: Line 31:
 +
<html>
-
An important aspect of the iGEM competition is the use and creation of standard  biological parts. Each team will make new parts during iGEM and will place them in the [http://partsregistry.org Registry of Standard Biological Parts]. The iGEM software provides an easy way to present the parts your team has created . The "groupparts" tag will generate a table with all of the parts that your team adds to your team sandbox.  Note that if you want to document a part you need to document it on the [http://partsregistry.org Registry], not on your team wiki.
+
<h2>Parts Submitted to the Registry</h2>
-
Remember that the goal of proper part documentation is to describe and define a part such that it can be used without a need to refer to the primary literature. The next iGEM team 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>
 +
An important aspect of the iGEM competition is the use and creation of standard  biological parts. Each team will make new parts during iGEM and will place them in the <a href="http://partsregistry.org"> Registry of Standard Biological Parts</a>. The iGEM software provides an easy way to present the parts your team has created . The "groupparts" tag will generate a table with all of the parts that your team adds to your team sandbox.   
 +
<p>
 +
<strong>Note that if you want to document a part you need to document it on the <a href="http://partsregistry.org Registry"> Registry</a>, not on your team wiki.</strong> Future teams and other users and are much more likley to find parts on the Registry than on your team wiki.
 +
</p>
 +
<p>
 +
Remember that the goal of proper part documentation is to describe and define a part such that it can be used without a need to refer to the primary literature. iGEM teams 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>
 +
 +
<h2>When should you put parts into the Registry?</h2>
 +
 +
<p>
 +
As soon as possible! 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 sooner other teams will see them and can request them in collaborations. Remember you don't need to send us the DNA to create a part on the Registry, although you should before the Jamboree.
 +
</p>
 +
 +
<h2>What information do I need to start putting my parts on the Registry?</h2>
 +
 +
<p>
 +
The minimum information needed to create a part on the Registry is:
 +
</p>
 +
<ol>
 +
 +
<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>
 +
</ol>
 +
</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>
 +
 +
<h2>Parts Table</h2>
 +
 +
<p>
 +
Any parts your team has created will appear in this table below:
 +
</p>
 +
 +
</html>
<groupparts>iGEM013 Example_C</groupparts>
<groupparts>iGEM013 Example_C</groupparts>

Revision as of 20:44, 21 March 2014


This is a template page. READ THESE INSTRUCTIONS.
You are provided with this team page template with which to start the iGEM season. You may choose to personalize it to fit your team but keep the same "look." Or you may choose to take your team wiki to a different level and design your own wiki. You can find some examples HERE.
You MUST have all of the pages listed in the menu below with the names specified. PLEASE keep all of your pages within your teams namespace.


Home Team Our Lab Official Team Profile Project Parts Submitted to the Registry Modeling Notebook Safety Attributions


Parts Submitted to the Registry

An important aspect of the iGEM competition is the use and creation of standard biological parts. Each team will make new parts during iGEM and will place them in the Registry of Standard Biological Parts. The iGEM software provides an easy way to present the parts your team has created . The "groupparts" tag will generate a table with all of the parts that your team adds to your team sandbox.

Note that if you want to document a part you need to document it on the Registry, not on your team wiki. Future teams and other users and are much more likley to find parts on the Registry than on your team wiki.

Remember that the goal of proper part documentation is to describe and define a part such that it can be used without a need to refer to the primary literature. iGEM teams 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.

When should you put parts into the Registry?

As soon as possible! 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 sooner other teams will see them and can request them in collaborations. Remember you don't need to send us the DNA to create a part on the Registry, although you should before the Jamboree.

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

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

  1. Part Name
  2. Part type
  3. Creator
  4. Sequence
  5. Short Description (60 characters on what the DNA does)
  6. Long Description (Longer description of what the DNA does)
  7. Design considerations

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

Parts Table

Any parts your team has created will appear in this table below:

<groupparts>iGEM013 Example_C</groupparts>