Difference between revisions of "Team:Sheffield/Description"

Line 1: Line 1:
−
{{Sheffield}}
 
 
<html>
 
<html>
 +
<head>
 +
<meta charset="utf-8">
 +
<meta http-equiv="X-UA-Compatible" content="IE=edge">
 +
<meta name="viewport" content="width=device-width, initial-scale=1">
 +
 +
<meta name="description" content="">
 +
<meta name="author" content="">
 +
 +
<title>A template page</title>
  
−
<div class="column full_size">
+
<link rel="stylesheet" type="text/css"
 +
                href="https://2016.igem.org/Template:Sheffield/style/template?action=raw&ctype=text/css" />
  
−
<p>Tell us about your project, describe what moves you and why this is something important for your team.</p>
+
                <link rel="stylesheet" type="text/css"
 +
                href="https://2016.igem.org/Template:Sheffield/style/slide?action=raw&ctype=text/css" />
 +
               
 +
                <link rel="stylesheet" type="text/css"
 +
                href="https://2016.igem.org/Template:Sheffield/style/CAS?action=raw&ctype=text/css" />
 +
               
 +
                  <script src="https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js"></script>
 +
                <script>window.jQuery || document.write('<script src="js/vendor/jquery.min.js"><\/script>')</script>
 +
                <script type = "text/javascript"
 +
        src = "http://ajax.googleapis.com/ajax/libs/jquery/2.1.3/jquery.min.js"></script>
  
−
<h5>PROJECT DESCRIPTION</h5>
+
                <script
−
<p><strong>Brainstorming & Selection Process</strong>
+
                  src="https://2016.igem.org/Template:Sheffield/scripts/min?action=raw&ctype=text/javascript"></script>
−
<br>When brainstorming for project ideas, we approached the project from different directions to generate as many ideas as possible. For instance, we looked at current and imminent world issues, from infectious diseases to plastics recycling. We researched recent scientific developments to find synthetic biology solutions that can then be applied to problems, as well as looking at past iGEM projects to see if we could build upon those ideas. We then narrowed down the list of ideas based on whether it was feasible within the project timeframe and whether the idea was able to involve and engage all team members and their areas of expertise. Based on this shortlist, we researched and expanded on each idea in detail before voting for our favorite idea.</p>
+
              <script
−
<p>We decided to focus on the issue of antibiotic resistance and the lack of diagnostic tools to differentiate between bacterial and viral infections. When the cause of an infection is unknown, antibiotics are usually prescribed as a preventative measure. However, this contributes to the rise of antibiotic resistant bacteria.</p>
+
                  src="https://2016.igem.org/Template:Sheffield/scripts/backtotopbutton?action=raw&ctype=text/javascript"></script>
−
<p><strong>What We Hope to Accomplish</strong>
+
−
<br>iGEM Sheffield 2016 aims to combat the issue of a lack of diagnostic tools by building a bedside device that can detect a bacterial infection from a viral one within 15 minutes of extracting the patient’s blood sample. We plan to design Escherichia coli receptors to detect siderophores, which are molecules produced by bacteria to scavenge iron from low-iron environments such as the bloodstream. As a proof of concept, we will only be focusing on the siderophore enterobactin.</p>
+
−
<p>Our biosensor involves the use of engineered E. coli strains that produce a detectable color change in response to the uptake of enterobactin-iron complexes. To improve the sensitivity of this system, the number of enterobactin-iron complexes being internalized by E. coli will be maximized before the actual detection step. This can be done by decoupling lipocalin-enterobactin complexes and saturating enterobactin with iron. Our detection system involves the use of the protein hemerythrin, a high-affinity iron-binding protein, that turns blue when bound to iron. By comparing the color against a standard, the cause of infection can be determined.</p>
+
  
−
<h5>What should this page contain?</h5>
+
<style type="text/css">
−
<ul>
+
    #top_title, #sideMenu{
−
<li> A clear and concise description of your project.</li>
+
      display:none;
−
<li>A detailed explanation of why your team chose to work on this particular project.</li>
+
      }
−
<li>References and sources to document your research.</li>
+
    #content{
−
<li>Use illustrations and other visual resources to explain your project.</li>
+
      background-color:black;
−
</ul>
+
      width:100%;
 +
      margin:0;
 +
      padding:0;
 +
    }
 +
    .mw-content-ltr ul {
 +
      margin-left:0px;
 +
}
 +
#blank {
 +
width:165px;
 +
}
  
 +
#shield  p {
 +
        font-size:25px;
 +
      }
  
−
</div>
+
#HQ_page th, #HQ_page td, #HQ_page table {
 +
      border:rgba(1,1,1,0);
 +
      padding:0px;
 +
      vertical-align:middle;
 +
      background-color:rgba(1,1,1,0) ;
 +
      }
  
−
<div class="column full_size" >
+
#HQ_page h1 {
 +
      font-family:Century Gothic;
 +
      font-weight:normal;
 +
}
  
−
<h5>Advice on writing your Project Description</h5>
+
#HQ_page h2 {
 +
      padding:0px;
 +
      }
 +
#HQ_page p {
 +
      text-align:left;
 +
}
  
−
<p>
+
#shield  p {
−
We encourage you to put up a lot of information and content on your wiki, but we also encourage you to include summaries as much as possible. If you think of the sections in your project description as the sections in a publication, you should try to be consist, accurate and unambiguous in your achievements.
+
        font-size:25px;
−
</p>
+
      }
  
−
<p>
+
@media (min-width:992px) and (max-width:1199px) {
−
Judges like to read your wiki and know exactly what you have achieved. This is how you should think about these sections; from the point of view of the judge evaluating you at the end of the year.
+
−
</p>
+
  
−
</div>
 
  
 +
}
  
−
<div class="column half_size" >
+
@media (min-width:768px) and (max-width:991px) {
 +
#shield  p {
 +
        font-size:20px;
 +
      }
 +
#shield li {
 +
        font-size:20px;
 +
}
 +
}
  
−
<h5>References</h5>
+
@media (max-width:767px) {
−
<p>iGEM teams are encouraged to record references you use during the course of your research. They should be posted somewhere on your wiki so that judges and other visitors can see how you thought about your project and what works inspired you.</p>
+
      #shield  p {
 +
        font-size:15px;
 +
        margin:10px;
 +
      }
 +
     
 +
#shield li {
 +
font-size:12px;
 +
}
 +
      #shield h2 {
 +
        font-size:30px;
 +
        margin-left:5px;
 +
      }
 +
     
 +
      #shield span {
 +
      font-size:18px;
 +
      }
 +
}
 +
     
 +
</style>
  
−
</div>
 
  
 +
</head>
 +
  
−
<div class="column half_size" >
+
<body style="min-height:2000px;background-color:black">
−
<h5>Inspiration</h5>
+
<nav class="navbar navbar-default navbar-fixed-top">
−
<p>See how other teams have described and presented their projects: </p>
+
      <div class="container">
−
 
+
 
−
<ul>
+
        <div class="navbar-header">
−
<li><a href="https://2014.igem.org/Team:Imperial/Project"> Imperial</a></li>
+
          <div class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar" aria-expanded="false" aria-controls="navbar">
−
<li><a href="https://2014.igem.org/Team:UC_Davis/Project_Overview"> UC Davis</a></li>
+
            <img src="https://static.igem.org/mediawiki/2016/a/a5/T--Sheffield--Website-home-mobile.png">
−
<li><a href="https://2014.igem.org/Team:SYSU-Software/Overview">SYSU Software</a></li>
+
          </div>
−
</ul>
+
          <!-- <a class="navbar-brand" href="#">Igem Sheff 16</a> -->
−
</div>
+
        </div>
−
 
+
       
 +
        <div id="navbar" class="navbar-collapse collapse">
 +
 +
          <ul class="nav navbar-nav">
 +
 
 +
<li id="navimage" >
 +
<table id="imgtable">
 +
<th>
 +
<div class="navimagediv">
 +
<a href="https://2016.igem.org/Team:Sheffield"><img src="https://static.igem.org/mediawiki/2016/1/18/T--Sheffield--navbar-logo.png"></a>
 +
</div>
 +
</th>
 +
</table>
 +
            </li>
 +
    <li class="dropdown" id="li-home">
 +
              <a href="https://2016.igem.org/Team:Sheffield" >
 +
  <center>
 +
<table id="navtable">
 +
<th>
 +
<center>
 +
<div id="nav-intro">
 +
</div>
 +
</center>
 +
</th>
 +
<tr>
 +
<td>
 +
<p>HOME</p>
 +
</td>
 +
</tr>
 +
</table>
 +
  </center>
 +
              </a>
 +
            </li> 
 +
            <li class="dropdown">
 +
            <a href="https://2016.igem.org/Team:Sheffield/Description" class="dropdown-toggle"  >
 +
  <center>
 +
<table id="navtable">
 +
<th>
 +
<center>
 +
<div id="nav-intro">
 +
<img src="https://static.igem.org/mediawiki/2016/5/53/T--Sheffield--Intro-Icon.png">
 +
</div>
 +
</center>
 +
</th>
 +
<tr>
 +
<td>
 +
<p>INTRO</p>
 +
</td>
 +
</tr>
 +
</table>
 +
  </center>
 +
              </a>
 +
            </li>          
 +
           
 +
            <li class="dropdown">
 +
              <a href="https://2016.igem.org/Team:Sheffield/project" class="dropdown-toggle"  >
 +
  <center>
 +
<table id="navtable">
 +
<th>
 +
<center>
 +
<div id="nav-project">
 +
<img src="https://static.igem.org/mediawiki/2016/8/86/T--Sheffield--icon-project.png">
 +
</div>
 +
</center>
 +
</th>
 +
<tr>
 +
<td>
 +
<p>PROJECT</p>
 +
</td>
 +
</tr>
 +
</table>
 +
  </center>
 +
              </a>
 +
            </li>
 +
 +
<li class="dropdown">
 +
              <a href="https://2016.igem.org/Team:Sheffield/Team" class="dropdown-toggle" >
 +
  <center>
 +
<table id="navtable">
 +
<th>
 +
<center>
 +
<div id="nav-team">
 +
<img src="https://static.igem.org/mediawiki/2016/0/07/T--Sheffield--icon-team.png">
 +
</div>
 +
</center>
 +
</th>
 +
<tr>
 +
<td>
 +
<p>TEAM</p>
 +
</td>
 +
</tr>
 +
</table>
 +
  </center>
 +
              </a>
 +
            </li>
 +
         
 +
<li class="dropdown">
 +
              <a href="https://2016.igem.org/Team:Sheffield/Notebook" class="dropdown-toggle" >
 +
  <center>
 +
<table id="navtable">
 +
<th>
 +
<center>
 +
<div id="nav-notebook">
 +
<img src="https://static.igem.org/mediawiki/2016/c/ce/T--Sheffield--icon-notebook.png">
 +
</div>
 +
</center>
 +
</th>
 +
<tr>
 +
<td>
 +
<p>NOTES</p>
 +
</td>
 +
</tr>
 +
</table>
 +
  </center>
 +
              </a>
 +
            </li>  
 +
           
 +
            <li class="dropdown">
 +
              <a href="https://2016.igem.org/Team:Sheffield/judging" class="dropdown-toggle" >
 +
  <center>
 +
<table id="navtable">
 +
<th>
 +
<center>
 +
<div id="nav-judging">
 +
<img src="https://static.igem.org/mediawiki/2016/3/35/T--Sheffield--icon-judging.png">
 +
</div>
 +
</center>
 +
</th>
 +
<tr>
 +
<td>
 +
<p>JUDGING</p>
 +
</td>
 +
</tr>
 +
</table>
 +
  </center>
 +
              </a>
 +
            </li> 
 +
        </div><!--/.nav-collapse -->
 +
      </div>
 +
    </nav>
 +
   
 +
    <div id="shield">
 +
    <div class = "container" >
 +
<div style="height:100px"></div>
 +
<div class="heading">
 +
<table>
 +
<th class="banner-img">
 +
<img src="https://static.igem.org/mediawiki/2016/6/67/T--Sheffield--heading-banner.png">
 +
</th>
 +
<th>
 +
<div class="heading-title"><h1 style="padding:0px">Introduction</h1></div>
 +
</th>
 +
<th class="banner-img">
 +
<img src="https://static.igem.org/mediawiki/2016/b/b2/T--Sheffield--heading-banner-flip.png">
 +
</th>
 +
</table>
 +
</div>
 +
<div class = "jumbotron">
 +
                      <h2>Brainstorming & Selection Process</h2>
 +
<p>When brainstorming for project ideas, we approached the project from different directions to generate as many ideas as possible. For instance, we looked at current and imminent world issues, from infectious diseases to plastics recycling. We researched recent scientific developments to find synthetic biology solutions that can then be applied to problems, as well as looking at past iGEM projects to see if we could build upon those ideas. We then narrowed down the list of ideas based on whether it was feasible within the project timeframe and whether the idea was able to involve and engage all team members and their areas of expertise. Based on this shortlist, we researched and expanded on each idea in detail before voting for our favorite idea.</p>
 +
<p>We decided to focus on the issue of antibiotic resistance and the lack of diagnostic tools to differentiate between bacterial and viral infections. When the cause of an infection is unknown, antibiotics are usually prescribed as a preventative measure. However, this contributes to the rise of antibiotic resistant bacteria.</p>
 +
      <h2>What We Hope to Accomplish</h2>
 +
<p>iGEM Sheffield 2016 aims to combat the issue of a lack of diagnostic tools by building a bedside device that can detect a bacterial infection from a viral one within 15 minutes of extracting the patient’s blood sample. We plan to design Escherichia coli receptors to detect siderophores, which are molecules produced by bacteria to scavenge iron from low-iron environments such as the bloodstream. As a proof of concept, we will only be focusing on the siderophore enterobactin.</p>
 +
<p>Our biosensor involves the use of engineered <i>E. coli</i> strains that produce a detectable color change in response to the uptake of enterobactin-iron complexes. To improve the sensitivity of this system, the number of enterobactin-iron complexes being internalized by <i>E. coli</i> will be maximized before the actual detection step. This can be done by decoupling lipocalin-enterobactin complexes and saturating enterobactin with iron. Our detection system involves the use of the protein hemerythrin, a high-affinity iron-binding protein, that turns blue when bound to iron. By comparing the color against a standard, the cause of infection can be determined.</p>
  
 +
 +
</div>
 +
</center>
 +
    </div>
 +
    </div>
 +
<div class="glossary"><a href="https://2016.igem.org/Team:Sheffield/glossary"><img src="https://static.igem.org/mediawiki/2016/8/86/T--Sheffield--Glossary.png"></a></div>
 +
<div class="backToTop"><img src="https://static.igem.org/mediawiki/2016/5/55/T--Sheffield--TopArrow.png"></div>
 +
    <!-- Bootstrap core JavaScript
 +
    ================================================== -->
 +
    <!-- Placed at the end of the document so the pages load faster -->
 +
   
 +
   
 +
   
 +
</body>
  
 
</html>
 
</html>

Revision as of 13:32, 17 October 2016

A template page

Introduction

Brainstorming & Selection Process

When brainstorming for project ideas, we approached the project from different directions to generate as many ideas as possible. For instance, we looked at current and imminent world issues, from infectious diseases to plastics recycling. We researched recent scientific developments to find synthetic biology solutions that can then be applied to problems, as well as looking at past iGEM projects to see if we could build upon those ideas. We then narrowed down the list of ideas based on whether it was feasible within the project timeframe and whether the idea was able to involve and engage all team members and their areas of expertise. Based on this shortlist, we researched and expanded on each idea in detail before voting for our favorite idea.

We decided to focus on the issue of antibiotic resistance and the lack of diagnostic tools to differentiate between bacterial and viral infections. When the cause of an infection is unknown, antibiotics are usually prescribed as a preventative measure. However, this contributes to the rise of antibiotic resistant bacteria.

What We Hope to Accomplish

iGEM Sheffield 2016 aims to combat the issue of a lack of diagnostic tools by building a bedside device that can detect a bacterial infection from a viral one within 15 minutes of extracting the patient’s blood sample. We plan to design Escherichia coli receptors to detect siderophores, which are molecules produced by bacteria to scavenge iron from low-iron environments such as the bloodstream. As a proof of concept, we will only be focusing on the siderophore enterobactin.

Our biosensor involves the use of engineered E. coli strains that produce a detectable color change in response to the uptake of enterobactin-iron complexes. To improve the sensitivity of this system, the number of enterobactin-iron complexes being internalized by E. coli will be maximized before the actual detection step. This can be done by decoupling lipocalin-enterobactin complexes and saturating enterobactin with iron. Our detection system involves the use of the protein hemerythrin, a high-affinity iron-binding protein, that turns blue when bound to iron. By comparing the color against a standard, the cause of infection can be determined.