Difference between revisions of "Team:UMBC-Maryland/Description"

(added logo)
Line 1: Line 1:
{{UMBC-Maryland}}
+
{{Template_All_Teams}}
 +
[[File:Team_UMBC-Maryland_banner.jpg|600px]]
 +
<html>
 +
 
 +
<style type="text/css">
 +
 
 +
/* PAGE LAYOUT */
 +
 +
/* page background color*/
 +
body {
 +
background-color: #A7A9AB;
 +
}
 +
 
 +
 
 +
/* Creates a container that will wrap all of the content inside your wiki pages. */
 +
#mainContainer { 
 +
width: 980px;
 +
overflow: hidden;
 +
float:left;
 +
margin-left: 20px;
 +
background-color: #EEEDEA;
 +
border-bottom: 6px solid #EE3e53;
 +
}
 +
 
 +
/* Creates the container for the menu */
 +
#menuContainer  {
 +
float:right;
 +
width: 150px;
 +
background-color: #0e232f;
 +
height: 100%;
 +
border-top: 6px solid #EE3e53;
 +
font-family: "Arial", Helvetica, sans-serif;
 +
}
 +
 
 +
/* Creates the container for the content */
 +
#contentContainer {
 +
background-color: #EEEDEA;
 +
width: 810px;
 +
float: left;
 +
padding: 10px;
 +
border-top: 6px solid #EE3e53;
 +
}
 +
 
 +
 
 +
/*VISUAL STYLE (TABLES, FONTS, LINKS, IMAGES, UL) */
 +
 
 +
 
 +
/*Change the styling of text for everything inside main container*/
 +
#mainContainer p {
 +
font-family: "Arial", Helvetica, sans-serif;
 +
font-size: 12px;
 +
color: #0e232f;
 +
}
 +
 +
/*This changes the color and font family */
 +
#contentContainer h1, h2, h3, h4, h5, h6 {
 +
font-family: "Arial", Helvetica, sans-serif;
 +
color: #0e232f;
 +
border-bottom: none;
 +
font-weight: bold;
 +
text-transform: uppercase;
 +
}
 +
 
 +
/*Style of the links - links are different inside the menu */
 +
#contentContainer a {
 +
font-weight: bold;
 +
color: #ee3e53;
 +
}
 +
 
 +
  /* Styling links on hover- links are different inside the menu */
 +
#contentContainer a:hover{
 +
color: #f4b248;
 +
}
 +
 
 +
/*Change the styling of tables */
 +
        #contentContainer table {
 +
    border: 1px solid #0e232f;
 +
    border-collapse: collapse;
 +
    width: 90%
 +
    margin: auto;
 +
    margin-bottom: 15px;
 +
    margin-top: 15px;
 +
    margin-right: 10px;
 +
    margin-left: 10px;
 +
    }
 +
 
 +
/*Change the styling of table cells*/
 +
    #contentContainer  td {
 +
    padding: 10px;
 +
    border: 1px solid #0e232f;
 +
    border-collapse: collapse;
 +
    vertical-align: text-top;
 +
    background-color: #EEEDEA;
 +
    }
 +
 
 +
/*Change the styling of table headers */
 +
    #contentContainer th {
 +
    padding: 10px;
 +
    border: 1px solid #0e232f;
 +
    border-collapse: collapse;
 +
    vertical-align: text-top;
 +
    background-color: #e8d5b7;
 +
    }
 +
 
 +
 
 +
/*MENU STYLING */
 +
 
 +
/*Styling for the links in the menu */
 +
#menuContainer a {
 +
color: #EEEDEA;
 +
text-decoration:none;
 +
font-weight: bold;
 +
}
 +
 
 +
/* Sets the style for lists inside menuContainer  */
 +
#menuContainer ul {
 +
width:100%;
 +
list-style: none;
 +
margin: auto;
 +
padding-top: 10px;
 +
padding-bottom: 10px;
 +
 
 +
}
 +
 
 +
/*Styles the list items to become menu buttons */
 +
#menuContainer ul li {
 +
display: block;
 +
position: relative;
 +
padding: 10px;
 +
margin-bottom:5px;
 +
padding-left: -20px;
 +
}
 +
 
 +
#menuContainer ul li:hover {
 +
background: #F4B248;
 +
color: #0e232f;
 +
}
 +
 
 +
 
 +
/*HIde the submenus and removes the padding */
 +
#menuContainer li ul {
 +
display: none;
 +
padding-top:15px;
 +
margin-left: -9px;
 +
}
 +
 
 +
/*Shows the submenus once you hover*/
 +
#menuContainer li:hover ul {
 +
display: block;
 +
}
 +
 
 +
/*style the submenu buttons*/
 +
#menuContainer li ul li {
 +
background: #0E232F;
 +
width: 100%;
 +
}
 +
 
 +
#menuContainer li ul li:hover {
 +
background: #EE3E53;
 +
color: #fff;
 +
}
 +
 
 +
 
 +
 
 +
/*CLASSES */
 +
/*Clear class for all the pages, adds spacing too*/
 +
.clear{
 +
clear:both;
 +
height: 10px;
 +
}
 +
 
 +
/* highlight box for special messages */
 +
    .highlightBox {
 +
    width:500px;
 +
            margin:auto;
 +
            background-color: #E8D5B7;
 +
    margin-bottom: 15px;
 +
    margin-top: 15px;
 +
    padding: 15px;
 +
    padding-top: 5px;
 +
          }
 +
 
 +
</style>
 +
<!-- End of CSS -->
 +
 
 +
 
 +
<!-- Start of the template html elements. -->
 +
<div id ="mainContainer"><!--This div will close on the page.-->
 +
 
 +
<div id="bannerContainer">
 +
<br> <br>
 +
 +
</div>
 +
 
 +
<!-- Start of menu -->
 +
<div id="menuContainer">
 +
<!-- This list is your menu, every list item is a menu button and nested listed become submenu buttons -->
 +
<ul>
 +
<a href="https://2015.igem.org/Team:UMBC-Maryland"><li>HOME</li></a>
 +
 
 +
<a href="https://2015.igem.org/Team:UMBC-Maryland/Team"><li>TEAM</li></a>
 +
 
 +
 
 +
<a href="#"><li>PROJECT
 +
            <ul>
 +
<a href="https://2015.igem.org/Team:UMBC-Maryland/Description"><li>Description</li></a>
 +
<a href="https://2015.igem.org/Team:UMBC-Maryland/Experiments"><li>Experiments & Protocols</li></a> 
 +
<a href="https://2015.igem.org/Team:UMBC-Maryland/Results"><li>Results</li></a> 
 +
</ul>
 +
</li></a>
 +
 
 +
<a href="#"><li>PARTS
 +
            <ul>
 +
<a href="https://2015.igem.org/Team:UMBC-Maryland/Parts"><li>Team Parts</li></a>
 +
<a href="https://2015.igem.org/Team:UMBC-Maryland/Basic_Part"><li>Basic Parts</li></a> 
 +
<a href="https://2015.igem.org/Team:UMBC-Maryland/Composite_Part"><li>Composite Parts</li></a>
 +
<a href="https://2015.igem.org/Team:UMBC-Maryland/Part_Collection"><li>Part Collection</li></a> 
 +
</ul>
 +
</li></a>
 +
 
 +
<a href="https://2015.igem.org/Team:UMBC-Maryland/Notebook"><li>NOTEBOOK</li></a>
 +
     
 +
<a href="https://2015.igem.org/Team:UMBC-Maryland/Attributions"><li>ATTRIBUTIONS</li></a>
 +
 
 +
<a href="https://2015.igem.org/Team:UMBC-Maryland/Collaborations"><li>COLLABORATIONS</li></a>
 +
 
 +
<a href="https://2015.igem.org/Team:UMBC-Maryland/Practices"><li>HUMAN PRACTICES</li></a>
 +
 
 +
<a href="https://2015.igem.org/Team:UMBC-Maryland/Safety"><li>SAFETY</li></a>
 +
 
 +
<a href="https://2015.igem.org/Team:UMBC-Maryland/Modeling"><li>MODELING</li></a>
 +
 
 +
<a href="https://2015.igem.org/Team:UMBC-Maryland/Measurement"><li>MEASUREMENT</li></a>
 +
 
 +
<a href="https://2015.igem.org/Team:UMBC-Maryland/Software"><li>SOFTWARE</li></a>
 +
 
 +
<a href="https://2015.igem.org/Team:UMBC-Maryland/Entrepreneurship"><li>ENTREPRENEURSHIP</li></a>
 +
 
 +
</ul>
 +
</div>
 +
<!-- End of menu  -->
 +
 
 +
<!-- Start of content -->
 +
<div id="contentContainer"><!--This div will close on the page.-->
 +
</html>
 
<html>
 
<html>
 
<img  title = 'UMBC iGEM logo' align = 'right' src = 'https://static.igem.org/mediawiki/2015/5/58/UMBCiGemlogo.png' height = '400' width = '400'</>
 
<img  title = 'UMBC iGEM logo' align = 'right' src = 'https://static.igem.org/mediawiki/2015/5/58/UMBCiGemlogo.png' height = '400' width = '400'</>

Revision as of 04:20, 14 August 2015

Team UMBC-Maryland banner.jpg



Project Description

Copper is a major pollutant in a variety of fresh water ecosystems. When copper is oxidized from Cu+ to Cu2+, it often produces a free radical known as a reactive oxygen species (ROS) which is capable of severely damaging any biological molecules it comes into contact with. This damage at the molecular level has been linked to diseases such as Parkinson's, Alzheimer's, and Prion diseases. E. coli have been engineered to have increased copper uptake; however, due to the toxicity of copper, the E. coli quickly saturate and are unable to uptake any more copper. Our goal is to increase the efficiency of copper uptake in E. coli for the purpose of bioremediation in fresh water ecosystems. We plan on doing this by increasing our engineered cells' resistance to copper toxicity as well as increasing their ability to uptake copper.

In order to make engineered cells more resistant to copper toxicity, we will be genetically engineering E. coli with enhanced copper tolerance by giving it a gene for yeast metallothionein. This protein will bind 11 copper atoms, making them less reactive and less toxic. This protein is also an antioxidant that can detoxify hydroxyl radicals with its cysteine groups.

We plan on creating three separate cell lines that contain a metallothionein gene in different forms. One is the yeast metallothionein CUP1 gene directly transformed into E. coli. A second is the CUP1 gene codon optimized for E. coli. The third is metallothionein that will adhere to the outer membrane of E. coli. This will be done by fusing the CUP1 gene sequence into the lamB transport channel. This will cause metallothionein to adhere to the outer surface of E. coli by being bound to one of E. coli’s outer membrane transporters. This should ideally allow engineered cells to be able to sequester copper without getting as much inside, making copper less toxic to them.

Future efforts to bring this project to its complete application in polluted waters will include several additional genes. Superoxide dismutase and catalase are integral antioxidant proteins that are key to radical scavenging. Without them, ROS will continue to cause cell damage as quickly as heavy metals like copper will produce ROS. Superoxide dismutase converts superoxide ROS molecules into hydrogren peroxide. Catalse converts hydrogen peroxide into water. In addition to these antioxidants, a buoyancy gene under the control of a copper sensitive promoter can be utilized to gather and collect engineered cells. The use of these combined tools will aid in the harvesting of heavy metals such as copper from polluted waters.


What should this page contain?
  • A clear and concise description of your project.
  • A detailed explanation of why your team chose to work on this particular project.
  • References and sources to document your research.
  • Use illustrations and other visual resources to explain your project.

Advice on writing your Project Description

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.

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.


References

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 though about your project and what works inspired you.

Inspiration

See how other teams have described and presented their projects: