Team:UiOslo Norway

From 2014.igem.org

(Difference between revisions)
 
(27 intermediate revisions not shown)
Line 1: Line 1:
-
{{CSS/Main}}
+
{{:Team:UiOslo_Norway/Include/Header}}
-
 
+
<html>
<html>
 +
<body>
-
<!--main content -->
+
<div class="container">
-
<table width="70%" align="center">
+
-
 
+
-
<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:UiOslo_Norway"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:UiOslo_Norway/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://2014.igem.org/Team:UiOslo_Norway/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:UiOslo_Norway/Achievements"style="color:#000000"> Achievements</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:UiOslo_Norway/Notebook"style="color:#000000"> Notebook</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>
+
-
 
+
-
 
+
-
<!--requirements section -->
+
-
<tr><td colspan="3"> <h3> Requirements </h3></td></tr>
+
-
<tr>
+
-
<td width="45%"  valign="top">
+
-
 
+
-
<p> Please be sure to keep these links, your audience will want to find your: </p>
+
-
 
+
-
<!-- Links to other team pages -->
+
-
<ul>
+
-
<li><a href="https://2014.igem.org/Team:UiOslo_Norway">Home</a> </li>
+
-
<li><a href="https://2014.igem.org/Team:UiOslo_Norway/Team">Team</a> </li>
+
-
<li><a href="https://igem.org/Team.cgi?year=2013&team_name=UiOslo_Norway">Official Team Profile</a> </li>
+
-
<li><a href="https://2014.igem.org/Team:UiOslo_Norway/Project">Project</a> </li>
+
-
<li><a href="https://2014.igem.org/Team:UiOslo_Norway/Parts">Parts</a> </li>
+
-
<li><a href="https://2014.igem.org/Team:UiOslo_Norway/Modeling">Modeling</a> </li>
+
-
<li><a href="https://2014.igem.org/Team:UiOslo_Norway/Notebook">Notebook</a> </li>
+
-
<li><a href="https://2014.igem.org/Team:UiOslo_Norway/Safety">Safety</a> </li>
+
-
<li><a href="https://2014.igem.org/Team:UiOslo_Norway/Attributions">Attributions</a> </li>
+
-
 
+
-
</ul>
+
-
 
+
-
</td>
+
-
 
+
-
<td > </td>
+
-
<td width="45%">
+
-
 
+
-
<p>There are a few wiki requirements teams must follow:</p>
+
-
<ul>
+
-
<li>All pages, images and files must be hosted on the <a href ="https://2014.igem.org/Special:Upload">  2014.igem.org server</a>. </li>
+
-
<li>All pages must be created under the team’s name space.</li>
+
-
<li>As part of your documentation, keep the links from the menu to the left. </li>
+
-
<li>Do not use flash in wiki code. </li>
+
-
<li>The <a href="https://static.igem.org/mediawiki/igem.org/6/60/Igemlogo_300px.png"> iGEM logo </a> should be placed on the upper part of every page and should link to <a href="https://2014.igem.org/Main_Page">2014.igem.org</a>.</li>
+
-
</ul>
+
-
<p>Visit the <a href="https://2014.igem.org/Wiki_How-To"> Wiki How To page </a> for a complete list of requirements, tips and other useful information. </p>
+
-
</td>
+
<div class="row" style="margin-top: 40px;">
-
</tr>
+
<div class="col-md-3"></div>
 +
<div class="col-md-6">
 +
<img
 +
class="img-responsive"
 +
src="https://static.igem.org/mediawiki/2014/4/49/UiOslo_Norway_logo_merged.jpg"
 +
alt="microOrganizer">
 +
</div>
 +
<div class="col-md-3"></div>
 +
</div>
 +
<div class="row">
 +
<div class="col-md-12">
 +
<h2>The Idea</h2>
 +
<p>One of the most fundamental distinctions in nature is the one between unicellular and multicellular organisms. Multicellular organisms, like humans, can perform a wide specter of different tasks due to the highly ordered and differentiated system of cells. This ability is lacking from the simpler unicellular organisms like <em>E. coli</em>.</p>
 +
<p>But is it possible to build complex ordered structures from bacteria?</p>
 +
<p><strong>Is it possible to manipulate <em>E.coli</em> to become artificially multicellular?</strong></p>
 +
<p>The UiO Oslo iGEM team has taken the challenge and is aiming to build a microOrganizer – a system for organizing <em>E. coli</em> in a predetermined way.</p>
 +
</div>
 +
</div>
 +
<div class="row" style="margin-top: 20px;">
 +
<hr>
 +
</div>
-
<tr> <td colspan="3" height="15px"> </td></tr>
+
<div class="row">
-
<tr><td bgColor="#e7e7e7" colspan="3" height="1"> </tr>
+
<div class="col-md-2"></div>
 +
<div class="col-md-8">
 +
<img
 +
class="img-responsive"
 +
src="https://static.igem.org/mediawiki/2014/thumb/1/13/UiO_Oslo_MicroOrganizer_ill_with_logo.png/713px-UiO_Oslo_MicroOrganizer_ill_with_logo.png"
 +
alt="microOrganizer">
 +
</div>
 +
<div class="col-md-2"></div>
 +
</div>
 +
<div class="row" style="margin-top: 20px;">
 +
<div class="col-md-12">
 +
<p>In our project we are trying to create BioBricks that gives <em>E. coli</em> the ability to bind physically to other bacteria and transfer a signal to the inside of the bacteria about its binding state. This signal can then be used to select for only those bacteria that have bound to each other in the correct configuration. This will make it possible to build and preserve any desired configuration of different bacteria. Thus bacteria can be units in even more complex genetically engineered machines where each type of bacteria has its own function and location in complex multistep procedures.</p>
 +
<p>The system should have a wide variety of applications and could be used in for instance biological manufacturing, remediation processes, and biocomputers.</p>
 +
</div>
 +
</div>
-
<!--tips  -->
+
<div class="row" style="margin-top: 20px;">
-
<tr><td colspan="3" > <h3> Tips  </h3></td></tr>
+
<hr>
 +
</div>
-
<tr>
+
<div class="row">
-
<td width="45%" valign="top">  
+
<div class="col-md-12">
-
<p>We are currently working on providing teams with some easy to use design templates.
+
<h2>The System</h2>
-
<br> In the meantime you can also view other team wikis for inspiration! Here are some very good examples</p>
+
<p>So what kinds of BioBricks could possibly fulfill these tasks?</p>
 +
<p>The answer is split enzymes coupled to autotransporter proteins from <em>E. coli</em>. Split enzymes are enzymes consisting of two or more separated parts that will only work when they are assembled correctly. The enzyme parts also have a natural affinity for each other and can assemble and give activity in solution.</p>
 +
<p>By expressing different parts of the enzyme on the surface of different bacteria, the bacteria will have a unique surface identity and the potential to bind to the bacteria with the matching enzyme part. Only interacting bacteria will give enzyme activity and this activity can be used to select against unbound bacteria by inducing or inhibiting the bacterias gene expression. The autotransporter makes sure the enzyme parts are presented and attached to the bacterial surface.</p>
 +
</div>
 +
</div>
-
<ul>
+
<div class="row" style="margin-top: 20px;">
-
<li> <a href="https://2013.igem.org/Team:SDU-Denmark/"> 2013 SDU Denmark </a> </li>
+
<div class="col-md-12">
-
<li> <a href="https://2013.igem.org/Team:SYSU-China">2013 SYSU China</a> </li>
+
<img
-
<li> <a href="https://2013.igem.org/Team:Shenzhen_BGIC_ATCG"> 2013 Shenxhen BGIG ATCG </a></li>
+
class="img-responsive"
-
<li> <a href="https://2013.igem.org/Team:Colombia_Uniandes">2013 Colombia Unianades </a></li>
+
src="https://static.igem.org/mediawiki/2014/d/d8/UiO_Oslo_signalingmechanism.png"
-
<li> <a href="https://2013.igem.org/Team:Lethbridge">2013 Lethbridge</a></li>
+
alt="The System">
-
</ul>
+
</div>
 +
</div>
-
<p>For a full wiki list, you can visit <a href="https://igem.org/Team_Wikis?year=2013">iGEM 2013 web sites </a> and <a href="https://igem.org/Team_Wikis?year=2012">iGEM 2012 web sites</a> lists. </p>
+
<div class="text-center" style="margin-top: 40px;margin-bottom:20px;">
-
</td>
+
<h3>Want to know more about our project? Continue reading on our <a href="/Team:UiOslo_Norway/Project">Project Details</a> page.</h3>
 +
</div>
-
<td> </td>
+
<div class="text-center">
-
<td width="45%">  
+
<img src="https://static.igem.org/mediawiki/2014/f/ff/Uioslo_norway_Uio.jpg" height="100px">  
 +
<img src="https://static.igem.org/mediawiki/2014/8/87/Uioslo_norway_Nbs.jpg" height="100px">
 +
</div>
-
<p>This wiki will be your team’s first interaction with the rest of the world, so here are a few tips to help you get started: </p>
+
</div>
-
<ul>
+
<div class="footer">
-
<li>State your accomplishments! Tell people what you have achieved from the start. </li>
+
<div class="container">
-
<li>Be clear about what you are doing and what you plan to do.</li>
+
<p class="text-muted text-center">Created using Bootstrap and jQuery.</p>
-
<li>You have a global audience! Consider the different backgrounds that your users come from.</li>
+
</div>
-
<li>Make sure information is easy to find; nothing should be more than 3 clicks away.  </li>
+
</div>
-
<li>Avoid using very small fonts and low contrast colors; information should be easy to read. </li>
+
-
<li>Start documenting your project as early as possible; don’t leave anything to the last minute before the Wiki Freeze. For a complete list of deadlines visit the <a href="">iGEM 2013 calendar</a> </li>
+
-
<li>Have lots of fun! </li>
+
-
</ul>
+
-
</br>
+
-
</td>
+
-
</tr>
+
-
</table>
+

Latest revision as of 20:34, 28 April 2015

UiOslo IGEM 2014

microOrganizer

The Idea

One of the most fundamental distinctions in nature is the one between unicellular and multicellular organisms. Multicellular organisms, like humans, can perform a wide specter of different tasks due to the highly ordered and differentiated system of cells. This ability is lacking from the simpler unicellular organisms like E. coli.

But is it possible to build complex ordered structures from bacteria?

Is it possible to manipulate E.coli to become artificially multicellular?

The UiO Oslo iGEM team has taken the challenge and is aiming to build a microOrganizer – a system for organizing E. coli in a predetermined way.


microOrganizer

In our project we are trying to create BioBricks that gives E. coli the ability to bind physically to other bacteria and transfer a signal to the inside of the bacteria about its binding state. This signal can then be used to select for only those bacteria that have bound to each other in the correct configuration. This will make it possible to build and preserve any desired configuration of different bacteria. Thus bacteria can be units in even more complex genetically engineered machines where each type of bacteria has its own function and location in complex multistep procedures.

The system should have a wide variety of applications and could be used in for instance biological manufacturing, remediation processes, and biocomputers.


The System

So what kinds of BioBricks could possibly fulfill these tasks?

The answer is split enzymes coupled to autotransporter proteins from E. coli. Split enzymes are enzymes consisting of two or more separated parts that will only work when they are assembled correctly. The enzyme parts also have a natural affinity for each other and can assemble and give activity in solution.

By expressing different parts of the enzyme on the surface of different bacteria, the bacteria will have a unique surface identity and the potential to bind to the bacteria with the matching enzyme part. Only interacting bacteria will give enzyme activity and this activity can be used to select against unbound bacteria by inducing or inhibiting the bacterias gene expression. The autotransporter makes sure the enzyme parts are presented and attached to the bacterial surface.

The System

Want to know more about our project? Continue reading on our Project Details page.