(Prototype team page) |
|||
Line 1: | Line 1: | ||
− | |||
− | |||
− | + | {{UCL/BootstrapCSS}} | |
− | + | {{UCL/Style}} | |
− | + | ||
− | + | ||
− | + | ||
− | < | + | <html lang="en"> |
− | + | <head> | |
− | </ | + | <meta charset="UTF-8"> |
+ | <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0"> | ||
+ | <meta http-equiv="X-UA-Compatible" content="ie=edge"> | ||
+ | <title>UCL SETA - Part Design</title> | ||
+ | <link rel="icon" href="https://static.igem.org/mediawiki/2018/7/73/T--UCL--Logo2.png"> | ||
+ | |||
+ | </head> | ||
− | </ | + | <script type="text/javascript" src="https://2018.igem.org/Template:UCL/BootstrapJS?action=raw&ctype=text/javascript"></script> |
+ | <script type="text/javascript" src="https://2018.igem.org/Template:UCL/JQuery?action=raw&ctype=text/javascript"></script> | ||
+ | <script type="text/javascript" src="https://2018.igem.org/Template:UCL/WowJS?action=raw&ctype=text/javascript"></script> | ||
+ | <script> | ||
+ | $(document).ready(function(){ | ||
+ | $("a").on('click', function(event) { | ||
+ | if (this.hash !== "") { | ||
+ | event.preventDefault(); | ||
+ | var hash = this.hash; | ||
+ | $('html, body').animate({ | ||
+ | scrollTop: $(hash).offset().top - 100 | ||
+ | }, 1500, function(){ | ||
+ | window.location.hash = hash; | ||
+ | }); | ||
+ | } | ||
+ | }); | ||
+ | }); | ||
+ | </script> | ||
+ | <script> | ||
+ | new WOW().init(); | ||
+ | </script> | ||
+ | |||
+ | <body> | ||
+ | <div class="background_img_igem"> | ||
+ | <div class="navbarzindex"> | ||
+ | <div class="navbar-brand_igem"><a href="https://2018.igem.org/Team:UCL"> | ||
+ | <img class="img-logo_igem" src="https://static.igem.org/mediawiki/2018/7/73/T--UCL--Logo2.png" ></a> | ||
+ | </div> | ||
+ | |||
+ | <div class="topnav_igem" id="myTopnav_igem"> | ||
+ | <div class="floatright_igem"> | ||
+ | <a href="javascript:void(0);" style="font-size:21px;" class="icon_igem" onclick="myFunction()">☰</a> | ||
+ | <div class="dropdown_igem"> | ||
+ | <button class="dropbtn_igem"onclick="People()">People | ||
+ | |||
+ | </button> | ||
+ | <div class="dropdown-content_igem"id="dropdownpeople_igem"> | ||
+ | <a href="https://2018.igem.org/Team:UCL/Team">Team</a> | ||
+ | <a href="https://2018.igem.org/Team:UCL/Attributions">Attributions</a> | ||
+ | <a href="https://2018.igem.org/Team:UCL/Attributions#Sponsors">Sponsors</a> | ||
+ | </div> | ||
+ | </div> | ||
+ | <div class="dropdown_igem"> | ||
+ | <button class="dropbtn_igem"onclick="Project()">Project | ||
+ | |||
+ | </button> | ||
+ | <div class="dropdown-content_igem"id="dropdownproject_igem"> | ||
+ | <a href="https://2018.igem.org/Team:UCL/Description">Description</a> | ||
+ | <a href="https://2018.igem.org/Team:UCL/Results">Results</a> | ||
+ | <a href="https://2018.igem.org/Team:UCL/Demonstrate">Demonstrate</a> | ||
+ | <a href="https://2018.igem.org/Team:UCL/InterLab">InterLab</a> | ||
+ | <a href="https://2018.igem.org/Team:UCL/Safety">Safety</a> | ||
+ | </div> | ||
+ | </div> | ||
+ | <div class="dropdown_igem"> | ||
+ | <button class="dropbtn_igem"onclick="Parts()">Parts | ||
+ | |||
+ | </button> | ||
+ | <div class="dropdown-content_igem"id="dropdownparts_igem"> | ||
+ | <a href="https://2018.igem.org/Team:UCL/Design">Part Design</a> | ||
+ | <a href="https://2018.igem.org/Team:UCL/Parts">Parts</a> | ||
+ | <a href="https://2018.igem.org/Team:UCL/Improve">Improved Part</a> | ||
+ | </div> | ||
+ | </div> | ||
+ | <div class="dropdown_igem"> | ||
+ | <button class="dropbtn_igem"onclick="Modelling()">Modelling | ||
+ | |||
+ | </button> | ||
+ | <div class="dropdown-content_igem"id="dropdownmodelling_igem"> | ||
+ | <a href="https://2018.igem.org/Team:UCL/Model">Modelling</a> | ||
+ | <a href="https://2018.igem.org/Team:UCL/Model#Intein">Intein</a> | ||
+ | <a href="https://2018.igem.org/Team:UCL/Model#Intein_Polymerisation">Intein Polymerisation</a> | ||
+ | <a href="https://2018.igem.org/Team:UCL/Model#LAMMPS">LAMMPS</a> | ||
+ | <a href="https://2018.igem.org/Team:UCL/Model#Scale_Up">Scale Up</a> | ||
+ | </div> | ||
+ | </div> | ||
+ | <div class="dropdown_igem"> | ||
+ | <button class="dropbtn_igem"onclick="Humanpractices()">Human Practices | ||
+ | |||
+ | </button> | ||
+ | <div class="dropdown-content_igem"id"dropdownhumanpractices_igem"> | ||
+ | <a href="https://2018.igem.org/Team:UCL/Human_Practices">Human Practices</a> | ||
+ | <a href="https://2018.igem.org/Team:UCL/Public_Engagement">Public Engagement</a> | ||
+ | <a href="https://2018.igem.org/Team:UCL/Collaborations">Collaborations</a> | ||
+ | </div> | ||
+ | </div> | ||
+ | <div class="dropdown_igem"> | ||
+ | <button class="dropbtn_igem"onclick="Notebook()">Notebook | ||
+ | |||
+ | </button> | ||
+ | <div class="dropdown-content_igem"id="dropdownnotebook_igem"> | ||
+ | <a href="https://2018.igem.org/Team:UCL/Notebook">Notebook</a> | ||
+ | <a href="https://2018.igem.org/Team:UCL/Achievements">Achievements</a> | ||
+ | <a href="https://2018.igem.org/Team:UCL/Experiments">Experiments</a> | ||
+ | </div> | ||
+ | </div> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</div> | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | |||
+ | <script> | ||
+ | $(window).on('scroll',function(){ | ||
+ | if($(window).scrollTop()){ | ||
+ | $('.navbarzindex').addClass('black'); | ||
+ | } | ||
+ | else { | ||
+ | $('.navbarzindex').removeClass('black'); | ||
+ | } | ||
+ | }) | ||
+ | </script> | ||
+ | <script> | ||
+ | function myFunction() { | ||
+ | var x = document.getElementById("myTopnav_igem"); | ||
+ | if (x.className === "topnav_igem") { | ||
+ | x.className += " responsive"; | ||
+ | } else { | ||
+ | x.className = "topnav_igem"; | ||
+ | } | ||
+ | } | ||
+ | </script> | ||
+ | |||
+ | <script> | ||
+ | (function(){ | ||
+ | var dropDownClass = 'dropdown-content_igem'; | ||
+ | var showClass = 'show_igem'; | ||
+ | var dropDowns = document.getElementsByClassName('dropdown_igem'); | ||
+ | |||
+ | var open = function(e){ | ||
+ | var openDropDown = e.target.nextElementSibling; | ||
+ | var dropdowns = document.getElementsByClassName(dropDownClass); | ||
+ | |||
+ | openDropDown.classList.toggle(showClass); | ||
+ | |||
+ | var closeDropDown = function(event) { | ||
+ | if (event.target === e.target) { | ||
+ | return; | ||
+ | } | ||
+ | if (openDropDown.classList.contains(showClass)) { | ||
+ | openDropDown.classList.remove(showClass); | ||
+ | } | ||
+ | window.removeEventListener('click', closeDropDown); | ||
+ | }; | ||
+ | window.addEventListener('click', closeDropDown); | ||
+ | } | ||
+ | |||
+ | for(var i = 0; i < dropDowns.length; i++){ | ||
+ | dropDowns[i].children[0].addEventListener('click', open); | ||
+ | } | ||
+ | }()); | ||
+ | </script> | ||
+ | |||
+ | |||
+ | <script type="text/javascript" src="https://2018.igem.org/Template:UCL/ScrollToFixed?action=raw&ctype=text/javascript"></script> | ||
+ | |||
+ | <script> | ||
+ | $(document).ready(function() { | ||
+ | $('#sidenav').scrollToFixed({ marginTop: 250 }); | ||
+ | }); | ||
+ | </script> | ||
+ | |||
+ | <!--BODY==================================================================== --> | ||
+ | <body> | ||
+ | <div class="container container_igem"> | ||
+ | <div class="container container_igem"> | ||
+ | <img class="wow fadeInUp subpage_img_igem" src="https://static.igem.org/mediawiki/2018/9/9e/T--UCL--part_design2.svg" data-wow-duration="2s" data-wow-delay="0.1s"/> | ||
+ | <div class="h1_igem_subpage">Part Design</div> | ||
+ | </div> | ||
+ | |||
+ | <div class="container container_igem"> | ||
+ | <div id="sidenav" class="sidenav wow fadeInUp" data-wow-duration="2s" data-wow-delay="0.1s"> | ||
+ | <a href="#BB">BioBrick 2.0</a> | ||
+ | <a href="#IM">Intein Monomers</a> | ||
+ | <a href="#SC">Spidroin Constructs</a> | ||
+ | <a href="#IP">Intein Passenger</a> | ||
+ | <a href="#NIKR">NikR</a> | ||
+ | <a href="#ER">ER</a> | ||
+ | </div> | ||
+ | |||
− | <div class=" | + | <section id="BB"> |
− | <div class=" | + | <div class="card card_igem wow fadeInUp" data-wow-duration="2s" data-wow-delay="0.1s"> |
− | < | + | <div class="card-title text-center"> |
− | < | + | <h4>BioBrick 2.0</h4> |
− | < | + | </div> |
− | < | + | <div class="card-body text-justify"> |
− | < | + | <div class="container"> |
− | </ | + | <div class="row"> |
+ | <div class="col-sm-10 mmmm mrfont"> | ||
+ | <br> | ||
+ | <div class="card-title text-center"> | ||
+ | <div class="h4_cards">Overview</div> | ||
+ | </div> | ||
+ | <br> | ||
+ | <p>While developing our modular platform, we conceived a BioBrick-compatible standard with improved flexibility that enables the integration of conventional cloning methods into iGEM’s workflow. This construct, once inserted into a backbone, allows cloning through Golden Gate assembly and Gibson assembly. At the same time, our construct has a LacZ reporter which can be used to screen plates for successful colonies. We are proposing our BioBrick2.0 as a new standard, which could facilitate an improved cloning process for future iGEM teams.</p> | ||
+ | <br> | ||
+ | <div class="card-title text-center"> | ||
+ | <div class="h4_cards">Reporter</div> | ||
+ | </div> | ||
+ | <p class="card-text card-text_igem text-justify"> | ||
+ | The lacZ reporter allows for blue-white screening. It can be displaced by compatible constructs through BioBrick assembly, Golden Gate assembly or Gibson assembly. Blue-white screening is based on the inability of commercial E. coli to metabolise galactose or structurally similar substrates like X-Gal because of a lacZ deletion mutation. Once lacZα is provided through a plasmid, X-Gal can be metabolised to an easily detectable blue compound. This screening can also be used for subsequent cloning where the displacement of lacZ results in white colonies. | ||
+ | </p> | ||
+ | <br> | ||
+ | <div class="card-title text-center"> | ||
+ | <div class="h4_cards">Compatibility</div> | ||
</div> | </div> | ||
+ | <p>For Golden Gate assembly, BsaI cut sites and defined overhangs were added. The BsaI overhangs are based on Vladimir et al. 2018 [1]. CCAA was chosen for upstream and ACGG for downstream. For Gibson assembly, a defined area of homology was designed. BsaI can be used to open the plasmid, removing the reporter and exposing the Gibson overhangs. </p> | ||
+ | <br><br> | ||
+ | <div class="card-title text-center"> | ||
+ | <div class="h4_cards">BioBrick2.0 standardisation</div> | ||
</div> | </div> | ||
+ | <br> | ||
+ | <p>One of the oldest problems of biological research which persists nowadays is the lack of standardization in experimental design, which impacts reproducibility and therefore reliability of results. Especially with the advent of DNA cloning, sequencing and omics techniques, there has been a growing need for a connecting thread which would simplify the bundle of data generated by these new experimental techniques. Arkin and Endy from MIT were the first ones who tried to address the issue by publishing a standard registry of biological parts which didn’t have considerable success [1]. However, Tom Knight, one of their colleagues, who at the time was working in an artificial intelligence laboratory, proposed in 2003 a new standard called Biobrick [2]. BioBricks are DNA sequences which conform to a restriction enzyme assembly standard, building blocks which can be assembled in larger synthetic biological circuits from individual parts.</p> | ||
+ | <br> | ||
+ | <p>Over the years the Biobrick assembly has shown various flaws. First of all, it doesn’t allow for assembly of multiple parts in one reaction and it cannot be used for fusion proteins. Secondly, it produces a scar sequence which can be harmful for E. coli [3]. Even though, some of these issues have been addressed by improved methodologies such as the Silver or the 3A [4], [5], they are unnecessarily laborious as they require additional pre-screenings or, in the case of 3A, three different antibiotics. | ||
+ | </p> | ||
+ | <br> | ||
+ | <p>Our BioBrick2.0 construct integrates different cloning techniques, such as Gibson assembly and Golden Gate assembly, into the iGEM standard. When cloned into a backbone through BioBrick Assembly, it enables the other cloning methods to be used inside the BioBrick2.0 sequence. The Gibson overlapping regions allow for high-fidelity cloning of constructs up to thousands of kilobases, as shown previously [6]. The Golden Gate recognition sites allow for seamless cloning and, applying methods such as MoClo and Golden Braid, this procedure can be carried out with multiple fragments in one single reaction [7] [8].</p> | ||
+ | <br> | ||
+ | <p>The purpose of the BioBrick is not to create a new standard because, as it happened before in synthetic biology, an excess of attempts at creating new standards can become detrimental [9]. As a consequence, our brick is meant to be a platform to BioBrick standardize constructs cloned using different methods to accommodate different labs’ preferences and boost the iGEM workflow. | ||
+ | </p> | ||
+ | <br> | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | </section> | ||
+ | |||
+ | <section id="IM"> | ||
+ | <div class="card card_igem wow fadeInUp" data-wow-duration="2s" data-wow-delay="0.1s"> | ||
+ | <div class="card-title text-center"> | ||
+ | <h4>Intein Monomers</h4> | ||
+ | </div> | ||
+ | <div class="card-body text-justify"> | ||
+ | <div class="container"> | ||
+ | <div class="row"> | ||
+ | <div class="col-sm-10 mmmm mrfont"> | ||
+ | <div class="card-title text-center"> | ||
+ | <div class="h4_cards">Intein Monomer 1 and Intein Monomer 2</div> | ||
+ | </div> | ||
+ | <p class="card-text card-text_igem text-justify"> | ||
+ | |||
+ | <br><br> | ||
+ | Initially we planned to clone constructs that would allow us to produce long spider silk proteins which could then be functionalised with proteins of interest using SpyTag/SpyCatcher technology. We later realised that instead of restricting ourselves to just one protein - spider silk protein, we could develop a much broader platform to polymerise any protein of interest. To achieve this we thought about using split inteins for polymerisation. We designed two constructs ,Bba_K2842680 and Bba_K2842690 that could work together to polymerise proteins via intein trans-splicing. Each construct is made of an Intein C termini, a fluorescent reporter protein, a StrepTag and an intein N termini. | ||
+ | We introduced Type II restriction sites sites that could be used to introduce any protein of interest into the construct for polymerisation. | ||
+ | </p> | ||
+ | <br><br> | ||
+ | <div class="card-title text-center"> | ||
+ | <div class="h4_cards">Design Details</div> | ||
+ | </div> | ||
+ | <br> | ||
+ | <p><b>Inteins</b>: Each construct contains orthogonal inteins on each side preventing self reaction and circularisation. The orthogonal inteins mean that polymerisation will only occur when both constructs are expressed together or when the two proteins are combined.</p> | ||
+ | <br> | ||
+ | <p><b>Reporters</b>: One construct contains GFP and the other mRFP1. This will enable easy identification of cross polymerisation by fluorescence measurements.</p> | ||
+ | <br> | ||
+ | <p><b>Modular design</b>: SapI sites were placed immediately upstream and downstream of the reporter proteins. The codons used were designed to be as innocuous as possible.</p> | ||
+ | <br> | ||
+ | <p><b>Other elements</b></p> | ||
+ | |||
+ | <p>Promotor: A T7 promoter was used <br> | ||
+ | RBS: We used a RBS based on predictions by sallis lab [1,2] <br> | ||
+ | Regulatory elements: We introduced a lac operator to further control gene expression if the T7 promoter was too strong or detrimental to cell health. | ||
+ | </p> | ||
+ | <br><br> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | </section> | ||
+ | <section id="SC"> | ||
+ | <div class="card card_igem wow fadeInUp" data-wow-duration="2s" data-wow-delay="0.1s"> | ||
+ | <div class="card-title text-center"> | ||
+ | <h4>Spidroin Constructs</h4> | ||
+ | </div> | ||
+ | <div class="card-body text-justify"> | ||
+ | <div class="container"> | ||
+ | <div class="row"> | ||
+ | <div class="col-sm-10 mmmm mrfont"> | ||
+ | <div class="card-title text-center"> | ||
+ | <div class="h4_cards">Spidroin Constructs</div> | ||
+ | </div> | ||
+ | <p class="card-text card-text_igem text-justify"> | ||
+ | A spidroin is a protein belonging to the family of scleroproteins, which includes collagen and keratin. It is the main building block of spiders’ dragline silk; its tensile properties exceed steel and kevlar and, at the same time, it is more flexible than both of these material as it can be stretched up to 135% of its original length. | ||
+ | </p> | ||
+ | <br> | ||
+ | <p>The amino acid composition is largely dominated by alanine, found in the crystalline regions of the protein, and glycine blocks found in the amorphous matrix. The alternation of the crystalline and amorphous regions, formed by helical structures and beta turns, is what gives spidersilk its incredible properties. However, the protein by itself is a monomer, therefore in order to form a strong fiber, it has to form an oligomer. The C-termini in solution associate by covalent bond and with a change in pH, which in vivo is carried by transport into a different gland The N-termini form hydrogen bonds and complete the oligomerization. | ||
+ | </p> | ||
+ | <br> | ||
+ | <p>Our construct, which we split into two for simplicity of assembly, is composed by the spidroin core with four total repetitive regions, two in one construct and two in the other, and the C-and N-termini, distinguishing the two constructs. Moreover, to enable characterisation of the fiber, we flanked the C-terminus of the sequence with the N-terminus of the AceL-TerL intein which would splice out when associated with its compatible counterpart. | ||
+ | </p> | ||
+ | <br> | ||
+ | <p>The assembly of this construct can be carried out through Gibson assembly or Golden Gate into our BioBrick2.0 construct to standardise it for Bobrick assembly. Finally, the fibre can also be modified to test different properties through assembly of additional repetitive regions into the core of the sequence. This is made possible by our SapI overhangs which are compatible with the ones on our Spidroin Core construct. </p> | ||
+ | <br><br> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | </section> | ||
+ | <section id="IP"> | ||
+ | <div class="card card_igem wow fadeInUp" data-wow-duration="2s" data-wow-delay="0.1s"> | ||
+ | <div class="card-title text-center"> | ||
+ | <h4>Intein Passenger</h4> | ||
+ | </div> | ||
+ | <div class="card-body text-justify"> | ||
+ | <div class="container"> | ||
+ | <div class="row"> | ||
+ | <div class="col-sm-10 mmmm mrfont"> | ||
+ | <div class="card-title text-center"> | ||
+ | <div class="h4_cards">Overview of Intein Passenger</div> | ||
+ | </div> | ||
+ | <p class="card-text card-text_igem text-justify"> | ||
+ | The intein passenger construct is the framework used to insert functional proteins into our highly modular platform. The design of the Biobrick allows it to flank any protein with inteins and, therefore, to functionalise biomaterials with a high degree of freedom. | ||
+ | Design notes: | ||
+ | |||
+ | </p> | ||
+ | <br> | ||
+ | <br> | ||
+ | <center><b>Intein</b></center> | ||
+ | <br> | ||
+ | <p>The choice of intein is important because we need to leave as small a fragment as possible at the sister construct. We picked the AceL-TerL intein (DOI 10.1002/anie.201307969) since its C-terminal section is 125 amino acids long and the N-terminal section only 11. </p> | ||
+ | <br> | ||
+ | <br> | ||
+ | <cen></cen> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | </section> | ||
+ | <section id="BB"> | ||
+ | <div class="card card_igem wow fadeInUp" data-wow-duration="2s" data-wow-delay="0.1s"> | ||
+ | <div class="card-title text-center"> | ||
+ | <h4>BioBrick 2.0</h4> | ||
+ | </div> | ||
+ | <div class="card-body text-justify"> | ||
+ | <div class="container"> | ||
+ | <div class="row"> | ||
+ | <div class="col-sm-10 mmmm mrfont"> | ||
+ | <p class="card-text card-text_igem text-justify"> | ||
+ | Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. | ||
+ | </p> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | </section> | ||
+ | <section id="BB"> | ||
+ | <div class="card card_igem wow fadeInUp" data-wow-duration="2s" data-wow-delay="0.1s"> | ||
+ | <div class="card-title text-center"> | ||
+ | <h4>BioBrick 2.0</h4> | ||
+ | </div> | ||
+ | <div class="card-body text-justify"> | ||
+ | <div class="container"> | ||
+ | <div class="row"> | ||
+ | <div class="col-sm-10 mmmm mrfont"> | ||
+ | <p class="card-text card-text_igem text-justify"> | ||
+ | Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. | ||
+ | </p> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | </section> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | |||
+ | </div> | ||
+ | <!--FOOTER================================================================== --> | ||
+ | <div class="footer"> | ||
+ | <div class="container"> | ||
+ | <div class="row"> | ||
+ | <div class="col-lg-4"> | ||
+ | <center> | ||
+ | <div class="h2_footer_igem">Our Location</div> | ||
+ | University College London<br /> | ||
+ | Gower St, Bloomsbury<br />London <br />WC1E 6BT | ||
+ | <span></span> | ||
+ | </center> | ||
+ | </div> | ||
+ | <div class="col-lg-4"> | ||
+ | <center> | ||
+ | <div class="h2_footer_igem">Contact Us</div> | ||
+ | ucl.igem@ucl.ac.uk | ||
+ | <a class="footer_img_igem" href="https://www.ucl.ac.uk/"> | ||
+ | <img src="https://static.igem.org/mediawiki/2018/f/ff/T--UCL--UCLLogo.jpeg" height="100rem;" /> | ||
+ | </a> | ||
+ | </center> | ||
+ | </div> | ||
+ | <div class="col-lg-4"> | ||
+ | <center> | ||
+ | <div class="h2_footer_igem">Follow Us</div> | ||
+ | <a href="https://www.facebook.com/UCLiGEM/"class="contacticons"> | ||
+ | <img src="https://static.igem.org/mediawiki/2018/c/c4/T--UCL--FBLogo.svg" style="padding-top:1em;" height="62rem;"/> | ||
+ | </a> | ||
+ | <a href="https://twitter.com/ucligem?lang=en"class="contacticons"> | ||
+ | <img src="https://static.igem.org/mediawiki/2018/e/ed/T--UCL--TwitterLogo.svg" style="padding-top:1em;" height="62rem;"/> | ||
+ | </a> | ||
+ | <a href="https://www.instagram.com/ucl.igem/"class="contacticons"> | ||
+ | <img src="https://static.igem.org/mediawiki/2018/3/31/T--UCL--InstaLogo.png" style="padding-top:1em;" height="62rem;"/> | ||
+ | </a> | ||
+ | </center> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | </div> | ||
+ | </body> | ||
</html> | </html> |
Revision as of 03:21, 18 October 2018
BioBrick 2.0
While developing our modular platform, we conceived a BioBrick-compatible standard with improved flexibility that enables the integration of conventional cloning methods into iGEM’s workflow. This construct, once inserted into a backbone, allows cloning through Golden Gate assembly and Gibson assembly. At the same time, our construct has a LacZ reporter which can be used to screen plates for successful colonies. We are proposing our BioBrick2.0 as a new standard, which could facilitate an improved cloning process for future iGEM teams.
The lacZ reporter allows for blue-white screening. It can be displaced by compatible constructs through BioBrick assembly, Golden Gate assembly or Gibson assembly. Blue-white screening is based on the inability of commercial E. coli to metabolise galactose or structurally similar substrates like X-Gal because of a lacZ deletion mutation. Once lacZα is provided through a plasmid, X-Gal can be metabolised to an easily detectable blue compound. This screening can also be used for subsequent cloning where the displacement of lacZ results in white colonies.
For Golden Gate assembly, BsaI cut sites and defined overhangs were added. The BsaI overhangs are based on Vladimir et al. 2018 [1]. CCAA was chosen for upstream and ACGG for downstream. For Gibson assembly, a defined area of homology was designed. BsaI can be used to open the plasmid, removing the reporter and exposing the Gibson overhangs.
One of the oldest problems of biological research which persists nowadays is the lack of standardization in experimental design, which impacts reproducibility and therefore reliability of results. Especially with the advent of DNA cloning, sequencing and omics techniques, there has been a growing need for a connecting thread which would simplify the bundle of data generated by these new experimental techniques. Arkin and Endy from MIT were the first ones who tried to address the issue by publishing a standard registry of biological parts which didn’t have considerable success [1]. However, Tom Knight, one of their colleagues, who at the time was working in an artificial intelligence laboratory, proposed in 2003 a new standard called Biobrick [2]. BioBricks are DNA sequences which conform to a restriction enzyme assembly standard, building blocks which can be assembled in larger synthetic biological circuits from individual parts.
Over the years the Biobrick assembly has shown various flaws. First of all, it doesn’t allow for assembly of multiple parts in one reaction and it cannot be used for fusion proteins. Secondly, it produces a scar sequence which can be harmful for E. coli [3]. Even though, some of these issues have been addressed by improved methodologies such as the Silver or the 3A [4], [5], they are unnecessarily laborious as they require additional pre-screenings or, in the case of 3A, three different antibiotics.
Our BioBrick2.0 construct integrates different cloning techniques, such as Gibson assembly and Golden Gate assembly, into the iGEM standard. When cloned into a backbone through BioBrick Assembly, it enables the other cloning methods to be used inside the BioBrick2.0 sequence. The Gibson overlapping regions allow for high-fidelity cloning of constructs up to thousands of kilobases, as shown previously [6]. The Golden Gate recognition sites allow for seamless cloning and, applying methods such as MoClo and Golden Braid, this procedure can be carried out with multiple fragments in one single reaction [7] [8].
The purpose of the BioBrick is not to create a new standard because, as it happened before in synthetic biology, an excess of attempts at creating new standards can become detrimental [9]. As a consequence, our brick is meant to be a platform to BioBrick standardize constructs cloned using different methods to accommodate different labs’ preferences and boost the iGEM workflow.
Intein Monomers
Initially we planned to clone constructs that would allow us to produce long spider silk proteins which could then be functionalised with proteins of interest using SpyTag/SpyCatcher technology. We later realised that instead of restricting ourselves to just one protein - spider silk protein, we could develop a much broader platform to polymerise any protein of interest. To achieve this we thought about using split inteins for polymerisation. We designed two constructs ,Bba_K2842680 and Bba_K2842690 that could work together to polymerise proteins via intein trans-splicing. Each construct is made of an Intein C termini, a fluorescent reporter protein, a StrepTag and an intein N termini.
We introduced Type II restriction sites sites that could be used to introduce any protein of interest into the construct for polymerisation.
Inteins: Each construct contains orthogonal inteins on each side preventing self reaction and circularisation. The orthogonal inteins mean that polymerisation will only occur when both constructs are expressed together or when the two proteins are combined.
Reporters: One construct contains GFP and the other mRFP1. This will enable easy identification of cross polymerisation by fluorescence measurements.
Modular design: SapI sites were placed immediately upstream and downstream of the reporter proteins. The codons used were designed to be as innocuous as possible.
Other elements
Promotor: A T7 promoter was used
RBS: We used a RBS based on predictions by sallis lab [1,2]
Regulatory elements: We introduced a lac operator to further control gene expression if the T7 promoter was too strong or detrimental to cell health.
Spidroin Constructs
A spidroin is a protein belonging to the family of scleroproteins, which includes collagen and keratin. It is the main building block of spiders’ dragline silk; its tensile properties exceed steel and kevlar and, at the same time, it is more flexible than both of these material as it can be stretched up to 135% of its original length.
The amino acid composition is largely dominated by alanine, found in the crystalline regions of the protein, and glycine blocks found in the amorphous matrix. The alternation of the crystalline and amorphous regions, formed by helical structures and beta turns, is what gives spidersilk its incredible properties. However, the protein by itself is a monomer, therefore in order to form a strong fiber, it has to form an oligomer. The C-termini in solution associate by covalent bond and with a change in pH, which in vivo is carried by transport into a different gland The N-termini form hydrogen bonds and complete the oligomerization.
Our construct, which we split into two for simplicity of assembly, is composed by the spidroin core with four total repetitive regions, two in one construct and two in the other, and the C-and N-termini, distinguishing the two constructs. Moreover, to enable characterisation of the fiber, we flanked the C-terminus of the sequence with the N-terminus of the AceL-TerL intein which would splice out when associated with its compatible counterpart.
The assembly of this construct can be carried out through Gibson assembly or Golden Gate into our BioBrick2.0 construct to standardise it for Bobrick assembly. Finally, the fibre can also be modified to test different properties through assembly of additional repetitive regions into the core of the sequence. This is made possible by our SapI overhangs which are compatible with the ones on our Spidroin Core construct.
Intein Passenger
The intein passenger construct is the framework used to insert functional proteins into our highly modular platform. The design of the Biobrick allows it to flank any protein with inteins and, therefore, to functionalise biomaterials with a high degree of freedom. Design notes:
The choice of intein is important because we need to leave as small a fragment as possible at the sister construct. We picked the AceL-TerL intein (DOI 10.1002/anie.201307969) since its C-terminal section is 125 amino acids long and the N-terminal section only 11.
BioBrick 2.0
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
BioBrick 2.0
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.