Difference between revisions of "Help:Document Parts"
m |
m |
||
Line 56: | Line 56: | ||
=Documenting Parts= | =Documenting Parts= | ||
− | Adding your part to the Registry is a great first step, '''but there's still more to do!''' | + | [[Add_a_Part_to_the_Registry|Adding your part to the Registry]] is a great first step, '''but there's still more to do!''' |
Documenting and characterizing your part is vital to its continued use by Registry users. Users will have a clearer understanding of how your part works, and what to expect when using your part in their project. A well documented part offers a foundation for users to experiment and test your part, and build upon your documentation and characterization work. You will find that your well documented part will be used in new composite parts, new systems, and new team projects. | Documenting and characterizing your part is vital to its continued use by Registry users. Users will have a clearer understanding of how your part works, and what to expect when using your part in their project. A well documented part offers a foundation for users to experiment and test your part, and build upon your documentation and characterization work. You will find that your well documented part will be used in new composite parts, new systems, and new team projects. | ||
Line 90: | Line 90: | ||
==Characterization== | ==Characterization== | ||
− | The bulk of your documentation will likely be characterizing and measuring your part. | + | The bulk of your documentation will likely be '''characterizing and measuring your part.''' |
+ | |||
+ | |||
+ | '''Why is this important?''' | ||
+ | *It will show users that your part works (or doesn't work!) as expected | ||
+ | *Your part will be experimentally validated, and better understood for users | ||
+ | *Others can reproduce your results and build upon them | ||
+ | |||
There isn't any one way to measure or characterize your parts, and you will find that certain parts will need to be experimentally validated differently than others; an inducible promoter will be characterized and measured differently than a metal binding protein. If you're unsure how to get started, you may want to take a look at similar parts in the Registry. | There isn't any one way to measure or characterize your parts, and you will find that certain parts will need to be experimentally validated differently than others; an inducible promoter will be characterized and measured differently than a metal binding protein. If you're unsure how to get started, you may want to take a look at similar parts in the Registry. | ||
Line 96: | Line 103: | ||
<table class="helpTable"> | <table class="helpTable"> | ||
<tr> | <tr> | ||
− | <th style="width: | + | <th style="width: 150px;">Promoter</th> |
− | <th style="width: | + | <th style="width: 150px;">RBS</th> |
− | <th style="width: | + | <th style="width: 150px;">Coding Region</th> |
− | <th style="width: | + | <th style="width: 150px;">Terminator</th> |
− | <th style="width: | + | <th style="width: 150px;">Device</th> |
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 108: | Line 115: | ||
<td title="Terminator"><partinfo>BBa_K731721</partinfo></td> | <td title="Terminator"><partinfo>BBa_K731721</partinfo></td> | ||
<td title="Device"><partinfo>BBa_K863005</partinfo></td> | <td title="Device"><partinfo>BBa_K863005</partinfo></td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <td title="Promoter"></td> | ||
+ | <td title="RBS"></td> | ||
+ | <td title="Coding"></td> | ||
+ | <td title="Terminator"></td> | ||
+ | <td title="Device"></td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | + | '''However, there are elements that should be consistent across all of the characterization for your parts. Always:''' | |
− | However, there are elements that should be consistent across all of the characterization for your parts. | + | |
− | + | ||
− | + | ||
*Explain the aim/hypothesis you will be testing | *Explain the aim/hypothesis you will be testing | ||
− | *Detail the | + | *Detail the conditions/parameters of your experiment, and reference your methods |
*Represent your data as clearly as possible | *Represent your data as clearly as possible | ||
*Include your controls! | *Include your controls! | ||
Line 127: | Line 138: | ||
==References== | ==References== | ||
Be sure to include any literature references for your part. This includes references that you have used while documenting your part (be sure to cite properly), as well as any references that you think would be useful as additional reading for users. | Be sure to include any literature references for your part. This includes references that you have used while documenting your part (be sure to cite properly), as well as any references that you think would be useful as additional reading for users. | ||
+ | |||
+ | |||
+ | |||
+ | ==Design Notes== | ||
+ | On the part's Design Page, detail any design considerations you may have taken for the part. This includes mutations to remove restriction sites, codon optimization, etc. | ||
+ | |||
+ | |||
+ | |||
+ | ==Source== | ||
+ | On the part's Design Page, you should briefly state the organism of origin and the sample source for your part. It may have been contributed from another lab, you may have PCRed it from an organism, or you may have synthesized it. | ||
=Judging= | =Judging= | ||
+ | If you belong to an iGEM team participating in a current iGEM competition, then there are certain requirements that your project must meet. Generally, this entails [[DNA_Submission|submitting]] at least one part that meets the [[Help:Submission|submission requirements]]. | ||
+ | |||
+ | |||
+ | '''Parts must also be documented on the Registry, and Judges will be viewing part before and during the Jamboree.''' In regards to documenting your part, we've included a recommendation from the [http://2015.igem.org/Judging 2015 Judges] below: | ||
+ | <blockquote cite="http://2015.igem.org/Judging#important">The Registry will not be frozen this year. However, you should put up all your part information on the Registry by the time of the wiki freeze. We care about capturing all your part measurement and characterization information and iGEM teams are not the sole users of the Registry, so we do not freeze that site. However, if you have not added all your part measurement and characterization data by the time of the wiki freeze, the judges are not under any obligation to look at new information. | ||
+ | |||
+ | For example, if you wait until the Jamboree to put up your part documentation on the Registry, judges evaluating your team may not have time to see it. Judges do not have any obligation to look at part information on the Registry posted after the wiki freeze. Remember - it is up to your team to convince the judges that you have done your work!</blockquote> | ||
+ | |||
+ | |||
+ | There are specific criteria that must be met to be eligible for Medals (Bronze/Silver/Gold) and the Special Awards (Best Basic Part/Best Composite Part/Best Part Collection. Make sure to check the requirements for your competition year. We've provided information for iGEM 2015 below. | ||
+ | *[http://2015.igem.org/Requirements 2015 Requirements] | ||
+ | *[http://2015.igem.org/Judging#handbook 2015 Medal Criteria] | ||
+ | *[http://2015.igem.org/Judging#handbook 2015 Judging Handbook] | ||
+ | *[http://2015.igem.org/Judging/Rubric_categories#Newbasicpart 2015 Judging Rubric for Part Awards] |
Revision as of 22:29, 6 August 2015
- Registry Help Pages:
- TOC
- At-a-Glance
- FAQ
Add a Part to the Registry: Related Registry Help Pages
- Add a Basic Part - A tutorial on how to add a basic part
- Add a Composite Part - A tutorial on how to add a composite part
- Scars - Information on assembly scars, and how to specify them for a composite part
- Synthesis - Things to keep in mind if you're adding and documenting a part you've synthesized
- Assembly Compatibility - Make sure your part is compatible with an assembly standard
- Twins - Parts are twins if they have the same sequence
- Document Parts - Recommendations on how to document your parts
- Make a Contribution - Improve existing parts
Have questions on adding a part to the Registry? Send an email to hq (at) igem . org.
Adding Parts
Adding a part to the Registry requires minimal information:
Required | Comments |
---|---|
Sequence | Parts require an accurate sequence. A part's sequence can be edited though part tools >> edit sequence and features |
Short Description | The biological or technical short hand for the part's function. The short description can be edited through the information page |
Long Description | Description of your part, and its functions. The long description can be edited through the wiki, tools >> edit this page |
Documenting Parts
Adding your part to the Registry is a great first step, but there's still more to do!
Documenting and characterizing your part is vital to its continued use by Registry users. Users will have a clearer understanding of how your part works, and what to expect when using your part in their project. A well documented part offers a foundation for users to experiment and test your part, and build upon your documentation and characterization work. You will find that your well documented part will be used in new composite parts, new systems, and new team projects.
We've provided a few guidelines on how you may want to approach documenting your parts. The guidelines include examples from current Registry parts that are considered well documented.
Usage
Explain what you used the part for in your project, and what other uses it might serve. Take a look at how the authors of BBa_K863006, an E. coli laccase, addressed Usage.
In the last few years a lot of attention has been drawn to laccases due to their ability to oxidize both phenolic and nonphenolic lignin related compounds as well as highly recalcitrant environmental pollutants. This makes them very useful for applications concerning several biotechnological processes. This includes the detoxification of industrial effluents, for example from the paper and pulp, textile and petrochemical industries. Laccases are also valuable as a tool as a tool for medical diagnostics and as a bioremediation agent to clean up herbicides, pesticides and certain explosives in soil. Furthermore these enzymes are also used as catalysts for the manufacture of anti-cancer drugs and even as ingredients in cosmetics[1]. Their capacity to remove xenobiotic substances and produce polymeric products makes them a useful tool for bioremediation purposes. In our project laccases are used as cleaning agents for a water purification system.
Why is this important?
- Users understand why this part was important to your project
- Users can identify if the part may be useful for future projects
- Offers an opportunity to show how novel/innovative this part may be to the Registry and the synthetic biology community
Biology
You may be using your part differently than its biological purpose, so it is important to also detail the biological origin and purpose of your part. Take a look at how the authors of BBa_K863006, an E. coli laccase, addressed Biology.
Laccases are copper-containing polyphenol oxidase enzymes (EC 1.10.3.2) that can be found in many plants, insects, microorganisms and mainly in fungi. These enzymes fulfill several functions in different metabolic pathways. Laccases are able to oxidize a broad range of substrates due to the contained copper-cluster, by reducing oxygen to water. The active site of the enzyme includes a four-copper-ion-cluster, which can be distinguished by spectroscopic analyses. This cluster consists of one blue copper-ion (type 1), one type 2 and two type 3 copper-ions. Because of the blue copper-ion, the laccases belong to the big family of the blue copper proteins. This specific blue copper ion is essential for the enzyme mediated radical oxidation of the phenolic groups. In this reaction the electron from the oxidation is transferred to the other three copper ions. These ions form a trinuclearic cluster, which transfers electrons to the terminal electron acceptor oxygen. By receiving four electrons the molecular oxygen is finally reduced to water.
Why is this important?
- Shows the origin of this part
- It explains the biological context and overall mechanism of the part
Characterization
The bulk of your documentation will likely be characterizing and measuring your part.
Why is this important?
- It will show users that your part works (or doesn't work!) as expected
- Your part will be experimentally validated, and better understood for users
- Others can reproduce your results and build upon them
There isn't any one way to measure or characterize your parts, and you will find that certain parts will need to be experimentally validated differently than others; an inducible promoter will be characterized and measured differently than a metal binding protein. If you're unsure how to get started, you may want to take a look at similar parts in the Registry.
Promoter | RBS | Coding Region | Terminator | Device |
---|---|---|---|---|
BBa_K801020 | BBa_K1084104 | BBa_K1172501 | BBa_K731721 | BBa_K863005 |
However, there are elements that should be consistent across all of the characterization for your parts. Always:
- Explain the aim/hypothesis you will be testing
- Detail the conditions/parameters of your experiment, and reference your methods
- Represent your data as clearly as possible
- Include your controls!
- Label your images and graphs
- Summarize the results of your experiment
References
Be sure to include any literature references for your part. This includes references that you have used while documenting your part (be sure to cite properly), as well as any references that you think would be useful as additional reading for users.
Design Notes
On the part's Design Page, detail any design considerations you may have taken for the part. This includes mutations to remove restriction sites, codon optimization, etc.
Source
On the part's Design Page, you should briefly state the organism of origin and the sample source for your part. It may have been contributed from another lab, you may have PCRed it from an organism, or you may have synthesized it.
Judging
If you belong to an iGEM team participating in a current iGEM competition, then there are certain requirements that your project must meet. Generally, this entails submitting at least one part that meets the submission requirements.
Parts must also be documented on the Registry, and Judges will be viewing part before and during the Jamboree. In regards to documenting your part, we've included a recommendation from the [http://2015.igem.org/Judging 2015 Judges] below:
The Registry will not be frozen this year. However, you should put up all your part information on the Registry by the time of the wiki freeze. We care about capturing all your part measurement and characterization information and iGEM teams are not the sole users of the Registry, so we do not freeze that site. However, if you have not added all your part measurement and characterization data by the time of the wiki freeze, the judges are not under any obligation to look at new information. For example, if you wait until the Jamboree to put up your part documentation on the Registry, judges evaluating your team may not have time to see it. Judges do not have any obligation to look at part information on the Registry posted after the wiki freeze. Remember - it is up to your team to convince the judges that you have done your work!
There are specific criteria that must be met to be eligible for Medals (Bronze/Silver/Gold) and the Special Awards (Best Basic Part/Best Composite Part/Best Part Collection. Make sure to check the requirements for your competition year. We've provided information for iGEM 2015 below.
- [http://2015.igem.org/Requirements 2015 Requirements]
- [http://2015.igem.org/Judging#handbook 2015 Medal Criteria]
- [http://2015.igem.org/Judging#handbook 2015 Judging Handbook]
- [http://2015.igem.org/Judging/Rubric_categories#Newbasicpart 2015 Judging Rubric for Part Awards]