|
|
| (8 intermediate revisions not shown) |
| Line 1: |
Line 1: |
| - | <!-- *** What falls between these lines is the Alert Box! You can remove it from your pages once you have read and understood the alert *** --> | + | {{CSU_Template_1_top}} |
| | + | <html xmlns="http://www.w3.org/1999/xhtml"> |
| | | | |
| - | <html> | + | <!--START PAGE CONTENT--> |
| - | <div id="box" style="width: 700px; margin-left: 137px; padding: 5px; border: 3px solid #000; background-color: #fe2b33;">
| + | |
| - | <div id="template" style="text-align: center; font-weight: bold; font-size: large; color: #f6f6f6; padding: 5px;">
| + | |
| - | This is a template page. READ THESE INSTRUCTIONS.
| + | |
| - | </div>
| + | |
| - | <div id="instructions" style="text-align: center; font-weight: normal; font-size: small; color: #f6f6f6; padding: 5px;">
| + | |
| - | You are provided with this team page template with which to start the iGEM season. You may choose to personalize it to fit your team but keep the same "look." Or you may choose to take your team wiki to a different level and design your own wiki. You can find some examples <a href="https://2008.igem.org/Help:Template/Examples">HERE</a>.
| + | |
| - | </div>
| + | |
| - | <div id="warning" style="text-align: center; font-weight: bold; font-size: small; color: #f6f6f6; padding: 5px;">
| + | |
| - | You <strong>MUST</strong> have all of the pages listed in the menu below with the names specified. PLEASE keep all of your pages within your teams namespace.
| + | |
| - | </div>
| + | |
| - | </div>
| + | |
| - | </html>
| + | |
| | | | |
| - | <!-- *** End of the alert box *** -->
| |
| | | | |
| - | {| style="color:#1b2c8a;background-color:#0c6;" cellpadding="3" cellspacing="1" border="1" bordercolor="#fff" width="62%" align="center"
| |
| - | !align="center"|[[Team:CSU_Fort_Collins|Home]]
| |
| - | !align="center"|[[Team:CSU_Fort_Collins/Team|Team]]
| |
| - | !align="center"|[https://igem.org/Team.cgi?year=2013&team_name=CSU_Fort_Collins Official Team Profile]
| |
| - | !align="center"|[[Team:CSU_Fort_Collins/Project|Project]]
| |
| - | !align="center"|[[Team:CSU_Fort_Collins/Parts|Parts Submitted to the Registry]]
| |
| - | !align="center"|[[Team:CSU_Fort_Collins/Modeling|Modeling]]
| |
| - | !align="center"|[[Team:CSU_Fort_Collins/Notebook|Notebook]]
| |
| - | !align="center"|[[Team:CSU_Fort_Collins/Safety|Safety]]
| |
| - | !align="center"|[[Team:CSU_Fort_Collins/Attributions|Attributions]]
| |
| - | |}
| |
| | | | |
| | + | <h1> Parts Submitted to the Registry</h1> |
| | | | |
| | + | <p>Our plan was to design our bio-bricks using Gibson Assembly and gBlocks. However, we were unable to get the Gibson Assemblies to work and we were unable to produce our parts. One big hurdle in designing our parts was that some of the sequences for the proteins we wanted to use had several restriction enzyme sites that were not compatible with the bio-brick standards. This is why we chose Gibson Assembly over using Standard Assembly. |
| | + | It was suggested by staff members at the iGEM headquarters that we prompt forthcoming iGEM teams of the potential risks of relying on Gibson Assembly alone. |
| | + | </p> |
| | | | |
| - | An important aspect of the iGEM competition is the use and creation of standard biological parts. Each team will make new parts during iGEM and will place them in the [http://partsregistry.org Registry of Standard Biological Parts]. The iGEM software provides an easy way to present the parts your team has created . The "groupparts" tag will generate a table with all of the parts that your team adds to your team sandbox. Note that if you want to document a part you need to document it on the [http://partsregistry.org Registry], not on your team wiki.
| |
| | | | |
| - | Remember that the goal of proper part documentation is to describe and define a part such that it can be used without a need to refer to the primary literature. The next iGEM team 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.
| + | </html> |
| - | | + | {{CSU_Template_1_bottom}} |
| - | | + | |
| - | <groupparts>iGEM013 CSU_Fort_Collins</groupparts>
| + | |
Parts Submitted to the Registry
Our plan was to design our bio-bricks using Gibson Assembly and gBlocks. However, we were unable to get the Gibson Assemblies to work and we were unable to produce our parts. One big hurdle in designing our parts was that some of the sequences for the proteins we wanted to use had several restriction enzyme sites that were not compatible with the bio-brick standards. This is why we chose Gibson Assembly over using Standard Assembly.
It was suggested by staff members at the iGEM headquarters that we prompt forthcoming iGEM teams of the potential risks of relying on Gibson Assembly alone.
"
