Difference between revisions of "Team:Toronto/Parts"

 
(23 intermediate revisions by the same user not shown)
Line 6: Line 6:
  
 
<!-- repo for this wiki: https://github.com/igemuoftATG/wiki2016 -->
 
<!-- repo for this wiki: https://github.com/igemuoftATG/wiki2016 -->
−
<!-- file built: Mon Oct 17 2016 23:59:11 GMT-0400 (EDT) -->
 
−
 
 
</html>
 
</html>
 
{{Toronto/head}}
 
{{Toronto/head}}
Line 15: Line 13:
 
<ul>
 
<ul>
 
<li><a href="https://2016.igem.org/Team:Toronto"><span>home</span></a></li>
 
<li><a href="https://2016.igem.org/Team:Toronto"><span>home</span></a></li>
 +
</li>
 +
<li><a href="https://2016.igem.org/Team:Toronto/Achievements"><span>achievements</span></a></li>
 
</li>
 
</li>
 
<li><a href="#"><span>team</span></a>
 
<li><a href="#"><span>team</span></a>
Line 64: Line 64:
 
</li>
 
</li>
 
<li><a href="https://2016.igem.org/Team:Toronto/Integrated_Practices"><span>integrated_practices</span></a></li>
 
<li><a href="https://2016.igem.org/Team:Toronto/Integrated_Practices"><span>integrated_practices</span></a></li>
−
</li>
 
−
<li><a href="https://2016.igem.org/Team:Toronto/Engagement"><span>engagement</span></a></li>
 
 
</li>
 
</li>
 
</ul>
 
</ul>
 
<li><a href="#"><span>awards</span></a>
 
<li><a href="#"><span>awards</span></a>
 
<ul>
 
<ul>
−
<li><a href="https://2016.igem.org/Team:Toronto/Entrepreneurship"><span>entrepreneurship</span></a></li>
 
−
</li>
 
−
<li><a href="https://2016.igem.org/Team:Toronto/Hardware"><span>hardware</span></a></li>
 
−
</li>
 
 
<li><a href="https://2016.igem.org/Team:Toronto/Software"><span>software</span></a></li>
 
<li><a href="https://2016.igem.org/Team:Toronto/Software"><span>software</span></a></li>
−
</li>
 
−
<li><a href="https://2016.igem.org/Team:Toronto/Measurement"><span>measurement</span></a></li>
 
 
</li>
 
</li>
 
<li><a href="https://2016.igem.org/Team:Toronto/Model"><span>model</span></a></li>
 
<li><a href="https://2016.igem.org/Team:Toronto/Model"><span>model</span></a></li>
Line 84: Line 76:
 
</div>
 
</div>
 
<div class="content">
 
<div class="content">
−
<div class="content" id="content-main"><div class="row"><div class="col col-lg-8 col-md-12"><div class="content-main"><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>
+
<div class="content" id="content-main"><div class="row"><div class="col col-lg-8 col-md-12"><div class="content-main"><h1 id="design">Design</h1>
−
<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>
+
<p><img src="https://static.igem.org/mediawiki/parts/2/29/Trial2016Toronto.jpeg" alt="alt text"></p>
−
<h5 id="note">Note</h5>
+
<center><em>Figure 1: Designed Circuit</em></center>
−
<p>Note that parts must be documented on the <a href="http://parts.igem.org/Main_Page">Registry</a>. This page serves to <em>showcase</em> 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>
+
 
−
<h5 id="adding-parts-to-the-registry">Adding parts to the registry</h5>
+
<h3 id="gols">GolS</h3>
−
<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 wild type gene for the salmonella GolS protein. GolS functions by binding to an operator (pGolb)to repress transcription by bending the DNA. In the presence of gold ions, the repressor undergoes a conformational change and unbends the DNA. This allows for transcription of the operon genes. In salmonella, GolS is used as a response protein to regulate gold resistance protein expression.</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&#39;t need to send us the DNA sample before you create an entry for a part on the Registry. (However, you <strong>do</strong> need to send us the DNA sample before the Jamboree. If you don&#39;t send us a DNA sample of a part, that part will not be eligible for awards and medal criteria.)</p>
+
<h3 id="gols-p118a">GolS P118A</h3>
−
<h5 id="what-information-do-i-need-to-start-putting-my-parts-on-the-registry-">What information do I need to start putting my parts on the Registry?</h5>
+
<p>The GolS repressor protein with a modified binding site to increase selectivity for gold ions and decrease interaction between copper ions.  This modification ensures that products will only be responsive to one element. </p>
−
<p>The information needed to initially create a part on the Registry is:</p>
+
<h3 id="mcherry">mCherry</h3>
−
<ul>
+
<p>A gene for a cherry coloured protein placed adjacent to pGolb to serve as a reporter for gold presence. </p>
−
<li>Part Name</li>
+
<h3 id="teto-promoter">TetO Promoter</h3>
−
<li>Part type</li>
+
<p>A strong constitutive promoter to express the GolS protein, ensuring saturation of all pGolb sites with GolS so there’s no leak of reporter. </p>
−
<li>Creator</li>
+
<h3 id="lacz">LacZ</h3>
−
<li>Sequence</li>
+
<p>Alternative reporter protein used next to pGolb to indicate gold ion presence.</p>
−
<li>Short Description (60 characters on what the DNA does)</li>
+
<h3 id="parts-submitted">Parts Submitted</h3>
−
<li>Long Description (Longer description of what the DNA does)</li>
+
<!-- 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.
−
<li>Design considerations</li>
+
 
−
</ul>
+
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>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.</p>
+
 
−
<h5 id="inspiration">Inspiration</h5>
+
Note
−
<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>
+
Note that parts must be documented on the [Registry](http://parts.igem.org/Main_Page). 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.
−
<ul>
+
 
−
<li><a href="https://2014.igem.org/Team:MIT/Parts">2014 MIT</a></li>
+
Adding parts to the registry
−
<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>
+
You can add parts to the Registry at our [Add a Part to the Registry](http://parts.igem.org/Add_a_Part_to_the_Registry) link.
−
</ul>
+
 
−
<h5 id="part-table">Part Table</h5>
+
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 over the summer. 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](http://parts.igem.org/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:
 +
 
 +
*  [2014 MIT](https://2014.igem.org/Team:MIT/Parts)
 +
*  [2014 Heidelberg](https://2014.igem.org/Team:Heidelberg/Parts)
 +
*  [2014 Tokyo Tech](https://2014.igem.org/Team:Tokyo_Tech/Parts)
 +
-->
 +
<p>Part Table</p>
 
</div></div><div id="tableofcontents" class="tableofcontents affix sidebar col-lg-4 hidden-xs hidden-sm hidden-md visible-lg-3"><ul class="nav">
 
</div></div><div id="tableofcontents" class="tableofcontents affix sidebar col-lg-4 hidden-xs hidden-sm hidden-md visible-lg-3"><ul class="nav">
−
<li><a href="#adding-parts-to-the-registry">Adding parts to the registry</a></li>
+
<li><a href="#gols">GolS</a></li>
−
<li><a href="#what-information-do-i-need-to-start-putting-my-parts-on-the-registry-">What information do I need to start putting my parts on the Registry?</a></li>
+
<li><a href="#gols-p118a">GolS P118A</a></li>
−
<li><a href="#inspiration">Inspiration</a></li>
+
<li><a href="#mcherry">mCherry</a></li>
−
<li><a href="#part-table">Part Table</a></li>
+
<li><a href="#teto-promoter">TetO Promoter</a></li>
 +
<li><a href="#lacz">LacZ</a></li>
 +
<li><a href="#parts-submitted">Parts Submitted</a></li>
 
</ul>
 
</ul>
 
</div></div></div>
 
</div></div></div>
 +
</html>
 +
<groupparts>iGEM016 Toronto</groupparts>
 +
<html>
 +
 
</div>
 
</div>
 
</html>
 
</html>
 +
 
{{Toronto/footer}}
 
{{Toronto/footer}}

Latest revision as of 15:10, 19 October 2016

Design

alt text

Figure 1: Designed Circuit

GolS

The wild type gene for the salmonella GolS protein. GolS functions by binding to an operator (pGolb)to repress transcription by bending the DNA. In the presence of gold ions, the repressor undergoes a conformational change and unbends the DNA. This allows for transcription of the operon genes. In salmonella, GolS is used as a response protein to regulate gold resistance protein expression.

GolS P118A

The GolS repressor protein with a modified binding site to increase selectivity for gold ions and decrease interaction between copper ions. This modification ensures that products will only be responsive to one element.

mCherry

A gene for a cherry coloured protein placed adjacent to pGolb to serve as a reporter for gold presence.

TetO Promoter

A strong constitutive promoter to express the GolS protein, ensuring saturation of all pGolb sites with GolS so there’s no leak of reporter.

LacZ

Alternative reporter protein used next to pGolb to indicate gold ion presence.

Parts Submitted

Part Table

<groupparts>iGEM016 Toronto</groupparts>