Difference between revisions of "Team:MIT/Parts"
| Line 166: | Line 166: | ||
<td> pEXPR TRE - TALER14</td> | <td> pEXPR TRE - TALER14</td> | ||
<td> <a href = "http://parts.igem.org/Part:BBa_K2100037">BBa_K2100037</a></td> | <td> <a href = "http://parts.igem.org/Part:BBa_K2100037">BBa_K2100037</a></td> | ||
| + | </tr> | ||
| + | |||
| + | <tr> | ||
| + | <td> pEXPR TRE - TALER21</td> | ||
| + | <td> <a href = "http://parts.igem.org/Part:BBa_K2100038">BBa_K2100038</a></td> | ||
</tr> | </tr> | ||
Revision as of 23:27, 17 October 2016
Parts
| Part Name | Part Number |
|---|---|
| pENTR hEF1a | BBa_K2100003 |
| pENTR pTRE | BBa_K2100004 |
| pENTR pERE3 | BBa_K2100000 |
| pENTR pERE5 | BBa_K2100001 |
| pENTR pERE6 | BBa_K2100002 |
| pENTR pPRE3 | BBa_K2100008 |
| pENTR pPRE4 | BBa_K2100009 |
| pENTR pHybrid | BBa_K2100010 |
| pENTR pEGSH | BBa_K2100021 |
| pENTR pBM3R1 | BBa_K2100022 |
| pENTR pTALER21 | BBa_K2100023 |
| pENTR pTALER14 | BBa_K2100024 |
| pENTR eYFP | BBa_K2100005 |
| pENTR mKate | BBa_K2100006 |
| pENTR tagBFP | BBa_K2100007 |
| pENTR mCherry | BBa_K2100014 |
| pENTR TALER14 | BBa_K2100016 |
| pENTR TALER21 | BBa_K2100017 |
| pENTR BM3R1 | BBa_K2100018 |
| pENTR TP901 | BBa_K2100019 |
| pENTR GAL4 - VP16 | BBa_K2100020 |
| pENTR rtTA | BBa_K2100022 |
| pEXPR hEF1a-eYFP | BBa_K2100011 |
| pEXPR hEF1a-mKate | BBa_K2100012 |
| pEXPR hEF1a-tagBFP | BBa_K2100013 |
| pDEST mCherry GG | BBa_K2100015 |
| pEXPR TRE - BM3R1 | BBa_K2100036 |
| pEXPR TRE - TALER14 | BBa_K2100037 |
| pEXPR TRE - TALER21 | BBa_K2100038 |
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:
