Team:UNC-Chapel Hill/Parts
From 2014.igem.org
Megaboy837 (Talk | contribs) |
Megaboy837 (Talk | contribs) |
||
(14 intermediate revisions not shown) | |||
Line 1: | Line 1: | ||
{{CSS/Main}} | {{CSS/Main}} | ||
+ | {{:Team:UNC-Chapel_Hill/practicemenu}} | ||
<html> | <html> | ||
- | < | + | <head> |
- | + | <link href="https://2014.igem.org/Team:UNC-Chapel_Hill/StyleSheets/HomePage?action=raw&ctype=text/css" rel="stylesheet"> | |
- | </ | + | </head> |
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
Line 55: | Line 13: | ||
<!-- first block of three columns --> | <!-- first block of three columns --> | ||
- | <table width=" | + | <center> |
- | <tr><td bgColor="#56A0D3"></td> <td colspan="3" width="975px" bgColor="#56A0D3" align="center"> < | + | <table width="975" cellspacing="0" height="10px"> |
+ | <tr><td bgColor="#56A0D3"></td> <td colspan="3" width="975px" bgColor="#56A0D3" align="center"> <p style="color:white;font-size:20px">PROJECT: PARTS SUBMITTED </p></td> <td bgColor="#56A0D3"></td> </tr> | ||
+ | </table> | ||
+ | </center> | ||
+ | <table width="100%" cellspacing="0" height="230px"> | ||
<tr> | <tr> | ||
<td bgColor="#FFFFFF"></td> | <td bgColor="#FFFFFF"></td> | ||
Line 63: | Line 25: | ||
<td width="435px" height="400px" bgColor="#FFFFFF" > | <td width="435px" height="400px" bgColor="#FFFFFF" > | ||
<h3>Parts Submitted to the Registry</h3> | <h3>Parts Submitted to the Registry</h3> | ||
- | <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. | + | <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. <br> |
+ | |||
- | |||
<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. | <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. | ||
- | < | + | <br> |
+ | |||
- | |||
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 76: | Line 38: | ||
<td width="50px"></td> | <td width="50px"></td> | ||
<td width="435px" bgColor="#FFFFFF"> | <td width="435px" bgColor="#FFFFFF"> | ||
- | < | + | <h3>Parts</h3> |
- | <ul> | + | <ul style="font: 18px/1.6 'Segoe UI', Calibri, Helvetica, sans-serif; |
+ | margin: 4px 0 12px 0; | ||
+ | padding-left: 20px; | ||
+ | text-indent: 0; | ||
+ | color: #000000; | ||
+ | text-align:justify; | ||
+ | text-justify:inter-word;"> | ||
<li>Part 1 - Lorem ipsum ad his scripta blandit partiendo, eum fastidii accumsan euripidis in, eum liber hendrerit an.</li> | <li>Part 1 - Lorem ipsum ad his scripta blandit partiendo, eum fastidii accumsan euripidis in, eum liber hendrerit an.</li> | ||
<li>Part 2 - Lorem ipsum ad his scripta blandit partiendo, eum fastidii accumsan euripidis in, eum liber hendrerit an.</li> | <li>Part 2 - Lorem ipsum ad his scripta blandit partiendo, eum fastidii accumsan euripidis in, eum liber hendrerit an.</li> | ||
<li>Part 3 - Lorem ipsum ad his scripta blandit partiendo, eum fastidii accumsan euripidis in, eum liber hendrerit an.</li> | <li>Part 3 - Lorem ipsum ad his scripta blandit partiendo, eum fastidii accumsan euripidis in, eum liber hendrerit an.</li> | ||
+ | <h3>When should you put parts into the Registry?</h3> | ||
+ | <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. | ||
+ | </p> | ||
</ul> | </ul> | ||
</td> | </td> | ||
Line 88: | Line 60: | ||
</tr> | </tr> | ||
</table> | </table> | ||
+ | |||
+ | <center> | ||
+ | <table width="975" cellspacing="0" height="115px"> | ||
+ | <tr> | ||
+ | <td bgColor="#FFFFFF"></td> | ||
+ | |||
+ | <td width="100%" height="4px" bgColor="#FFFFFF" > | ||
+ | |||
+ | <p></p> | ||
+ | |||
+ | <img src="https://static.igem.org/mediawiki/2014/thumb/b/b8/UNC_Chapel_Hill_Old_Well_Masthead.jpg/800px-UNC_Chapel_Hill_Old_Well_Masthead.jpg" width="100%"> | ||
+ | |||
+ | </td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | </center> | ||
+ | |||
<!-- end of first block --> | <!-- end of first block --> | ||
<!-- navigation for project page--> | <!-- navigation for project page--> | ||
- | <table width=" | + | <table width="1000" align="center" > |
<tr> | <tr> | ||
Line 97: | Line 86: | ||
<td align="center" width="10%" height ="35px" | <td align="center" width="10%" height ="35px" | ||
onMouseOver="this.bgColor='#A1DBB2'" onMouseOut="this.bgColor='#56A0D3'" bgColor=#56A0D3> | onMouseOver="this.bgColor='#A1DBB2'" onMouseOut="this.bgColor='#56A0D3'" bgColor=#56A0D3> | ||
- | <a href="#Parts" style="text-decoration:none;color:# | + | <a href="#Parts" style="text-decoration:none;color:#ffffff">Parts </a> </td> |
</td> | </td> | ||
<td align="center" width="10%" height ="35px" | <td align="center" width="10%" height ="35px" | ||
onMouseOver="this.bgColor='#A1DBB2'" onMouseOut="this.bgColor='#56A0D3'" bgColor=#56A0D3> | onMouseOver="this.bgColor='#A1DBB2'" onMouseOut="this.bgColor='#56A0D3'" bgColor=#56A0D3> | ||
- | <a href="#Part1" style="text-decoration:none;color:# | + | <a href="#Part1" style="text-decoration:none;color:#ffffff">Part 1 </a> </td> |
</td> | </td> | ||
<td align="center" width="10%" height ="35px" | <td align="center" width="10%" height ="35px" | ||
onMouseOver="this.bgColor='#A1DBB2'" onMouseOut="this.bgColor='#56A0D3'" bgColor=#56A0D3> | onMouseOver="this.bgColor='#A1DBB2'" onMouseOut="this.bgColor='#56A0D3'" bgColor=#56A0D3> | ||
- | <a href="#Part2" style="text-decoration:none;color:# | + | <a href="#Part2" style="text-decoration:none;color:#ffffff">Part 2 </a> </td> |
</td> | </td> | ||
<td align="center" width="10%" height ="35px" | <td align="center" width="10%" height ="35px" | ||
onMouseOver="this.bgColor='#A1DBB2'" onMouseOut="this.bgColor='#56A0D3'" bgColor=#56A0D3> | onMouseOver="this.bgColor='#A1DBB2'" onMouseOut="this.bgColor='#56A0D3'" bgColor=#56A0D3> | ||
- | <a href="#Part3" style="text-decoration:none;color:# | + | <a href="#Part3" style="text-decoration:none;color:#ffffff">Part 3 </a> </td> |
</td> | </td> | ||
Line 118: | Line 107: | ||
<td align="center" width="10%" height ="35px" | <td align="center" width="10%" height ="35px" | ||
onMouseOver="this.bgColor='#A1DBB2'" onMouseOut="this.bgColor='#56A0D3'" bgColor=#56A0D3> | onMouseOver="this.bgColor='#A1DBB2'" onMouseOut="this.bgColor='#56A0D3'" bgColor=#56A0D3> | ||
- | <a href="#references" style="text-decoration:none;color:# | + | <a href="#references" style="text-decoration:none;color:#ffffff">References </a> </td> |
</td> | </td> | ||
Line 135: | Line 124: | ||
<td width="450px" bgColor="#FFFFFF"> | <td width="450px" bgColor="#FFFFFF"> | ||
- | < | + | <h3 id="Parts"> Parts</h3> |
- | <p> | + | <p> |
+ | The information needed to initially create a part on the Registry is: | ||
+ | </p> | ||
+ | <ol style="font: 18px/1.6 'Segoe UI', Calibri, Helvetica, sans-serif; | ||
+ | margin: 4px 0 12px 0; | ||
+ | padding-left: 20px; | ||
+ | text-indent: 0; | ||
+ | color: #000000; | ||
+ | text-align:justify; | ||
+ | text-justify:inter-word;"> | ||
+ | |||
+ | <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> | ||
+ | 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> | ||
+ | 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> | ||
</td> | </td> | ||
Line 149: | Line 164: | ||
</table> | </table> | ||
<!-- end of first block --> | <!-- end of first block --> | ||
+ | |||
+ | <footer> | ||
+ | <a href="#" class="go-top">Top</a> | ||
+ | |||
+ | </footer> | ||
</html> | </html> | ||
+ | |||
+ | <center><groupparts>iGEM013 UNC-Chapel_Hill</groupparts></center> |
Latest revision as of 02:35, 5 August 2014
PROJECT: PARTS SUBMITTED |
Parts Submitted to the RegistryAn 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. |
Parts
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. |
Parts | Part 1 | Part 2 | Part 3 | References |
PartsThe information needed to initially create a part on the Registry is:
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. |
You can place an image here about your project |