Team:Groningen/Project/SilkAssemblyShop
From 2013.igem.org
Line 68: | Line 68: | ||
<li>Select the subunits you need</li> | <li>Select the subunits you need</li> | ||
<li>Assemble them together</li></ol> | <li>Assemble them together</li></ol> | ||
- | At this point the silk product is ready to be produced (<a href="https://2013.igem.org/Team:Groningen/ | + | At this point the silk product is ready to be produced (<a href="https://2013.igem.org/Team:Groningen/Navigation/Construct">See production backbone</a>) and employed for the desired purpose. |
</p> | </p> | ||
Revision as of 10:39, 3 October 2013
Silk Assembly Shop
Bacillus subtilis silk genes collection derived from Argiope aurantia MaSp2
One of the challenges that the project includes is the production of spider silk. In order to achieve this goal iGEM Groningen designed for you what we call “The Bacillus subtilis silk assembly shop”.
The 'shop' idea follows those conceptual steps:
- Design your own silk protein
- Browse the iGEM Groningen silk subunits collection:
- Select the subunits you need
- Assemble them together
Spider silk subunit |
Biobrick id | Construct Features | ||
---|---|---|---|---|
RBS | Strep-tag | Stop codon | ||
E1 | BBa_K1085000 | 25px | 25px | |
BBa_K1085001 | 25px | |||
E2 | BBa_K1085002 | |||
BBa_K1085003 | 25px | |||
Tail | BBa_K1085008 | 25px | ||
BBa_K1085009 | 25px | 25px | ||
table 1: The following silk subunits are: E1 blabla , E2 blabla and Tail blabla. |
The Groningen team enriched the iGEM database adding several new Bacillus subtilis BioBricks containing spider silk gene subunits. This provides the iGEM community with a new bunch of parts; which, in the future, will help anyone in assembling its own silk protein and customize it with different features.
It is the first time that silk-coding BioBricks suitable for Bacillus subtilis are introduced into the database. Therefore this work marks the starting point for further studies about silk within the Bacillus subtilis chassis inside the iGEM framework.
The advantages shown by our collection are mainly two which can be summarized as follows:
- Accessible design The iGEM database provides a lot of basic parts (such as RBS and terminator), but often achieving the desired goal turns out to be really tedious and time consuming, since the creation of a working construct needs to go through a lot of steps. iGEM Groningen took into account this problematic aspect while designing the silk collection, therefore all the silk subunits (each of them coding for the same final protein product) have been created in different versions (see Table 1). Such a design enables the end-user to quickly reach the desired silk protein construct without bothering too much about the molecular issues. This kind of approach helps to make synthetic biology and specifically working with silk protein in Bacilus subtilis production more accessible.
- Compatibility with BioBrick standards
We are aware that the BioBrick assembly standard is the foundation of the iGEM method, allowing all different laboratories to build on each others work. That is why the silk subunits are compatible with the following standard:
- BBF RFC 10
- BBF RFC 12
- BBF RFC 21
- BBF RFC 23
- BBF RFC 25
- BBF RFC 1000
- dealing with repetitiveness One of the issue while working with the silk protein is the high repetitiveness of the coding sequence. The subunit concept provides us with a smart solution; indeed the molecular steps do not depend anymore on the silk coding sequence itself, but on the universal flanking regions. This
Strep-tag
Why this is needed
For what purposes it comes in handy
Signal peptide
Why is it so important.
The use of existing pathway so not lots of trouble
The signal sequences are nice addition to the registry
how the pathway works and how the silk will be secreted