Team:Colombia/Parts

From 2014.igem.org

(Difference between revisions)
(Prototype team page)
 
(22 intermediate revisions not shown)
Line 1: Line 1:
-
{{CSS/Main}}
+
{{Http://2014.igem.org/Team:Colombia}}
-
 
+
<html>
<html>
-
<style type="text/css">
+
<div class="span11" style="text-align: justify;">
-
#groupparts {text-align: center; margin-left: auto; margin-right: auto;}
+
-
</style>
+
-
<!--main content -->
+
-
<table width="70%" align="center">
+
 +
<br><br>
 +
<center><b><h1  class="curs1">Parts</h1></b></center>
-
<!--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>
<br>
-
<p style="color:#E7E7E7"> <a href="https://2014.igem.org/wiki/index.php?title=Team:Colombia/Parts&action=edit"style="color:#FFFFFF"> Click here  to edit this page!</a> </p>
 
-
</td>
 
-
</tr>
 
-
<tr> <td colspan="3"  height="5px"> </td></tr>
+
<font size="4" >In the following table you can find the parts we built (all of them are RFC10 compatible). You can check each one in our <a href="http://parts.igem.org/cgi/partsdb/pgroup.cgi?pgroup=iGEM2014&group=Colombia" target="_blank"> offical part's submission page</a>, where you also can find their documentation and characterization. </font><br><br>
-
<!-- end welcome box -->
+
</html>
-
<tr>
+
[[File:BioPArtsColombia.jpg|center|600px]]
-
 
+
<html>
-
<!--navigation menu -->
+
<br><br>
-
<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:Colombia"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:Colombia/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=Colombia"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:Colombia/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:Colombia/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:Colombia/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:Colombia/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:Colombia/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:Colombia/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>
+
-
 
+
-
 
+
-
<!--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 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.
+
We constructed 7 new, RFC10-compatible parts, two of which were not submitted to the registry because we could not transfer them to the appropriate plasmid backbones on time. Among the parts we built are two reporter genes under the control of <i>ptet</i>. One of these was used to build two different versions of the output circuit: one version with <i>psid</i>, thus completing the feedback loop, and another stand-alone version without the inducible promoter. We also built a circuit capable of producing phosphorylated LuxO when induced by arabinose to test the signal processing and output circuits. Additionally, we built our own Quad-Part tetracycline Inverter device, because we found the one in our distribution to be faulted. We also built a <i>pqrr4</i>-containing biobrick; this part, however, did not appear to function as expected. Finally, since we cannot work with actual <i>V. cholerae</i> due to obvious biosecurity concerns, we need a way of testing the circuits we build without having to deal with the pathogen. For this reason, <i>cqsA</i> was cloned in <i>E. coli</i> (BBa_K581011) to use as a positive control for the whole system.
-
 
+
-
<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 likely to find parts on the Registry than on your team wiki.  
+
</p>
</p>
-
 
+
<br><br>
-
<p>
+
<br><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.
+
<br><br>
-
</p>
+
-
 
+
-
 
+
-
 
+
-
<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>
+
-
</td>
+
-
 
+
-
<td > </td>
+
-
<td width="45%" valign="top">
+
-
 
+
-
<p>
+
-
The information needed to initially create a part on the Registry is:
+
-
</p>
+
-
<ol>
+
-
 
+
-
<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>
+
-
</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 Colombia</groupparts>
 

Latest revision as of 00:44, 18 October 2014

Wheeltz - CSS3 Navigational Wheel Menu

  • Home
  • iGEM
  • Facebook
  • Twitter



Parts


In the following table you can find the parts we built (all of them are RFC10 compatible). You can check each one in our offical part's submission page, where you also can find their documentation and characterization.

BioPArtsColombia.jpg



We constructed 7 new, RFC10-compatible parts, two of which were not submitted to the registry because we could not transfer them to the appropriate plasmid backbones on time. Among the parts we built are two reporter genes under the control of ptet. One of these was used to build two different versions of the output circuit: one version with psid, thus completing the feedback loop, and another stand-alone version without the inducible promoter. We also built a circuit capable of producing phosphorylated LuxO when induced by arabinose to test the signal processing and output circuits. Additionally, we built our own Quad-Part tetracycline Inverter device, because we found the one in our distribution to be faulted. We also built a pqrr4-containing biobrick; this part, however, did not appear to function as expected. Finally, since we cannot work with actual V. cholerae due to obvious biosecurity concerns, we need a way of testing the circuits we build without having to deal with the pathogen. For this reason, cqsA was cloned in E. coli (BBa_K581011) to use as a positive control for the whole system.