Team:London BioHackspace/Parts

From 2014.igem.org

(Difference between revisions)
(Prototype team page)
Line 1: Line 1:
{{CSS/Main}}
{{CSS/Main}}
-
 
+
{{Template:Team:London_BioHackspace/navbar}}
<html>
<html>
-
<style type="text/css">
+
<h1>Parts</h1>
-
#groupparts {text-align: center; margin-left: auto; margin-right: auto;}
+
-
</style>
+
-
<!--main content -->
+
-
<table width="70%" align="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>
+
-
<p style="color:#E7E7E7"> <a href="https://2014.igem.org/wiki/index.php?title=Team:London_BioHackspace/Parts&action=edit"style="color:#FFFFFF"> Click here  to edit this page!</a> </p>
+
-
</td>
+
-
</tr>
+
-
 
+
-
<tr> <td colspan="3"  height="5px"> </td></tr>
+
-
<!-- end welcome box -->
+
-
<tr>
+
-
 
+
-
<!--navigation menu -->
+
-
<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:London_BioHackspace"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:London_BioHackspace/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=London_BioHackspace"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:London_BioHackspace/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:London_BioHackspace/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:London_BioHackspace/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:London_BioHackspace/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:London_BioHackspace/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:London_BioHackspace/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>
+
-
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>
+
-
<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>
+
-
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>
+
-
 
+
-
 
+
-
<h3>When should you put parts into the Registry?</h3>
+
<h2>Introduction</h2>
-
<p>
+
<p>The majority of parts in the iGEM registry are designed to work in <em>E. coli</em>, however our project is centred around genetic modification of <em>G. hansenii</em>. In particular, the biobricks to produce the light sensitive signal transduction pathway based around Cph8(see <a href="https://2014.igem.org/Team:London_BioHackspace/Project_Background">Project Background</a>) do not include a gene for the expression of OmpR because it is found natively in <em>E. coli</em> and is therefore not required for functional expression when working in <em>E. coli</em>.</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>
+
<h2>Aims</h2>
-
<td width="45%" valign="top">
+
-
<p>
+
<ul><li><p>Produce a biobrick containing <em>ompR</em> and sequence it to provide a reliable part for future use in expression of the the Cph8 light sensitive signal transduction pathway in non <em>E. coli</em> chassis.</p></li><li><p>Provide clarifying notes in the registry on parts which have confusingly used the term "ompR" or "OmpR" to label the ompC promoter (ompCp) sequence. Or in some cases have labelled the sequence of ompR as "envZ".</p></li><li><p>Produce a composite biobrick for use in a broad host-range vector such as <a href="https://2014.igem.org/Team:Imperial/Gluconacetobacter">pSEVA321, pSEVA331, pSEVA351</a> which will show whether a a given non-<em>E. coli</em> chassis can functionally express the Cph8 light sensitive signal transduction pathway.</p></li><li><p>Produce a composite biobrick to control the production of extracellular cellulose in <em>dgc1</em> knockout mutants of <em>G. hansenii</em>.</p></li></ul>
-
The information needed to initially create a part on the Registry is:
+
-
</p>
+
-
<ol>
+
-
<li>Part Name</li>
+
<h2>Parts</h2>
-
<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>
+
<p>**[BBa<em>K1337000](parts.igem.org/Part:BBa</em>K1337000)**&lt;/br&gt;
-
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.  
+
<em>ompR</em> from <em>E.coli</em></p>
-
</p>
+
-
<p>
+
<p>**[BBa<em>K1337001](parts.igem.org/Part:BBa</em>K1337001)**&lt;/br&gt;
-
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.
+
<em>dgc1</em> from <em>G. hansenii</em></p>
-
</p>
+
-
</td>
+
-
</tr>
+
 +
<p>**[BBa<em>K1337002](parts.igem.org/Part:BBa</em>K1337002)**&lt;/br&gt;
 +
Cph8 signal transduction pathway compatibility tester.</p>
-
<tr> <td colspan="3"  height="15px"> </td></tr>
+
<p>**[BBa<em>K1337003](parts.igem.org/Part:BBa</em>K1337003)**&lt;/br&gt;
 +
Light mediated <em>dgc1</em> transcription construct (should produce the cellular pathway in Figure 1.)</p>
-
<tr><td colspan="3" > <h3> Parts Table</h3></td></tr>
+
<h2>Results</h2>
 +
<p>So far we have successfully amplified <em>envZ</em> from <em>E. coli</em> (Figure 2 - gel electrophoresis of PCR product from primers flanking <em>envZ</em> from <em>E. coli</em>). </p>
-
<tr><td width="45%" colspan="3"  valign="top">
+
<p>As we continue the project, we hope to successfully amplify <em>ompR</em> from <em>E. coli</em> and ligate it into pSB1C3, in order to submit our first independently produced biobrick.</p>
-
Any parts your team has created will appear in this table below:</td></tr>
+
-
</table>
+
<p>Following on from that, we hope to also produce and submit our other planned plasmids.</p>
</html>
</html>
<groupparts>iGEM013 London_BioHackspace</groupparts>
<groupparts>iGEM013 London_BioHackspace</groupparts>

Revision as of 02:49, 18 October 2014

Home Project Team Policy & Practice Protocols Safety

Parts

Introduction

The majority of parts in the iGEM registry are designed to work in E. coli, however our project is centred around genetic modification of G. hansenii. In particular, the biobricks to produce the light sensitive signal transduction pathway based around Cph8(see Project Background) do not include a gene for the expression of OmpR because it is found natively in E. coli and is therefore not required for functional expression when working in E. coli.

Aims

  • Produce a biobrick containing ompR and sequence it to provide a reliable part for future use in expression of the the Cph8 light sensitive signal transduction pathway in non E. coli chassis.

  • Provide clarifying notes in the registry on parts which have confusingly used the term "ompR" or "OmpR" to label the ompC promoter (ompCp) sequence. Or in some cases have labelled the sequence of ompR as "envZ".

  • Produce a composite biobrick for use in a broad host-range vector such as pSEVA321, pSEVA331, pSEVA351 which will show whether a a given non-E. coli chassis can functionally express the Cph8 light sensitive signal transduction pathway.

  • Produce a composite biobrick to control the production of extracellular cellulose in dgc1 knockout mutants of G. hansenii.

Parts

**[BBaK1337000](parts.igem.org/Part:BBaK1337000)**</br> ompR from E.coli

**[BBaK1337001](parts.igem.org/Part:BBaK1337001)**</br> dgc1 from G. hansenii

**[BBaK1337002](parts.igem.org/Part:BBaK1337002)**</br> Cph8 signal transduction pathway compatibility tester.

**[BBaK1337003](parts.igem.org/Part:BBaK1337003)**</br> Light mediated dgc1 transcription construct (should produce the cellular pathway in Figure 1.)

Results

So far we have successfully amplified envZ from E. coli (Figure 2 - gel electrophoresis of PCR product from primers flanking envZ from E. coli).

As we continue the project, we hope to successfully amplify ompR from E. coli and ligate it into pSB1C3, in order to submit our first independently produced biobrick.

Following on from that, we hope to also produce and submit our other planned plasmids.

<groupparts>iGEM013 London_BioHackspace</groupparts>

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