Team:Melbourne/Parts

From 2014.igem.org

(Difference between revisions)
(Prototype team page)
 
(3 intermediate revisions not shown)
Line 1: Line 1:
-
{{CSS/Main}}
+
<html>
 +
<link href='http://fonts.googleapis.com/css?family=Lato:400,900' rel='stylesheet' type='text/css'>
 +
<style>
 +
/* CSS Document */
 +
/*! normalize.css v2.1.2 | MIT License | git.io/normalize */
 +
/* ==========================================================================
 +
  HTML5 display definitions
 +
  ========================================================================== */
-
<html>
+
/**
-
<style type="text/css">
+
* Correct `block` display not defined in IE 8/9.
-
#groupparts {text-align: center; margin-left: auto; margin-right: auto;}
+
*/
-
</style>
+
-
<!--main content -->
+
-
<table width="70%" align="center">
+
 +
article,
 +
aside,
 +
details,
 +
figcaption,
 +
figure,
 +
footer,
 +
header,
 +
hgroup,
 +
main,
 +
nav,
 +
section,
 +
summary {
 +
    display: block;
 +
}
-
<!--welcome box -->
+
/**
-
<tr>
+
* Correct `inline-block` display not defined in IE 8/9.
-
<td style="border:1px solid black;" colspan="3" align="center" height="150px" bgColor=#FF404B>
+
  */
-
<h1 >WELCOME TO iGEM 2014! </h1>
+
-
<p>Your team has been approved and you are ready to start the iGEM season!
+
-
<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>
+
-
<br>
+
-
<p style="color:#E7E7E7"> <a href="https://2014.igem.org/wiki/index.php?title=Team:Melbourne/Parts&action=edit"style="color:#FFFFFF"> Click here to edit this page!</a> </p>
+
-
</td>
+
-
</tr>
+
-
<tr> <td colspan="3"  height="5px"> </td></tr>
+
audio,
-
<!-- end welcome box -->
+
canvas,
-
<tr>
+
video {
 +
    display: inline-block;
 +
}
-
<!--navigation menu -->
+
/**
-
<td align="center" colspan="3">
+
* Prevent modern browsers from displaying `audio` without controls.
 +
* Remove excess height in iOS 5 devices.
 +
*/
-
<table  width="100%">
+
audio:not([controls]) {
-
<tr heigth="15px"></tr>
+
    display: none;
-
<tr heigth="75px">
+
    height: 0;
 +
}
 +
/**
 +
* Address styling not present in IE 8/9.
 +
*/
-
<td style="border:1px solid black;" align="center" height ="45px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7> 
+
[hidden] {
-
<a href="https://2014.igem.org/Team:Melbourne"style="color:#000000">Home </a> </td>
+
    display: none;
 +
}
-
<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:Melbourne/Team"style="color:#000000"> Team </a> </td>
+
  Base
 +
  ========================================================================== */
-
<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=Melbourne"style="color:#000000"> Official Team Profile </a></td>
+
  * 1. Set default font family to sans-serif.
 +
* 2. Prevent iOS text size adjust after orientation change, without disabling
 +
*    user zoom.
 +
*/
-
<td style="border:1px solid black" align="center"  height ="45px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7> 
+
html {
-
<a href="https://2014.igem.org/Team:Melbourne/Project"style="color:#000000"> Project</a></td>
+
    font-family: sans-serif; /* 1 */
 +
    -ms-text-size-adjust: 100%; /* 2 */
 +
    -webkit-text-size-adjust: 100%; /* 2 */
 +
}
-
<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:Melbourne/Parts"style="color:#000000"> Parts</a></td>
+
  * Remove default margin.
 +
*/
-
<td style="border:1px solid black;" align="center" height ="45px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7>
+
body {
-
<a href="https://2014.igem.org/Team:Melbourne/Modeling"style="color:#000000"> Modeling</a></td>
+
    margin: 0;
 +
}
-
<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:Melbourne/Notebook"style="color:#000000"> Notebook</a></td>
+
  Links
 +
  ========================================================================== */
-
<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:Melbourne/Safety"style=" color:#000000"> Safety </a></td>
+
  * Address `outline` inconsistency between Chrome and other browsers.
 +
*/
-
<td style="border:1px solid black;" align="center"  height ="45px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7>
+
a:focus {
-
<a href="https://2014.igem.org/Team:Melbourne/Attributions"style="color:#000000"> Attributions </a></td>
+
    outline: thin dotted;
 +
}
 +
/**
 +
* Improve readability when focused and also mouse hovered in all browsers.
 +
*/
-
<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>
+
a:active,
-
</tr>
+
a:hover {
-
</table>
+
    outline: 0;
 +
}
-
<!--end navigation menu -->
+
/* ==========================================================================
-
</tr>
+
  Typography
 +
  ========================================================================== */
 +
/**
 +
* Address variable `h1` font-size and margin within `section` and `article`
 +
* contexts in Firefox 4+, Safari 5, and Chrome.
 +
*/
-
</tr>
+
h1 {
-
+
    font-size: 2em;
 +
    margin: 0.67em 0;
 +
}
 +
/**
 +
* Address styling not present in IE 8/9, Safari 5, and Chrome.
 +
*/
 +
abbr[title] {
 +
    border-bottom: 1px dotted;
 +
}
 +
/**
 +
* Address style set to `bolder` in Firefox 4+, Safari 5, and Chrome.
 +
*/
-
</td>
+
b,
 +
strong {
 +
    font-weight: bold;
 +
}
-
<tr> <td colspan="3"  height="15px"> </td></tr>
+
/**
-
<tr><td bgColor="#e7e7e7" colspan="3" height="1px"> </tr>
+
* Address styling not present in Safari 5 and Chrome.
-
<tr> <td colspan="3" height="5px"> </td></tr>
+
  */
 +
dfn {
 +
    font-style: italic;
 +
}
-
<!--Parts Submitted to the Registry -->
+
/**
-
<tr><td > <h3> Parts Submitted to the Registry </h3></td>
+
* Address differences between Firefox and other browsers.
-
<td ></td >
+
*/
-
<td > <h3>What information do I need to start putting my parts on the Registry? </h3></td>
+
 
 +
hr {
 +
    -moz-box-sizing: content-box;
 +
    box-sizing: content-box;
 +
    height: 0;
 +
}
 +
 
 +
/**
 +
* Address styling not present in IE 8/9.
 +
*/
 +
 
 +
mark {
 +
    background: #ff0;
 +
    color: #000;
 +
}
 +
 
 +
/**
 +
* Correct font family set oddly in Safari 5 and Chrome.
 +
*/
 +
 
 +
code,
 +
kbd,
 +
pre,
 +
samp {
 +
    font-family: monospace, serif;
 +
    font-size: 1em;
 +
}
 +
 
 +
/**
 +
* Improve readability of pre-formatted text in all browsers.
 +
*/
 +
 
 +
pre {
 +
    white-space: pre-wrap;
 +
}
 +
 
 +
/**
 +
* Set consistent quote types.
 +
*/
 +
 
 +
q {
 +
    quotes: "\201C" "\201D" "\2018" "\2019";
 +
}
 +
 
 +
/**
 +
* Address inconsistent and variable font size in all browsers.
 +
*/
 +
 
 +
small {
 +
    font-size: 80%;
 +
}
 +
 
 +
/**
 +
* Prevent `sub` and `sup` affecting `line-height` in all browsers.
 +
*/
 +
 
 +
sub,
 +
sup {
 +
    font-size: 75%;
 +
    line-height: 0;
 +
    position: relative;
 +
    vertical-align: baseline;
 +
}
 +
 
 +
sup {
 +
    top: -0.5em;
 +
}
 +
 
 +
sub {
 +
    bottom: -0.25em;
 +
}
 +
 
 +
/* ==========================================================================
 +
  Embedded content
 +
  ========================================================================== */
 +
 
 +
/**
 +
* Remove border when inside `a` element in IE 8/9.
 +
*/
 +
 
 +
img {
 +
    border: 0;
 +
}
 +
 
 +
/**
 +
* Correct overflow displayed oddly in IE 9.
 +
*/
 +
 
 +
svg:not(:root) {
 +
    overflow: hidden;
 +
}
 +
 
 +
/* ==========================================================================
 +
  Figures
 +
  ========================================================================== */
 +
 
 +
/**
 +
* Address margin not present in IE 8/9 and Safari 5.
 +
*/
 +
 
 +
figure {
 +
    margin: 0;
 +
}
 +
 
 +
/* ==========================================================================
 +
  Forms
 +
  ========================================================================== */
 +
 
 +
/**
 +
* Define consistent border, margin, and padding.
 +
*/
 +
 
 +
fieldset {
 +
    border: 1px solid #c0c0c0;
 +
    margin: 0 2px;
 +
    padding: 0.35em 0.625em 0.75em;
 +
}
 +
 
 +
/**
 +
* 1. Correct `color` not being inherited in IE 8/9.
 +
* 2. Remove padding so people aren't caught out if they zero out fieldsets.
 +
*/
 +
 
 +
legend {
 +
    border: 0; /* 1 */
 +
    padding: 0; /* 2 */
 +
}
 +
 
 +
/**
 +
* 1. Correct font family not being inherited in all browsers.
 +
* 2. Correct font size not being inherited in all browsers.
 +
* 3. Address margins set differently in Firefox 4+, Safari 5, and Chrome.
 +
*/
 +
 
 +
button,
 +
input,
 +
select,
 +
textarea {
 +
    font-family: inherit; /* 1 */
 +
    font-size: 100%; /* 2 */
 +
    margin: 0; /* 3 */
 +
}
 +
 
 +
/**
 +
* Address Firefox 4+ setting `line-height` on `input` using `!important` in
 +
* the UA stylesheet.
 +
*/
 +
 
 +
button,
 +
input {
 +
    line-height: normal;
 +
}
 +
 
 +
/**
 +
* Address inconsistent `text-transform` inheritance for `button` and `select`.
 +
* All other form control elements do not inherit `text-transform` values.
 +
* Correct `button` style inheritance in Chrome, Safari 5+, and IE 8+.
 +
* Correct `select` style inheritance in Firefox 4+ and Opera.
 +
*/
 +
 
 +
button,
 +
select {
 +
    text-transform: none;
 +
}
 +
 
 +
/**
 +
* 1. Avoid the WebKit bug in Android 4.0.* where (2) destroys native `audio`
 +
  *    and `video` controls.
 +
* 2. Correct inability to style clickable `input` types in iOS.
 +
* 3. Improve usability and consistency of cursor style between image-type
 +
*    `input` and others.
 +
*/
 +
 
 +
button,
 +
html input[type="button"], /* 1 */
 +
input[type="reset"],
 +
input[type="submit"] {
 +
    -webkit-appearance: button; /* 2 */
 +
    cursor: pointer; /* 3 */
 +
}
 +
 
 +
/**
 +
* Re-set default cursor for disabled elements.
 +
*/
 +
 
 +
button[disabled],
 +
html input[disabled] {
 +
    cursor: default;
 +
}
 +
 
 +
/**
 +
* 1. Address box sizing set to `content-box` in IE 8/9.
 +
* 2. Remove excess padding in IE 8/9.
 +
*/
 +
 
 +
input[type="checkbox"],
 +
input[type="radio"] {
 +
    box-sizing: border-box; /* 1 */
 +
    padding: 0; /* 2 */
 +
}
 +
 
 +
/**
 +
* 1. Address `appearance` set to `searchfield` in Safari 5 and Chrome.
 +
* 2. Address `box-sizing` set to `border-box` in Safari 5 and Chrome
 +
*    (include `-moz` to future-proof).
 +
*/
 +
 
 +
input[type="search"] {
 +
    -webkit-appearance: textfield; /* 1 */
 +
    -moz-box-sizing: content-box;
 +
    -webkit-box-sizing: content-box; /* 2 */
 +
    box-sizing: content-box;
 +
}
 +
 
 +
/**
 +
* Remove inner padding and search cancel button in Safari 5 and Chrome
 +
* on OS X.
 +
*/
 +
 
 +
input[type="search"]::-webkit-search-cancel-button,
 +
input[type="search"]::-webkit-search-decoration {
 +
    -webkit-appearance: none;
 +
}
 +
 
 +
/**
 +
* Remove inner padding and border in Firefox 4+.
 +
*/
 +
 
 +
button::-moz-focus-inner,
 +
input::-moz-focus-inner {
 +
    border: 0;
 +
    padding: 0;
 +
}
 +
 
 +
/**
 +
* 1. Remove default vertical scrollbar in IE 8/9.
 +
* 2. Improve readability and alignment in all browsers.
 +
*/
 +
 
 +
textarea {
 +
    overflow: auto; /* 1 */
 +
    vertical-align: top; /* 2 */
 +
}
 +
 
 +
/* ==========================================================================
 +
  Tables
 +
  ========================================================================== */
 +
 
 +
/**
 +
* Remove most spacing between table cells.
 +
*/
 +
 
 +
table {
 +
    border-collapse: collapse;
 +
    border-spacing: 0;
 +
}
 +
 
 +
html, body {
 +
color: #111;
 +
background-color: transparent;
 +
width: 100%;
 +
height: 100%;
 +
margin: 0;
 +
padding: 0;
 +
display:block;
 +
line-height:normal;
 +
 
 +
}
 +
 
 +
h1 {
 +
font-weight:bold;
 +
font-size:52px;
 +
margin:0;
 +
text-transform:uppercase;
 +
font-family: 'Lato', sans-serif;
 +
font-weight:900;
 +
text-align:center;
 +
/*font-family: "Courier New", Courier, "Lucida Sans Typewriter", "Lucida Typewriter", monospace;*/
 +
}
 +
h2 {
 +
font-weight:bold;
 +
font-size:24px;
 +
text-transform:uppercase;
 +
font-family: 'Lato', sans-serif;
 +
font-weight:900;
 +
/*font-family: "Courier New", Courier, "Lucida Sans Typewriter", "Lucida Typewriter", monospace;*/
 +
}
 +
p {
 +
font-family: 'Lato', sans-serif;
 +
/*font-family: "Courier New", Courier, "Lucida Sans Typewriter", "Lucida Typewriter", monospace;*/
 +
}
 +
img {margin:10px;}
 +
 
 +
 
 +
 
 +
.firstHeading { display:none;}
 +
 
 +
#content {border:none !important; line-height:normal !important;}
 +
 
 +
h1, h2, h3, h4 {border:none !important;}
 +
 
 +
#content, #gloabalWrapper {position:static !important;}
 +
 
 +
 
 +
 
 +
/*#menubar, .left-menu, .left-menu a {
 +
color: white !important;
 +
background-color: #555555;
 +
 
 +
}*/
 +
 
 +
#top-section {
 +
border:none !important;
 +
}
 +
#p-logo {display:none;}
 +
 
 +
#top-section {height:0px;}
 +
 
 +
#search-controls {
 +
display:none;
 +
}
 +
#footer-box {
 +
display:none;
 +
}
 +
 
 +
#catlinks {
 +
display:none;
 +
}
 +
 
 +
</style>
 +
<img src="https://static.igem.org/mediawiki/2014/9/9b/Melbourne_Banner.png" alt="Banner" height="225" width="1000">
 +
 
 +
 
 +
 
 +
<table  width="100%">
 +
 
 +
<tr height="10px">
 +
 
 +
 
 +
<td align="center" height="30px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7>
 +
<a href="https://2014.igem.org/Team:Melbourne"style="color:#000000">Home </a> </td>
 +
 
 +
<td align="center" height="30px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7>
 +
<a href="https://2014.igem.org/Team:Melbourne/Team"style="color:#000000">
 +
Team </a> </td>
 +
 
 +
<td align="center"  height="30px"  onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7>
 +
<a target="_blank" href="https://igem.org/Team.cgi?year=2014&team_name=Melbourne"style="color:#000000">Official Team Profile </a></td>
 +
 
 +
<td align="center"  height="30px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7>
 +
<a href="https://2014.igem.org/Team:Melbourne/Project"style="color:#000000">
 +
Project</a></td>
 +
 
 +
<td align="center"  height="30px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7>
 +
<a href="https://2014.igem.org/Team:Melbourne/Parts"style="color:#000000">
 +
Parts</a></td>
 +
 
 +
<td align="center" height="30px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7>
 +
<a href="https://2014.igem.org/Team:Melbourne/Modeling"style="color:#000000">
 +
Modeling</a></td>
 +
 
 +
<td align="center" height="30px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7>
 +
<a href="https://2014.igem.org/Team:Melbourne/Notebook"style="color:#000000">
 +
Notebook</a></td>
 +
 
 +
<td align="center"  height="30px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7>
 +
<a href="https://2014.igem.org/Team:Melbourne/Protocol"style="color:#000000">
 +
Protocol</a></td>
 +
<td align="center"  height="30px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7>
 +
<a href="https://2014.igem.org/Team:Melbourne/Safety"style=" color:#000000">
 +
Safety </a></td>
 +
 
 +
<td align="center"  height="30px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7>
 +
<a href="https://2014.igem.org/Team:Melbourne/Attributions"style="color:#000000">
 +
Attributions </a></td>
 +
 
 +
 
 +
<td align="center"  height="30px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7>
 +
<a href="https://2014.igem.org/Team:Melbourne/Public_Outreach"style="color:#000000">
 +
Public Outreach </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>
</tr>
-
<tr>
+
</table>
-
<td width="45%"  valign="top">  
+
 
 +
 
 +
<h1 >Parts</h1>
 +
 
 +
<h3>What information do I need to start putting my parts on the Registry? </h3>
 +
 
<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 99: Line 544:
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>
-
 
Line 107: Line 551:
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 > </td>
 
-
<td width="45%" valign="top">
 
<p>
<p>
Line 133: Line 573:
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>
 
 +
<h3> Parts Table</h3>
-
<tr> <td colspan="3"  height="15px"> </td></tr>
+
Any parts your team has created will appear in this table below
-
<tr><td colspan="3" > <h3> Parts Table</h3></td></tr>
 
-
 
+
<!-- END EDIT HERE HERE -->
-
<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 Melbourne</groupparts>
 

Latest revision as of 10:34, 17 October 2014

Banner

Home Team Official Team Profile Project Parts Modeling Notebook Protocol Safety Attributions Public Outreach

Parts

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

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