Difference between revisions of "Team:Macquarie Australia/Parts"

(Changed table nav colour)
(Added nav template and petri dish)
Line 1: Line 1:
 
{{Macquarie_Australia}}
 
{{Macquarie_Australia}}
 +
{{Macquarie_Australia/Nav4Parts}}
 
<html lang="en-AU">
 
<html lang="en-AU">
<title>Parts</title>
+
<title>Parts</title>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 +
<body>
  
<!-- html top nav menu start -->
+
<div class="contentContainer">
<table class="mainmenu" width="100%" cellspacing="0">
+
<tr height="2px"><td></td></tr>
+
<tr><td></td>
+
<td width="980px" align="left" bgColor="#ffffff" cellspacing="0" cellpadding="2px">
+
<table width="100%" align="center"></td>
+
</tr>
+
<tr height="30px"> <!-- #66cc66 light green; #009933 dark green -->
+
<td align="center" onMouseOver="this.bgColor='#ffffff'" onMouseOut="this.bgColor='#66cc66'" bgColor=#66cc66>
+
<a href="https://2015.igem.org/Team:Macquarie_Australia">Home</a></td>
+
<td align="center" onMouseOver="this.bgColor='#ffffff'" onMouseOut="this.bgColor='#66cc66'" bgColor=#66cc66>
+
<a href="https://2015.igem.org/Team:Macquarie_Australia/ProjectOverview">Project</a></td>
+
<td align="center" onMouseOver="this.bgColor='#ffffff'" onMouseOut="this.bgColor='#66cc66'" bgColor=#66cc66>
+
<a href="https://2015.igem.org/Team:Macquarie_Australia/Modeling">Modelling</a></td>
+
<td class="menuHighlight" align="center" onMouseOver="this.bgColor='#009933'" onMouseOut="this.bgColor='#009933'" bgColor=#009933>
+
<a href="https://2015.igem.org/Team:Macquarie_Australia/PartsOverview">Parts</a></td>
+
<td align="center" onMouseOver="this.bgColor='#ffffff'" onMouseOut="this.bgColor='#66cc66'" bgColor=#66cc66>
+
<a href="https://2015.igem.org/Team:Macquarie_Australia/Practices">Human Practices</a></td>
+
<td align="center" onMouseOver="this.bgColor='#ffffff'" onMouseOut="this.bgColor='#66cc66'" bgColor=#66cc66>
+
<a href="https://2015.igem.org/Team:Macquarie_Australia/Team">Team</a></td>
+
<td align="center" onMouseOver="this.bgColor='#ffffff'" onMouseOut="this.bgColor='#66cc66'" bgColor=#66cc66>
+
<a href="https://2015.igem.org/Team:Macquarie_Australia/Attributions">Attributions</a></td>
+
<td align="center" onMouseOver="this.bgColor='#ffffff'" onMouseOut="this.bgColor='#66cc66'" bgColor=#66cc66>
+
<a href="https://2015.igem.org/Team:Macquarie_Australia/Sitemap">Sitemap</a></td>
+
</tr>
+
</table>
+
<!-- end of html top nav menu -->
+
  
<body>
+
<div class="centreStuffInline">
 +
<figure class="specialInline"><a href="https://2015.igem.org/Team:Macquarie_Australia/PartsOverview"><img src="https://static.igem.org/mediawiki/2015/9/9a/MqAust_3Parts_v05a-150dpi.png" width="220px" alt="Link to Parts page"></a></figure>
 +
</div>
  
<div class="contentContainer">
+
<h2> Part Documentation</h2>
 +
<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>
  
<h2> Part Documentation</h2>
+
<h4>Note</h4>
<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>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>
<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 class="highlightBox">
+
<h4>Adding parts to the registry</h4>
<h4>Note</h4>
+
<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>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>
+
<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>
+
  
<h4>Adding parts to the registry</h4>
+
<h4>What information do I need to start putting my parts on the Registry?</h4>
<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>The information needed to initially create a part on the Registry is:</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>
+
<ul>
 
+
<h4>What information do I need to start putting my parts on the Registry?</h4>
+
<p>The information needed to initially create a part on the Registry is:</p>
+
<ul>
+
 
<li>Part Name</li>
 
<li>Part Name</li>
 
<li>Part type</li>
 
<li>Part type</li>
Line 59: Line 33:
 
<li>Long Description (Longer description of what the DNA does)</li>
 
<li>Long Description (Longer description of what the DNA does)</li>
 
<li>Design considerations</li>
 
<li>Design considerations</li>
</ul>
+
</ul>
<p>We encourage you to put up much more information as you gather it. If you have images, plots, characterization data and other information, please also put it up on the part page.</p>
+
<p>We encourage you to put up much more information as you gather it. If you have images, plots, characterization data and other information, please also put it up on the part page.</p>
  
<h4>Inspiration</h4>
+
<h4>Inspiration</h4>
<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>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>
+
<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>
  
<h4>Part Table </h4>
+
<h4>Part Table </h4>
</html>
+
<p>Table goes here</p>
<groupparts>iGEM2015 Example</groupparts>
+
<html>
+
  
</div> <!-- contentContainer end -->
+
</div> <!-- contentContainer end -->
  
</body>
+
</body>
 
</html>
 
</html>

Revision as of 08:25, 8 September 2015

Parts
Link to Parts page

Part Documentation

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

Table goes here