Team:UT-Dallas/Parts

From 2014.igem.org

(Difference between revisions)
Line 1: Line 1:
 +
{{CSS/Main}}
 +
 +
<html>
<html>
-
<head>
 
<style type="text/css">
<style type="text/css">
 +
#groupparts {text-align: center; margin-left: auto; margin-right: auto;}
 +
</style>
 +
<!--main content -->
 +
<table width="70%" align="center">
-
#contentSub, #footer-box, #catlinks, #search-controls, #p-logo, .printfooter, .visualClear {display: none;} /*-- hides default wiki settings --*/
+
-
.firstHeading {
 
-
width: 975px;
 
-
margin: 0px auto;
 
-
padding-top: 100px;
 
-
margin-bottom: 20px;
 
-
font-family: Georgia, Times, "Times New Roman", serif;
 
-
}
 
-
h1, h2, h3, h4, h5 { font-family: Georgia, Times, "Times New Roman", serif;}
+
<!--welcome box -->
 +
<tr>
 +
<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:UT-Dallas/Parts&action=edit"style="color:#FFFFFF"> Click here  to edit this page!</a> </p>
 +
</td>
 +
</tr>
-
#top-section { /*-- styling for default menu bar (edit, page, history, etc.) --*/
+
<tr> <td colspan="3"  height="5px"> </td></tr>
-
background-color: #383838;
+
<!-- end welcome box -->
-
border: 0 none;
+
<tr>
-
height: 14px;
+
-
z-index: 100;
+
-
top: 0;
+
-
position: fixed;
+
-
width: 975px;
+
-
left: 50%;
+
-
margin-left: -487px;
+
-
}
+
-
#top-section-bar { /*-- styling full width bar which hides behind default menu bar (edit, page, history, etc.) --*/
+
<!--navigation menu -->
-
background-color: #383838;
+
<td align="center" colspan="3">
-
height: 14px;
+
-
display: block;
+
-
z-index: 10;
+
-
position: fixed;
+
-
width: 100%;
+
-
top: 0;
+
-
}
+
-
#menubar a:link, #menubar a:active, #menubar a:visited, #menubar a:hover, #menubar:hover { /*-- styling for default menu bar links (edit, page, history, etc.) --*/
+
<table  width="100%">
-
color: #727272;
+
<tr heigth="15px"></tr>
-
text-decoration: none;
+
<tr heigth="75px">
-
background-color: transparent;
+
-
}
+
-
body {
 
-
background-color: #fff;
 
-
}
 
-
#globalWrapper, #content { /*-- changes default wiki settings --*/
+
<td style="border:1px solid black;" align="center" height ="45px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7> 
-
width: 100%;
+
<a href="https://2014.igem.org/Team:UT-Dallas"style="color:#000000">Home </a> </td>
-
height: 100%;
+
-
border: 0px;
+
-
background-color: transparent;
+
-
margin: 0px;
+
-
padding: 0px;
+
-
}
+
-
html, body, .wrapper { /*-- changes default wiki settings --*/
+
<td style="border:1px solid black;" align="center" height ="45px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7>
-
width: 100%;
+
<a href="https://2014.igem.org/Team:UT-Dallas/Team"style="color:#000000"> Team </a> </td>
-
height: 100%;
+
-
background-color: transparent;
+
-
}
+
-
#contentcontainer { /*-- creates container for all content on page --*/
+
<td style="border:1px solid black;" align="center"  height ="45px"  onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7>
-
font-family: Arial, Helvetica, sans-serif;  
+
<a href="https://igem.org/Team.cgi?year=2014&team_name=UT-Dallas"style="color:#000000"> Official Team Profile </a></td>
-
font-weight: normal;
+
-
font-size: 14px;
+
-
color: #414141;
+
-
width: 960px;
+
-
margin-left: auto;
+
-
margin-right: auto;
+
-
background-color: #transparent;
+
-
margin-top: 0px;
+
-
}
+
-
.sidemenu, .sidemenu li {
+
<td style="border:1px solid black" align="center"  height ="45px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7> 
-
list-style-type: none;
+
<a href="https://2014.igem.org/Team:UT-Dallas/Project"style="color:#000000"> Project</a></td>
-
list-style-image: none;
+
-
font-family: verdana;
+
-
text-decoration: none;
+
-
color:#000;
+
-
font-size: 14px;
+
-
}
+
-
.sidemenu li {display: block;}
+
<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:UT-Dallas/Parts"style="color:#000000"> Parts</a></td>
-
.sidemenu a {
+
<td style="border:1px solid black;" align="center" height ="45px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7>
-
text-decoration:none;  
+
<a href="https://2014.igem.org/Team:UT-Dallas/Modeling"style="color:#000000"> Modeling</a></td>
-
color: #000;
+
-
display: block;
+
-
width: 180px;
+
-
height: 100%;
+
-
padding: 3px 5px;
+
-
transition: .25s ease-in-out;
+
-
-moz-transition: .25s ease-in-out;
+
-
-webkit-transition: .25s ease-in-out;
+
-
}
+
-
.sidemenu a.greyout { color: #909090; }
+
<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:UT-Dallas/Notebook"style="color:#000000"> Notebook</a></td>
-
.sidemenu a:hover {
+
<td style="border:1px solid black;" align="center"  height ="45px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7>
-
color:#666;
+
<a href="https://2014.igem.org/Team:UT-Dallas/Safety"style=" color:#000000"> Safety </a></td>
-
background-color: #d9f5aa;
+
-
}
+
-
.sub-sidemenu {font-size: 10px; margin-bottom: 20px; color: #666; display: none;}
+
<td style="border:1px solid black;" align="center"  height ="45px" onMouseOver="this.bgColor='#d3d3d3'" onMouseOut="this.bgColor='#e7e7e7'" bgColor=#e7e7e7>
-
.sub-sidemenu a {color: #666;}
+
<a href="https://2014.igem.org/Team:UT-Dallas/Attributions"style="color:#000000"> Attributions </a></td>
-
div.underconst
 
-
{
 
-
padding:10px;
 
-
border-radius:5px;
 
-
background-color:pink;
 
-
text-align:center;
 
-
}
 
-
a.anchor{display: block; position: relative; top: -80px; visibility: hidden;}
+
<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>
-
.contentpara {margin-bottom: 30px;}
+
<!--end navigation menu -->
 +
</tr>
-
span.email{font-family: monospace; font-weight: normal;}
 
-
fieldset {border: 1px solid #337f53;}
+
</tr>
 +
-
.greyout {color: #A0A0A0;}
 
-
.highlightme {background-color: #FFFF00;}
 
-
#alertContainer { margin-bottom: 10px; width: 936px;}
 
-
#annContainer {margin-left: 8px;}
 
-
#newsContainer {border: 1px solid #ccc;}
 
-
.newsTitle {
 
-
display: block;
 
-
color: #414141;
 
-
font-size: 25px; 
 
-
        font-family: Georgia, Times, "Times New Roman", serif;
 
-
padding: 10px 15px 5px 10px;
 
-
border-bottom: 1px solid #ccc;
 
-
margin-bottom: 0px;
 
-
}
 
-
.newsItem {
+
</td>
-
border-bottom: 1px solid #ccc;
+
-
display: block;
+
-
padding: 5px 15px 0px 10px;
+
-
margin-bottom: 0px;
+
-
}
+
-
.newsItem h3 {
+
<tr> <td colspan="3"  height="15px"> </td></tr>
-
width: auto;
+
<tr><td bgColor="#e7e7e7" colspan="3" height="1px"> </tr>
-
display: inline;
+
<tr> <td colspan="3"  height="5px"> </td></tr>
-
font-size: 14px;
+
-
font-family: Arial, Helvetica, sans-serif;
+
-
padding: 0px;
+
-
margin: 0px;
+
-
}
+
-
.newsItem img {
 
-
float: right;
 
-
clear: right;
 
-
width: 80px;
 
-
padding-left: 15px;
 
-
display: inline-block;
 
-
}
 
-
.newsItem .newsDate {
+
<!--Parts Submitted to the Registry  -->
-
font-style: italic;
+
<tr><td > <h3> Parts Submitted to the Registry </h3></td>
-
font-size: 14px;
+
<td ></td >
-
display: inline-block;
+
<td > <h3>What information do I need to start putting my parts on the Registry? </h3></td>
-
color: #999;
+
</tr>
-
float: right;
+
<tr>
-
padding: 0px 0px 10px 15px;
+
<td width="45%"  valign="top">
-
}
+
<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. 
-
.newsItem p, .newsItem ul, .newsItem li {
+
<p>
-
padding: 0px;
+
<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.  
-
margin-left: 20px;
+
</p>
-
font-size: 12px;
+
-
line-height: 1.2;
+
-
}
+
-
.newsItem p {margin-top: 10px;}
+
<p>
 +
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>
-
.annItem {
 
-
border: 2px solid #414141;
 
-
display: block;
 
-
padding: 0px 15px 10px 10px;
 
-
margin-bottom: 18px;
 
-
position: relative;
 
-
height: 160px;
 
-
vertical-align: middle;
 
-
}
 
-
.annItem .annCentered {
 
-
display: table-cell;
 
-
vertical-align: middle;
 
-
height: 160px;
 
-
}
 
-
.annCentered h3 {
+
<h3>When should you put parts into the Registry?</h3>
-
padding: 0px;
+
-
display: block;
+
-
margin-left: auto;
+
-
margin-right: auto;
+
-
text-align: center;
+
-
}
+
-
.annItem ul, .annItem li {padding: 0px; margin: 0px;}
+
<p>
-
.annItem li {list-style: none; margin: 5px}
+
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>
 +
</td>
 +
<td > </td>
 +
<td width="45%" valign="top">
 +
<p>
 +
The information needed to initially create a part on the Registry is:
 +
</p>
 +
<ol>
-
</style>
+
<li>Part Name</li>
-
</style>
+
<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>
 +
</tr>
 +
 +
<tr> <td colspan="3"  height="15px"> </td></tr>
 +
 +
<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 UT-Dallas</groupparts>

Revision as of 20:33, 24 September 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 UT-Dallas</groupparts>

Retrieved from "http://2014.igem.org/Team:UT-Dallas/Parts"