Team:Heidelberg/Project/Capsid Shuffling/ViroBytes
From 2010.igem.org
(→Introduction) |
|||
Line 10: | Line 10: | ||
AAV serotypes 1,2,5,6,8 and 9 were selected as suitable candidates for fragmentation due to their exceptional individual properties. The analysis of Cap gene sequences revealed multiple homology regions which were then used for rational fragment formation. Total number of fragments per Cap gene is eight in our case and all fragments have similar length around ~250bp to assure similar behaviour in the ligation reaction. The Bytes are created and amplified by High-Fidelity PCR using Cap- and FragmentX-specific primers. These [https://2010.igem.org/Team:Heidelberg/Notebook/Material/Primer#ViroBytes_primers primers] contain flanking regions with recognition sequence for type II restriction enzyme Bsa1. Precise positioning in front of and behind the homology regions at the ends of each fragmetn ensures that the enzyme forms unique sticky ends with 4nt overhangs. This procedure allows the user to avoid arduous design of overhangs with incorporated uracils further used for USER<sup>TM</sup> digestion. Also for the purposes of shuffling, the homology regions need to be exploited in order to avoid frame shifts which cannot be easily accomplished using standard BioByte protocol. | AAV serotypes 1,2,5,6,8 and 9 were selected as suitable candidates for fragmentation due to their exceptional individual properties. The analysis of Cap gene sequences revealed multiple homology regions which were then used for rational fragment formation. Total number of fragments per Cap gene is eight in our case and all fragments have similar length around ~250bp to assure similar behaviour in the ligation reaction. The Bytes are created and amplified by High-Fidelity PCR using Cap- and FragmentX-specific primers. These [https://2010.igem.org/Team:Heidelberg/Notebook/Material/Primer#ViroBytes_primers primers] contain flanking regions with recognition sequence for type II restriction enzyme Bsa1. Precise positioning in front of and behind the homology regions at the ends of each fragmetn ensures that the enzyme forms unique sticky ends with 4nt overhangs. This procedure allows the user to avoid arduous design of overhangs with incorporated uracils further used for USER<sup>TM</sup> digestion. Also for the purposes of shuffling, the homology regions need to be exploited in order to avoid frame shifts which cannot be easily accomplished using standard BioByte protocol. | ||
+ | |||
==Important facts== | ==Important facts== | ||
- | + | Shuffling of several (six in our case) wild-type AAV serotypes unfortunately does not allow for standardization of the Virobyte fragments. We use type II restriction enzyme Bsa1 for creating the sticky ends instead. Incorporation of the recognition sequence of Bsa1 at both ends of the ViroBytes allows for higher specificity and thus prevents non-neighbouring fragments from ligating. The homology regions within which the Bsa1 enzyme cuts provide possibility for fragment shuffling without creating sequence frameshifts or deletions leading to nonviable chimeric isolates. | |
BsaI recognition and cutting sequence: | BsaI recognition and cutting sequence: | ||
Line 20: | Line 21: | ||
3'...CCAGAGNNNNN/...5' | 3'...CCAGAGNNNNN/...5' | ||
- | hence overhang: 5'-NNNN | + | hence the overhang created at each fragment ending: 5'-NNNN |
- | Homology | + | Homology regions employed in our Virobyte approach were selected as follows: |
- | between Anchor and Fragment1: | + | between Anchor and Fragment1 ("Start overhang"): |
5'...ATGG...3' | 5'...ATGG...3' | ||
Line 34: | Line 35: | ||
3'...CCTC...5' | 3'...CCTC...5' | ||
- | between Fragment2 and Fragment3 (bp 688-716): | + | between Fragment2 and Fragment3 (bp 688-716 ,AAV1): |
5'...GACA...3' | 5'...GACA...3' | ||
3'...CTGT...5' | 3'...CTGT...5' | ||
- | between Fragment3 and Fragment4 (bp 1013-1016): | + | between Fragment3 and Fragment4 (bp 1013-1016 ,AAV1): |
5'...AACC...3' | 5'...AACC...3' | ||
3'...TTGG...5' | 3'...TTGG...5' | ||
- | between Fragment4 and Fragment5 (bp 1282-1285): | + | between Fragment4 and Fragment5 (bp 1282-1285 ,AAV1): |
5'...CAGC...3' | 5'...CAGC...3' | ||
3'...GTCG...5' | 3'...GTCG...5' | ||
- | between Fragment5 and Fragment6 (bp 1444-1447): | + | between Fragment5 and Fragment6 (bp 1444-1447 ,AAV1): |
5'...AACT...3' | 5'...AACT...3' | ||
3'...TTGA...5' | 3'...TTGA...5' | ||
- | between Fragment6 and Fragment7 (bp 1740-1743): | + | between Fragment6 and Fragment7 (bp 1740-1743 ,AAV1): |
5'...GTGG...3' | 5'...GTGG...3' | ||
3'...CACC...5' | 3'...CACC...5' | ||
- | between Fragment7 and Fragment8 (bp 2040-2043): | + | between Fragment7 and Fragment8 (bp 2040-2043 ,AAV1): |
5'...TCAC...3' | 5'...TCAC...3' | ||
3'...AGTG...5' | 3'...AGTG...5' | ||
+ | |||
==ViroByte design== | ==ViroByte design== |
Revision as of 00:47, 28 October 2010
|
|
|||