Difference between revisions of "Team:British Columbia"

m
m
Line 15: Line 15:
 
<p>To accomplish this task, we are designing a two-part microbial community. One half will be responsible for transforming biomass feeds stalks such as lignin and cellulose into useful growth substrates. While the other half will focus on using these growth substrates for the production of useful products. </p>
 
<p>To accomplish this task, we are designing a two-part microbial community. One half will be responsible for transforming biomass feeds stalks such as lignin and cellulose into useful growth substrates. While the other half will focus on using these growth substrates for the production of useful products. </p>
  
<p>To create our biomass transforming bacterium, we will use the robust surface expression system in the bacterium Caulobacter crescentus to display biomass transforming enzymes, mimicking the cellulosomes and laccases found in natural biomass degrading bacteria. To create our production bacterium, we will engineer Escherichia coli, to produce violacein. Violacein is a high-value natural product with interesting pharmacological properties. It also has the benefit of being easily detected and quantified, allowing for the validation of our approach. When combined, these bacterial strains will be able to work together to degrade and valorize biomass. </p>
+
<p>To create our biomass transforming bacterium, we will use the robust surface expression system in the bacterium <i>Caulobacter crescentus</i> to display biomass transforming enzymes, mimicking the cellulosomes and laccases found in natural biomass degrading bacteria. To create our production bacterium, we will engineer <i>Escherichia coli</i>, to produce violacein. Violacein is a high-value natural product with interesting pharmacological properties. It also has the benefit of being easily detected and quantified, allowing for the validation of our approach. When combined, these bacterial strains will be able to work together to degrade and valorize biomass. </p>
  
<p>So far our team has been working to characterize a bio-bricked β-carotene construct in E. coli in order to do an initial proof of concept, we have also been working on the violacein construct. Simultaneously we have been cloning several laccases and celluloses into the s-layer protein of C. crescentus. We hope to get functional expression of our enzymes onto the s-layer and characterize the enzymatic activity to build and active model for our system which we can test by growing the two bacteria together in minimal media with restricted carbon sources. </p>
+
<p>So far our team has been working to characterize a bio-bricked β-carotene construct in <i>E. coli</i> in order to do an initial proof of concept, we have also been working on the violacein construct. Simultaneously we have been cloning several laccases and celluloses into the s-layer protein of <i>C. crescentus</i>. We hope to get functional expression of our enzymes onto the s-layer and characterize the enzymatic activity to build and active model for our system which we can test by growing the two bacteria together in minimal media with restricted carbon sources. </p>
  
 
</div>
 
</div>
Line 57: Line 57:
 
<h5> Editing your wiki </h5>
 
<h5> Editing your wiki </h5>
 
<p>On this page you can document your project, introduce your team members, document your progress and share your iGEM experience with the rest of the world! </p>  
 
<p>On this page you can document your project, introduce your team members, document your progress and share your iGEM experience with the rest of the world! </p>  
<p> <a href="https://2016.igem.org/wiki/index.php?title=Team:Example&action=edit"> Click here to edit this page! </a></p>
+
<p> <a href="https://2016.igem.org/wiki/index.php?title=Team:Example&action=edit"> </a>Use WikiTools - Edit in the black menu bar to edit this page</p>
  
 
</div>
 
</div>
Line 93: Line 93:
 
<h5> Uploading pictures and files </h5>
 
<h5> Uploading pictures and files </h5>
 
<p> You can upload your pictures and files to the iGEM 2016 server. Remember to keep all your pictures and files within your team's namespace or at least include your team's name in the file name. <br />
 
<p> You can upload your pictures and files to the iGEM 2016 server. Remember to keep all your pictures and files within your team's namespace or at least include your team's name in the file name. <br />
When you upload, set the "Destination Filename" to <code>Team:YourOfficialTeamName/NameOfFile.jpg</code>. (If you don't do this, someone else might upload a different file with the same "Destination Filename", and your file would be erased!)</p>
+
When you upload, set the "Destination Filename" to <br><code>T--YourOfficialTeamName--NameOfFile.jpg</code>. (If you don't do this, someone else might upload a different file with the same "Destination Filename", and your file would be erased!)</p>
  
  

Revision as of 05:05, 30 June 2016

Project Description

Petroleum-derived chemicals are used as building blocks to create a variety of products we take for granted in our day to day lives. And while these molecules have proven to be critical for modern society, their overuse has had significant negative environmental and societal impacts. Microbial biocatalysts play a prominent role in the future of renewable biomass degradation into bio-equivalent chemicals that can be used directly in established industrial processes. However, there is high cost to process raw biomass into a usable form which has remained a major obstacle in successfully implementing these techniques in industry.

During our brainstorming process we came up with the initial idea of using an engineered microbial community to effectively transform biomass into useful products. We were inspired by new research at our university on the expression of functional enzymes onto the S-Layer of certain strains of bacteria. We aim to use these new techniques together with traditional bacterial bio-catalytic pathways to make the processing and utilization of renewable biomass feedstocks cheaper and more efficient.

To accomplish this task, we are designing a two-part microbial community. One half will be responsible for transforming biomass feeds stalks such as lignin and cellulose into useful growth substrates. While the other half will focus on using these growth substrates for the production of useful products.

To create our biomass transforming bacterium, we will use the robust surface expression system in the bacterium Caulobacter crescentus to display biomass transforming enzymes, mimicking the cellulosomes and laccases found in natural biomass degrading bacteria. To create our production bacterium, we will engineer Escherichia coli, to produce violacein. Violacein is a high-value natural product with interesting pharmacological properties. It also has the benefit of being easily detected and quantified, allowing for the validation of our approach. When combined, these bacterial strains will be able to work together to degrade and valorize biomass.

So far our team has been working to characterize a bio-bricked β-carotene construct in E. coli in order to do an initial proof of concept, we have also been working on the violacein construct. Simultaneously we have been cloning several laccases and celluloses into the s-layer protein of C. crescentus. We hope to get functional expression of our enzymes onto the s-layer and characterize the enzymatic activity to build and active model for our system which we can test by growing the two bacteria together in minimal media with restricted carbon sources.

Welcome to iGEM 2016!

Your team has been approved and you are ready to start the iGEM season!

Before you start:

Please read the following pages:

Styling your wiki

You may style this page as you like or you can simply leave the style as it is. You can easily keep the styling and edit the content of these default wiki pages with your project information and completely fulfill the requirement to document your project.

While you may not win Best Wiki with this styling, your team is still eligible for all other awards. This default wiki meets the requirements, it improves navigability and ease of use for visitors, and you should not feel it is necessary to style beyond what has been provided.

Wiki template information

We have created these wiki template pages to help you get started and to help you think about how your team will be evaluated. You can find a list of all the pages tied to awards here at the Pages for awards link. You must edit these pages to be evaluated for medals and awards, but ultimately the design, layout, style and all other elements of your team wiki is up to you!

Editing your wiki

On this page you can document your project, introduce your team members, document your progress and share your iGEM experience with the rest of the world!

Use WikiTools - Edit in the black menu bar to edit this page

Tips

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:

  • State your accomplishments! Tell people what you have achieved from the start.
  • Be clear about what you are doing and how you plan to do this.
  • You have a global audience! Consider the different backgrounds that your users come from.
  • Make sure information is easy to find; nothing should be more than 3 clicks away.
  • Avoid using very small fonts and low contrast colors; information should be easy to read.
  • 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 iGEM 2016 calendar
  • Have lots of fun!
Inspiration

You can also view other team wikis for inspiration! Here are some examples:

Uploading pictures and files

You can upload your pictures and files to the iGEM 2016 server. Remember to keep all your pictures and files within your team's namespace or at least include your team's name in the file name.
When you upload, set the "Destination Filename" to
T--YourOfficialTeamName--NameOfFile.jpg. (If you don't do this, someone else might upload a different file with the same "Destination Filename", and your file would be erased!)

UPLOAD FILES