Team:Example C/Parts

From 2014.igem.org

(Difference between revisions)
 
(17 intermediate revisions not shown)
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}}
 +
 
<html>
<html>
-
<div id="box" style="width: 700px; margin-left: 137px; padding: 5px; border: 3px solid #000; background-color: #fe2b33;">
+
<style type="text/css">
-
<div id="template" style="text-align: center; font-weight: bold; font-size: large; color: #f6f6f6; padding: 5px;">
+
#groupparts {text-align: center; margin-left: auto; margin-right: auto;}
-
This is a template page. READ THESE INSTRUCTIONS.
+
</style>
-
</div>
+
<!--main content -->
-
<div id="instructions" style="text-align: center; font-weight: normal; font-size: small; color: #f6f6f6; padding: 5px;">
+
<table width="70%" align="center">
-
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 <a href="https://2008.igem.org/Help:Template/Examples">HERE</a>.
+
-
</div>
+
-
<div id="warning" style="text-align: center; font-weight: bold; font-size: small; color: #f6f6f6; padding: 5px;">
+
-
You <strong>MUST</strong>  have all of the pages listed in the menu below with the names specified.  PLEASE keep all of your pages within your teams namespace. 
+
-
</div>
+
-
</div>
+
-
</html>
+
-
<!-- *** End of the alert box *** -->
 
-
{| style="color:#1b2c8a;background-color:#0c6;" cellpadding="3" cellspacing="1" border="1" bordercolor="#fff" width="62%" align="center"
+
<!--welcome box -->
-
!align="center"|[[Team:Example_C|Home]]
+
<tr>
-
!align="center"|[[Team:Example_C/Team|Team]]
+
<td style="border:1px solid black;" colspan="3" align="center" height="150px" bgColor=#FF404B>
-
!align="center"|[[Team:Example_C/Our Lab|Our Lab]]
+
<h1 >WELCOME TO iGEM 2014! </h1>
-
!align="center"|[https://igem.org/Team.cgi?year=2013&team_name=Example_C Official Team Profile]
+
<p>Your team has been approved and you are ready to start the iGEM season!
-
!align="center"|[[Team:Example_C/Project|Project]]
+
<br>On this page you can document your project, introduce your team members, document your progress <br> and share your iGEM experience with the rest of the world! </p>
-
!align="center"|[[Team:Example_C/Parts|Parts Submitted to the Registry]]
+
<br>
-
!align="center"|[[Team:Example_C/Modeling|Modeling]]
+
<p style="color:#E7E7E7"> <a href="https://2014.igem.org/wiki/index.php?title=Team:Example_C/Parts&action=edit"style="color:#FFFFFF"> Click here  to edit this page!</a> </p>
-
!align="center"|[[Team:Example_C/Notebook|Notebook]]
+
</td>
-
!align="center"|[[Team:Example_C/Safety|Safety]]
+
</tr>
-
!align="center"|[[Team:Example_C/Attributions|Attributions]]
+
-
|}
+
 +
<tr> <td colspan="3"  height="5px"> </td></tr>
 +
<!-- end welcome box -->
 +
<tr>
-
<html>
+
<!--navigation menu -->
 +
<td align="center" colspan="3">
 +
 
 +
<table  width="100%">
 +
<tr heigth="15px"></tr>
 +
<tr heigth="75px">
 +
 
 +
 
 +
<td style="border:1px solid black;" align="center" height ="45px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7> 
 +
<a href="https://2014.igem.org/Team:Example_C"style="color:#000000">Home </a> </td>
 +
 
 +
<td style="border:1px solid black;" align="center" height ="45px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7>
 +
<a href="https://2014.igem.org/Team:Example_C/Team"style="color:#000000"> Team </a> </td>
 +
 
 +
<td style="border:1px solid black;" align="center"  height ="45px"  onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7>
 +
<a href="https://igem.org/Team.cgi?year=2014&team_name=Example_C"style="color:#000000"> Official Team Profile </a></td>
 +
 
 +
<td style="border:1px solid black" align="center"  height ="45px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7> 
 +
<a href="https://2014.igem.org/Team:Example_C/Project"style="color:#000000"> Project</a></td>
 +
 
 +
<td style="border:1px solid black;" align="center"  height ="45px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7>
 +
<a href="https://2014.igem.org/Team:Example_C/Parts"style="color:#000000"> Parts</a></td>
 +
 
 +
<td style="border:1px solid black;" align="center" height ="45px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7>
 +
<a href="https://2014.igem.org/Team:Example_C/Modeling"style="color:#000000"> Modeling</a></td>
 +
 
 +
<td style="border:1px solid black;" align="center" height ="45px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7> 
 +
<a href="https://2014.igem.org/Team:Example_C/Notebook"style="color:#000000"> Notebook</a></td>
 +
 
 +
<td style="border:1px solid black;" align="center"  height ="45px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7>
 +
<a href="https://2014.igem.org/Team:Example_C/Safety"style=" color:#000000"> Safety </a></td>
 +
 
 +
<td style="border:1px solid black;" align="center"  height ="45px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7>
 +
<a href="https://2014.igem.org/Team:Example_C/Attributions"style="color:#000000"> Attributions </a></td>
 +
 
 +
 
 +
<td align ="center"> <a href="https://2014.igem.org/Main_Page"> <img src="https://static.igem.org/mediawiki/igem.org/6/60/Igemlogo_300px.png" width="55px"></a> </td>
 +
</tr>
 +
</table>
 +
 
 +
<!--end navigation menu -->
 +
</tr>
 +
 
 +
 
 +
</tr>
 +
 +
 
 +
 
 +
 
 +
 
 +
</td>
 +
 
 +
<tr> <td colspan="3"  height="15px"> </td></tr>
 +
<tr><td bgColor="#e7e7e7" colspan="3" height="1px"> </tr>
 +
<tr> <td colspan="3"  height="5px"> </td></tr>
-
<h2>Parts Submitted to the Registry</h2>
 
 +
<!--Parts Submitted to the Registry  -->
 +
<tr><td > <h3> Parts Submitted to the Registry </h3></td>
 +
<td ></td >
 +
<td > <h3>What information do I need to start putting my parts on the Registry? </h3></td>
 +
</tr>
 +
<tr>
 +
<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 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.   
+
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.   
<p>
<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.  
+
<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 likely to find parts on the Registry than on your team wiki.  
</p>
</p>
<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.
+
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>
-
<h2>When should you put parts into the Registry?</h2>
+
 
 +
 
 +
<h3>When should you put parts into the Registry?</h3>
<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 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.
+
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>
-
<h2>What information do I need to start putting my parts on the Registry?</h2>
+
<td > </td>
 +
<td width="45%" valign="top">
<p>
<p>
-
The minimum information needed to create a part on the Registry is:
+
The information needed to initially create a part on the Registry is:
</p>
</p>
<ol>
<ol>
Line 67: Line 125:
<li>Design considerations</li>
<li>Design considerations</li>
</ol>
</ol>
 +
 +
<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. Check out part <a href="http://parts.igem.org/Part:BBa_K404003">BBa_K404003</a> for an excellent example of a highly characterized part.
</p>
</p>
Line 72: Line 133:
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.
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>
 +
</td>
 +
</tr>
-
<h2>Parts Table</h2>
 
-
<p>
+
<tr> <td colspan="3"  height="15px"> </td></tr>
-
Any parts your team has created will appear in this table below:
+
-
</p>
+
 +
<tr><td colspan="3" > <h3> Parts Table</h3></td></tr>
 +
 +
 +
<tr><td width="45%" colspan="3"  valign="top">
 +
Any parts your team has created will appear in this table below:</td></tr>
 +
 +
</table>
</html>
</html>
 +
<groupparts>iGEM013 Example_C</groupparts>
<groupparts>iGEM013 Example_C</groupparts>

Latest revision as of 16:03, 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

What information do I need to start putting my parts on 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.

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

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.

Parts Table

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

<groupparts>iGEM013 Example_C</groupparts>

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