Difference between revisions of "Team:ICT-Mumbai/Parts"
Adityakamat (Talk | contribs) |
Adityakamat (Talk | contribs) |
||
| Line 159: | Line 159: | ||
| − | + | <div class="column full_size"> | |
<h1>Parts</h1> | <h1>Parts</h1> | ||
| Line 244: | Line 244: | ||
| − | </html | + | </html> |
Revision as of 03:09, 1 November 2017
Our project involves metabolism of ammonia by Escherichia coli to produce a blue-coloured dye, indigoidine. We had to choose between using a constitutive and an inducible promoter to drive expression of the genes that we wish to express in E. coli.
Expression from inducible promoters requires addition of an inducing molecule. However, as it would be cumbersome and tedious to add the inducer to the device that will house the engineered E. coli, and as it would also contribute to the cost, we decided to use a constitutive promoter to drive gene expression.
We reasoned that the constitutive promoter of choice should have the following two properties: (1) it should not be a very strong promoter, so as to not lead to any toxicity to the cell, and (2) it should be active in low-nutrient conditions. Based on these two considerations, the commonly used glycolytic promoters were ruled out as possible choices.
The ychH promoter has been described in literature to be active under low glucose conditions (Ref. 1). Moreover, it is not a very strong promoter, compared to those frequently employed to express recombinant proteins in E. coli (Ref. 2). Therefore, the ychH promoter became our promoter of choice.
Parts
Each team will make new parts during iGEM and will submit them to the Registry of Standard Biological Parts. The iGEM software provides an easy way to present the parts your team has created. The <groupparts> tag (see below) will generate a table with all of the parts that your team adds to your team sandbox.
Remember that the goal of proper part documentation is to describe and define a part, so that it can be used without needing to refer to the primary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper references to acknowledge previous authors and to provide for users who wish to know more.
Note
Note that parts must be documented on the Registry. This page serves to showcase the parts you have made. Future teams and other users and are much more likely to find parts by looking in the Registry than by looking at your team wiki.
Adding parts to the registry
You can add parts to the Registry at our Add a Part to the Registry link.
We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The sooner you put up your parts, the better you will remember all the details about your parts. Remember, you don't need to send us the DNA sample before you create an entry for a part on the Registry. (However, you do need to send us the DNA sample before the Jamboree. If you don't send us a DNA sample of a part, that part will not be eligible for awards and medal criteria.)
What information do I need to start putting my parts on the Registry?
The information needed to initially create a part on the Registry is:
- Part Name
- Part type
- Creator
- Sequence
- Short Description (60 characters on what the DNA does)
- Long Description (Longer description of what the DNA does)
- Design considerations
We encourage you to put up much more information as you gather it over the summer. If you have images, plots, characterization data and other information, please also put it up on the part page.
Inspiration
We have a created a collection of well documented parts that can help you get started.
You can also take a look at how other teams have documented their parts in their wiki:
Part Table
Please include a table of all the parts your team has made during your project on this page. Remember part characterization and measurement data must go on your team part pages on the Registry.
