</div></div></div></body> <!--These are the closing tags for div id="mainContainer" and div id="contentContainer". The corresponding opening tags appear in the template that is {{included}} at the top of this page.-->
</div></div></div></body> <!--These are the closing tags for div id="mainContainer" and div id="contentContainer". The corresponding opening tags appear in the template that is {{included}} at the top of this page.-->
+
<p style="margin-bottom:0;">
<!-- Scirpt for beautiful scrolling inside the page: smooth transitions and we show in what section the reader is. -->
<!-- Scirpt for beautiful scrolling inside the page: smooth transitions and we show in what section the reader is. -->
Our Propane 1 includes 4 of the 10 required genes to produce propane in E. coli. The plasmid has been assembled from IDT's gBlocks with NEBuilder assembly, similar to Gibson Assembly.
Validation:
Fusable GFP
We built a GFP biobrick which can be fused to any protein's aminoterminal end with the standard BioBrick assembly enzymes. We have added an extra nucleotide prior to the brick's suffix to maintain the reading frame after fusion, which is typically lost when the restriction enzyme assembly is used.
Validation: Our GFP brick has been fully sequenced, and the sequencing results were as expected. We have also been able to express the GFP after fusing it with an amphiphilic brick. This construct functioned under K608003, a strong constitutive promoter and a medium RBS. HS Slovenia Team also helped us validate this brick. They gained positive results of their construct with the GFP through colony PCR and analytical restrictions, but were unable to detect the fluerescence under UV light or functionality of the fused protein.
Amphiphilic
We submitted a sole amphiphilic brick, containing only the coding region of the ampihphilic protein. This brick can be used to produce intracellular micelles or vesicles under any chosen expression system.
Validation: Our amphiphilic brick's sequencing results were unclear, as the brick is mainly built of short repeats. Microscope pictures!
Part Documentation
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.
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.
