Team:Example C/Parts

From 2014.igem.org

(Difference between revisions)
Line 1: Line 1:
-
<!-- *** What falls between these lines is the Alert Box!  You can remove it from your pages once you have read and understood the alert *** -->
 
-
 
-
 
{{CSS/Main}}
{{CSS/Main}}
Line 66: Line 63:
</table>
</table>
-
</tr>
 
-
</table>
 
<!--end navigation menu -->
<!--end navigation menu -->
-
<table width="70%" align="center">
+
</tr>
 +
 
 +
 
 +
</tr>
 +
 +
 
 +
 
 +
 
 +
 
 +
</td>
<tr> <td colspan="3"  height="15px"> </td></tr>
<tr> <td colspan="3"  height="15px"> </td></tr>
Line 76: Line 80:
-
 
+
<!--Parts Submitted to the Registry -->
-
<!--text -->
+
<tr><td > <h3> Parts Submitted to the Registry </h3></td>
-
<tr><td colspan="3"> <h3> Parts Submitted to the Registry </h3></td></tr>
+
<td ></td >
 +
<td > <h3> When should you put parts into the Registry?</h3></td>
 +
</tr>
<tr>
<tr>
<td width="45%"  valign="top">  
<td width="45%"  valign="top">  
-
 
<p>
<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 submit them to 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.   
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 submit them to 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.   
Line 92: Line 97:
Remember that the goal of proper part documentation is to describe and define a part, so that it can be used without a need 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.
Remember that the goal of proper part documentation is to describe and define a part, so that it can be used without a need 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>
-
 
-
 
</td>
</td>
-
 
<td > </td>
<td > </td>
-
<tr><td colspan="3"> <h3>When should you put parts into the Registry? </h3></td>
+
<td width="45%" valign="top">
-
<td width="45%" valign="top">  
+
-
 
+
<p>
<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 better recall you will have of all details surrounding your parts. Remember you don't need to send us the DNA to create an entry for a part on the Registry. However, you must send us the sample/DNA before the Jamboree. Only parts for which you have sent us samples/DNA are eligible for awards and medal requirements.  
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 better recall you will have of all details surrounding your parts. Remember you don't need to send us the DNA to create an entry for a part on the Registry. However, you must send us the sample/DNA before the Jamboree. Only parts for which you have sent us samples/DNA are eligible for awards and medal requirements.  
</p>
</p>
</td>
</td>
-
 
</tr>
</tr>
-
<tr><td colspan="3"> <h3> What information do I need to start putting my parts on the Registry? </h3></td></tr>
+
<tr> <td colspan="3" height="15px"> </td></tr>
-
<tr>
+
<tr><td bgColor="#e7e7e7" colspan="3" height="1"> </tr>
-
<td width="45%"  valign="top">  
+
 
 +
 
 +
<tr><td > <h3> What information do I need to start putting my parts on the Registry?</h3></td>
 +
<td ></td >
 +
<td > <h3> Parts Table</h3></td>
 +
</tr>
 +
<td width="45%" valign="top">
<p>
<p>
The information needed to initially create a part on the Registry is:
The information needed to initially create a part on the Registry is:
Line 136: Line 141:
</td>
</td>
-
 
+
<td> </td>
-
<tr><td colspan="3"> <h3>Parts Table</h3></td></tr>
+
<td width="45%" valign="top">  
-
<td width="45%" valign="top">  
+
-
 
+
<p>
<p>
Any parts your team has created will appear in this table below:
Any parts your team has created will appear in this table below:
Line 146: Line 149:
<groupparts>iGEM013 Example_C</groupparts>
<groupparts>iGEM013 Example_C</groupparts>
</td>
</td>
-
 
</tr>
</tr>
</table>
</table>
-
</html>
 

Revision as of 03:07, 24 March 2014


WELCOME TO iGEM 2014!

Your team has been approved and you are ready to start the iGEM season!
On this page you can document your project, introduce your team members, document your progress
and share your iGEM experience with the rest of the world!


Click here to edit this page!

Home Team Official Team Profile Project Parts Modeling Notebook Safety Attributions

Parts Submitted to the Registry

When should you put parts into 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 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 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 likely 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, so that it can be used without a need 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.

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 better recall you will have of all details surrounding your parts. Remember you don't need to send us the DNA to create an entry for a part on the Registry. However, you must send us the sample/DNA before the Jamboree. Only parts for which you have sent us samples/DNA are eligible for awards and medal requirements.

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

Parts Table

The information needed to initially 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

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. Check out part BBa_K404003 for an excellent example of a highly characterized part.

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

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

iGEM013 Example_C

Retrieved from "http://2014.igem.org/Team:Example_C/Parts"