Chloroplast (Talk | contribs) |
Chloroplast (Talk | contribs) |
||
Line 1: | Line 1: | ||
− | {{NUS_Singapore}} | + | {{Team:NUS_Singapore/new}} |
<html> | <html> | ||
Revision as of 09:08, 18 September 2016
Template:Team:NUS Singapore/new
Welcome to NUS_Singapore iGEM 2016 Page!
Conventional drug delivery systems are plagued by problems such as non-specific targeting and low bioavailability. Bacterial-based drug delivery systems have gained much interest due to their ability to overcome the issue of non-specific delivery of drugs. This is achieved by engineering bacteria to sense and respond to specific stimuli present in the microenvironment of these pathogenic cells.
In this project, we propose the development of a dual-sensor bacteria which can only survive, and release therapeutics, within the targeted part of the human body (i.e., spatially specific). As our proof of concept, we will be engineering the Escherichia coli bacterium to target cancer tumors with high environmental lactate — see Warburg effect.
To ensure that the bacterium will only affect cancer cells, the bacterium is engineered to detect, and adhere to a cancer specific surface marker. Upon detection, a quorum sensing system and the production of invasin and listeriolysin O is triggered. The invasin and listeriolysin O then allows the bacteria to deliver its payload directly into the cytoplasm of the cancer cell. Since the production of invasin and listeriolysin O cannot occur in the absence of the said marker, this delivery system will only target cancer cells, concentrating drug payload at the intended site.
Our team has been working on cloning our desired biobrick parts and modelling our gene circuit. We hope to be able to characterise and optimise our parts, and demonstrate a functional spatially-specific drug delivery system, as well as complement our wet lab efforts with our model.
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!)