Difference between revisions of "Part:BBa K128001:Experience"
m |
|||
| (4 intermediate revisions by one other user not shown) | |||
| Line 6: | Line 6: | ||
The Freiburg iGEM Team 2013 wanted to use an HA-tag for cloning it into all of our versatile mammalian fusion constructs being able to detect their expression via western blot. Therefore we searched in the parts registry and found the BBa_K128001 containing the RFC23 pre- and suffix. With this silver standard it is possible to construct in-frame-fusion parts. In contrast to the RFC25 biobrick (which is also suitable for functional part fusions) there is no start codon and stop codon automatically included in the prefix and suffix. To clone this HA-tag at the N-or C-terminal part of a protein it is necessary to introduce the missing start or stop codon, see Fig.1 and 2. As tags are often fused at the end (C- or N-terminal) of proteins, this HA-tag cannot easily cloned in a functional way. We always cloned the HA-tag N-terminal to the parts of our devices. In order to save time and effort, we improved the consisting HA-tag BBa_K128001. Therefore we designed a new HA-tag in the RFC25 standard but with an identical sequence of amino acids. This should also facilitate cloning for other iGEM teams, see Fig.3. | The Freiburg iGEM Team 2013 wanted to use an HA-tag for cloning it into all of our versatile mammalian fusion constructs being able to detect their expression via western blot. Therefore we searched in the parts registry and found the BBa_K128001 containing the RFC23 pre- and suffix. With this silver standard it is possible to construct in-frame-fusion parts. In contrast to the RFC25 biobrick (which is also suitable for functional part fusions) there is no start codon and stop codon automatically included in the prefix and suffix. To clone this HA-tag at the N-or C-terminal part of a protein it is necessary to introduce the missing start or stop codon, see Fig.1 and 2. As tags are often fused at the end (C- or N-terminal) of proteins, this HA-tag cannot easily cloned in a functional way. We always cloned the HA-tag N-terminal to the parts of our devices. In order to save time and effort, we improved the consisting HA-tag BBa_K128001. Therefore we designed a new HA-tag in the RFC25 standard but with an identical sequence of amino acids. This should also facilitate cloning for other iGEM teams, see Fig.3. | ||
| − | For more information about that improved HA, please take a look at | + | For more information about that improved HA, please take a look at [https://parts.igem.org/Part:BBa_K1150016 BBa_K1150016]. |
[[File:HA_alt_1_Freigem_2013.png|800px|]] | [[File:HA_alt_1_Freigem_2013.png|800px|]] | ||
| − | Fig.1: BBa_K128001 with RFC23 prefix and suffix. | + | '''Fig.1''': BBa_K128001 with RFC23 prefix and suffix. |
[[File:HA_neu_2_Freigem_2013.png|800px|]] | [[File:HA_neu_2_Freigem_2013.png|800px|]] | ||
| − | Fig.2: BBa_K1150016 with RFC25 prefix and suffix. | + | '''Fig.2''': BBa_K1150016 with RFC25 prefix and suffix. |
| − | [[File:HA neu 3 Freigem2013.png| | + | [[File:HA neu 3 Freigem2013.png|950px|]] |
| − | Fig.3: BBa_K1150016 theoretically fused C-terminal to a NLS with an automatic functional | + | '''Fig.3''': BBa_K1150016 theoretically fused C-terminal to a NLS with an automatic functional start codon in the prefix. |
<partinfo>BBa_K128001 AddReview number</partinfo> | <partinfo>BBa_K128001 AddReview number</partinfo> | ||
Latest revision as of 21:53, 4 October 2013
This experience page is provided so that any user may enter their experience using this part.
Please enter
how you used this part and how it worked out.
Improvement of BBa_K128001
The Freiburg iGEM Team 2013 wanted to use an HA-tag for cloning it into all of our versatile mammalian fusion constructs being able to detect their expression via western blot. Therefore we searched in the parts registry and found the BBa_K128001 containing the RFC23 pre- and suffix. With this silver standard it is possible to construct in-frame-fusion parts. In contrast to the RFC25 biobrick (which is also suitable for functional part fusions) there is no start codon and stop codon automatically included in the prefix and suffix. To clone this HA-tag at the N-or C-terminal part of a protein it is necessary to introduce the missing start or stop codon, see Fig.1 and 2. As tags are often fused at the end (C- or N-terminal) of proteins, this HA-tag cannot easily cloned in a functional way. We always cloned the HA-tag N-terminal to the parts of our devices. In order to save time and effort, we improved the consisting HA-tag BBa_K128001. Therefore we designed a new HA-tag in the RFC25 standard but with an identical sequence of amino acids. This should also facilitate cloning for other iGEM teams, see Fig.3.
For more information about that improved HA, please take a look at BBa_K1150016.
Fig.1: BBa_K128001 with RFC23 prefix and suffix.
Fig.2: BBa_K1150016 with RFC25 prefix and suffix.
Fig.3: BBa_K1150016 theoretically fused C-terminal to a NLS with an automatic functional start codon in the prefix.
No review score entered. Username
User Reviews
UNIQ1d9dc938204bc5b2-partinfo-00000001-QINU UNIQ1d9dc938204bc5b2-partinfo-00000002-QINU