Team:Slovenia/Linker-extension standard.html
From 2009.igem.org
(3 intermediate revisions not shown) | |||
Line 2: | Line 2: | ||
Content= | Content= | ||
__NOTOC__ | __NOTOC__ | ||
+ | <html><left> | ||
+ | <font size="3" color="#009ee0"><b>Development of the BioBRICKS</b></font> | ||
+ | </left></html> | ||
==New developed linker-extension standard== | ==New developed linker-extension standard== | ||
<br> | <br> | ||
Line 7: | Line 10: | ||
<br> | <br> | ||
<br> | <br> | ||
- | Two variations of linker-extension standard were designed. Both variations contain 5' and 3' cloning restriction sites EcoRI, PstI, NotI, XbaI and SpeI characteristic for BBa standard (Figure 1). Additionally, core restriction sites NgoMIV, AgeI, XmaI, BspEI are added. These restriction sites are used for linker extension and their positions differ among two variations of linker-extension standard. The position and the usage of these core restriction sites determine amino acid residues incorporated in the linker between protein domains (Figure 2). | + | Two variations of linker-extension standard were designed. Both variations contain 5' and 3' cloning restriction sites EcoRI, PstI, NotI, XbaI and SpeI characteristic for BBa standard (''Figure 1''). Additionally, core restriction sites NgoMIV, AgeI, XmaI, BspEI are added. These restriction sites are used for linker extension and their positions differ among two variations of linker-extension standard. The position and the usage of these core restriction sites determine amino acid residues incorporated in the linker between protein domains (''Figure 2''). |
<br> | <br> | ||
<br> | <br> | ||
Line 18: | Line 21: | ||
<br> | <br> | ||
<br> | <br> | ||
- | Figure 1: Schematic presentation of basic elements of two linker-extension standards also named BB-NIC-II and BB-NIC-III vectors. | + | <b>Figure 1:</b> Schematic presentation of basic elements of two linker-extension standards also named BB-NIC-II and BB-NIC-III vectors. |
</center> | </center> | ||
</html> | </html> | ||
Line 26: | Line 29: | ||
<center> <img src="https://static.igem.org/mediawiki/2009/8/8c/Linker_ext_Figure_2.gif" align="center" width="600" height="450" border="0" /> | <center> <img src="https://static.igem.org/mediawiki/2009/8/8c/Linker_ext_Figure_2.gif" align="center" width="600" height="450" border="0" /> | ||
<br> | <br> | ||
- | Figure 2: Schematic presentation of linker extension using both variations of linker-extension standards. A basic BRICK is re-cloned into the linker-extension standard using suitable restriction sites to obtain either Thr-Gly, Ser-Gly or Pro-Gly extensions. | + | <b>Figure 2</b>: Schematic presentation of linker extension using both variations of linker-extension standards. A basic BRICK is re-cloned into the linker-extension standard using suitable restriction sites to obtain either Thr-Gly, Ser-Gly or Pro-Gly extensions. |
</center> | </center> | ||
</html> | </html> | ||
Line 39: | Line 42: | ||
<center> <img src="https://static.igem.org/mediawiki/2009/f/f8/Linker_ext_Figure_3.gif" align="center" width="600" height="450" border="0" /> | <center> <img src="https://static.igem.org/mediawiki/2009/f/f8/Linker_ext_Figure_3.gif" align="center" width="600" height="450" border="0" /> | ||
<br> | <br> | ||
- | Figure 3: A schematic presentation of repetitive linker extension. Similar strategy could be used to incorporate other linker amino acids. With each round of cloning the insert gains two additional amino acids. Type of linker amino acids is defined with way of cloning (restrictions of vectors). | + | <b>Figure 3</b>: A schematic presentation of repetitive linker extension. Similar strategy could be used to incorporate other linker amino acids. With each round of cloning the insert gains two additional amino acids. Type of linker amino acids is defined with way of cloning (restrictions of vectors). |
</center> | </center> | ||
</html> | </html> | ||
Line 52: | Line 55: | ||
<center> <img src="https://static.igem.org/mediawiki/2009/4/4e/Linker_ext_Figure_4.gif" align="center" width="600" height="450" border="0" /> | <center> <img src="https://static.igem.org/mediawiki/2009/4/4e/Linker_ext_Figure_4.gif" align="center" width="600" height="450" border="0" /> | ||
<br> | <br> | ||
- | Figure 4: Schematic presentation of three different cloning strategies in multiple-cloning site of BB-NIC-II vector. Note: Each type of cloning leaves different extension of amino acids that could be used to extend scar/linker between parts after in-frame parts assembly. | + | <b>Figure 4</b>: Schematic presentation of three different cloning strategies in multiple-cloning site of BB-NIC-II vector. Note: Each type of cloning leaves different extension of amino acids that could be used to extend scar/linker between parts after in-frame parts assembly. |
</center> | </center> | ||
</html> | </html> | ||
Line 60: | Line 63: | ||
<center> <img src="https://static.igem.org/mediawiki/2009/8/84/Linker_ext_Figure_5.gif" align="center" width="600" height="450" border="0" /> | <center> <img src="https://static.igem.org/mediawiki/2009/8/84/Linker_ext_Figure_5.gif" align="center" width="600" height="450" border="0" /> | ||
<br> | <br> | ||
- | Figure 5: Schematic presentation of four different cloning strategies in multiple-cloning site of BB-NIC-III vector. Note: Each type of cloning leaves different extension of amino acids which could be used to extend scar/linker between parts after in-frame parts assembly. | + | <b>Figure 5:</b> Schematic presentation of four different cloning strategies in multiple-cloning site of BB-NIC-III vector. Note: Each type of cloning leaves different extension of amino acids which could be used to extend scar/linker between parts after in-frame parts assembly. |
</center> | </center> | ||
</html> | </html> | ||
Line 66: | Line 69: | ||
==Assembly strategy== | ==Assembly strategy== | ||
- | Assembly strategy joining two parts/bricks is depicted in Figure 6. A detailed description is described also under BBF RFC37 | + | Assembly strategy joining two parts/bricks is depicted in Figure 6. A detailed description is described also under [http://dspace.mit.edu/bitstream/handle/1721.1/46705/BBFRFC37.pdf?sequence=1 BBF RFC37]. |
<br> | <br> | ||
<br> | <br> | ||
Line 72: | Line 75: | ||
<center> <img src="https://static.igem.org/mediawiki/2009/c/ca/Linker_ext_Figure_6.gif" align="center" width="600" height="450" border="0" /> | <center> <img src="https://static.igem.org/mediawiki/2009/c/ca/Linker_ext_Figure_6.gif" align="center" width="600" height="450" border="0" /> | ||
<br> | <br> | ||
- | Figure 6: A schematic presentation of parts assembly. Each of two BRICKs is cut with suitable restriction enzymes and three point ligation into vector (with ccdB domain) cut with EcoRI and PstI is performed. Note: Also the standard BBa assembly strategy could be used. | + | <b>Figure 6</b>: A schematic presentation of parts assembly. Each of two BRICKs is cut with suitable restriction enzymes and three point ligation into vector (with ccdB domain) cut with EcoRI and PstI is performed. Note: Also the standard BBa assembly strategy could be used. |
</center> | </center> | ||
</html> | </html> | ||
Line 78: | Line 81: | ||
==Compatibility with other BBa standards== | ==Compatibility with other BBa standards== | ||
- | The new linker-extension standard is fully compatible with BBa and other BBa compatible standards. Each part suited for cloning into standard BioBrick vector could be cloned also into BB-NIC vectors. The part suitable for standard Biobrick vector could be cloned into BB-NIC vectors into XbaI, SpeI restriction sites with some limitations. No linker extension strategy is applicable for those parts. Transfer of parts from linker-extension standard to BBa vector could be achieved in two steps (Figure 7). | + | The new linker-extension standard is fully compatible with BBa and other BBa compatible standards. Each part suited for cloning into standard BioBrick vector could be cloned also into BB-NIC vectors. The part suitable for standard Biobrick vector could be cloned into BB-NIC vectors into XbaI, SpeI restriction sites with some limitations. No linker extension strategy is applicable for those parts. Transfer of parts from linker-extension standard to BBa vector could be achieved in two steps (''Figure 7''). |
<br> | <br> | ||
<br> | <br> | ||
Line 84: | Line 87: | ||
<center> <img src="https://static.igem.org/mediawiki/2009/1/18/Linker_ext_Figure_7.gif" align="center" width="600" height="450" border="0" /> | <center> <img src="https://static.igem.org/mediawiki/2009/1/18/Linker_ext_Figure_7.gif" align="center" width="600" height="450" border="0" /> | ||
<br> | <br> | ||
- | Figure 7: A schematic presentation of part transfer from BB-NIC into BBa and alike vectors. Two steps of cloning are required for directional cloning. Step 1: Ligation of part from BB-NIC into BBa both cut with XbaI/PstI. Step 2: Ligation of part from intermediate into BBa both cut with EcoRI/SpeI. | + | <b>Figure 7</b>: A schematic presentation of part transfer from BB-NIC into BBa and alike vectors. Two steps of cloning are required for directional cloning. Step 1: Ligation of part from BB-NIC into BBa both cut with XbaI/PstI. Step 2: Ligation of part from intermediate into BBa both cut with EcoRI/SpeI. |
</center> | </center> | ||
</html> | </html> | ||
<br> | <br> | ||
}} | }} |
Latest revision as of 02:42, 22 October 2009
|
New developed linker-extension standard
Figure 1: Schematic presentation of basic elements of two linker-extension standards also named BB-NIC-II and BB-NIC-III vectors. Figure 2: Schematic presentation of linker extension using both variations of linker-extension standards. A basic BRICK is re-cloned into the linker-extension standard using suitable restriction sites to obtain either Thr-Gly, Ser-Gly or Pro-Gly extensions. Linker extension
Figure 3: A schematic presentation of repetitive linker extension. Similar strategy could be used to incorporate other linker amino acids. With each round of cloning the insert gains two additional amino acids. Type of linker amino acids is defined with way of cloning (restrictions of vectors).
Detailed cloning instructionsDetailed cloning instruction using the linker-extension standard A or the linker-extension standard B, BioBrick-NIC-III, are described in Figure 4 and Figure 5.
Figure 4: Schematic presentation of three different cloning strategies in multiple-cloning site of BB-NIC-II vector. Note: Each type of cloning leaves different extension of amino acids that could be used to extend scar/linker between parts after in-frame parts assembly.
Figure 5: Schematic presentation of four different cloning strategies in multiple-cloning site of BB-NIC-III vector. Note: Each type of cloning leaves different extension of amino acids which could be used to extend scar/linker between parts after in-frame parts assembly. Assembly strategyAssembly strategy joining two parts/bricks is depicted in Figure 6. A detailed description is described also under [http://dspace.mit.edu/bitstream/handle/1721.1/46705/BBFRFC37.pdf?sequence=1 BBF RFC37].
Figure 6: A schematic presentation of parts assembly. Each of two BRICKs is cut with suitable restriction enzymes and three point ligation into vector (with ccdB domain) cut with EcoRI and PstI is performed. Note: Also the standard BBa assembly strategy could be used. Compatibility with other BBa standardsThe new linker-extension standard is fully compatible with BBa and other BBa compatible standards. Each part suited for cloning into standard BioBrick vector could be cloned also into BB-NIC vectors. The part suitable for standard Biobrick vector could be cloned into BB-NIC vectors into XbaI, SpeI restriction sites with some limitations. No linker extension strategy is applicable for those parts. Transfer of parts from linker-extension standard to BBa vector could be achieved in two steps (Figure 7).
Figure 7: A schematic presentation of part transfer from BB-NIC into BBa and alike vectors. Two steps of cloning are required for directional cloning. Step 1: Ligation of part from BB-NIC into BBa both cut with XbaI/PstI. Step 2: Ligation of part from intermediate into BBa both cut with EcoRI/SpeI. |