Difference between revisions of "Team:iTesla-SoundBio/Parts"

(Prototype team page)
 
 
(29 intermediate revisions by 5 users not shown)
Line 1: Line 1:
 
{{iTesla-SoundBio}}
 
{{iTesla-SoundBio}}
 
<html>
 
<html>
 +
<script>
 +
    $("#title").text("BioBrick Parts")
 +
</script>
  
 +
<div width="600px" margin="auto">
 +
<br />
 +
<center><h2>We did not successfully complete any BioBricks, but we had the construction of several planned and in progress.</h2></center>
 +
<br />
  
<div class="column full_size">
+
<center><img src="https://static.igem.org/mediawiki/2018/1/1f/T--iTesla-SoundBio--BioBrick_Parts_Table.png" width="80%"></center>
<h1>Parts</h1>
+
<p>Each team will make new parts during iGEM and will submit them to the Registry of Standard Biological Parts. The iGEM software provides an easy way to present the parts your team has created. The <code>&lt;groupparts&gt;</code> tag (see below) will generate a table with all of the parts that your team adds to your team sandbox.</p>
+
<p>Remember that the goal of proper part documentation is to describe and define a part, so that it can be used without needing to refer to the primary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper references to acknowledge previous authors and to provide for users who wish to know more.</p>
+
</div>
+
  
<div class="column full_size">
 
<div class="highlight decoration_background">
 
<h3>Note</h3>
 
<p>Note that parts must be documented on the <a href="http://parts.igem.org/Main_Page"> Registry</a>. This page serves to <i>showcase</i> the parts you have made. Future teams and other users and are much more likely to find parts by looking in the Registry than by looking at your team wiki.</p>
 
</div>
 
</div>
 
  
<div class="clear extra_space"></div>
+
<u><h2 style="margin-left: 40px; font-size: 26px;">BBa_K2563000: Limulus Factor C Coding Sequence</h2></u>
<div class="line_divider"></div>
+
<p style="font-size: 20px; margin-left: 40px"> This would be the coding sequence for Limulus Clotting Factor C. To create this, we would first acquire the <a href="https://www.uniprot.org/uniprot/P28175" target="blank">amino acid sequence</a> from UniProt (UniProtKB - P28175 (LFC_TACTR)), then codon optimize for B. subtilis using JCat and add the BioBrick prefix and suffix. The Factor C sequence is just over the IDT length limit for free synthesis--the limit is 3kb, while the sequence was 3,133 bases long--so we would need to synthesize it as two separate parts. We would independently digest and ligate these fragments into two separate plasmid backbones, then PCR the plasmids, digest the fragments out, ligate them together, and finally ligate them into the backbone pSB1C3. To design those fragments, we would have them overlap at a BioBrick-compatible restriction site in the middle of the Factor C sequence. This would be used to ligate the fragments together once we had purified samples of each.
<div class="clear extra_space"></div>
+
</p>
 +
</br>
 +
<img src="https://static.igem.org/mediawiki/2018/d/de/T--iTesla-SoundBio--Factor_C_BioBrick.png" style="float: left; width: 53%; margin-left: 40px;"></img>
 +
<p style="font-size: 20px; margin-left: 40px">Each Factor C fragment would also be flanked by a BioBrick prefix and suffix, and the theoretical completed Factor C gene would be flanked by the restriction sites BamHI and SacII. These restriction sites are part of the BioBrick prefix and suffix and would be useful for future digestion and ligation into an expression vector. We would then separately digest Fragment 1 and our BioBricking vector (pSB1C3) using restriction enzymes PstI and EcoRI, then ligate those two components together and transform that Fragment 1 + pSB1C3 complex into E. coli. After growing copies of that plasmid with Fragment 1 inside, we would miniprep successful colonies and sequence them to ensure success.
 +
</p>
 +
</br>
 +
<p style="font-size: 20px; margin-left: 40px">Afterwards, we would digest the Fragment 1 + pSB1C3 complex with the BglII and PstI restriction enzymes, making an opening that would allow Fragment 2 to ligate with the appropriate side of Fragment 1. After digesting Fragment 2 with the same restriction enzymes, we would ligate and transform those components into E. coli. If all went according to plan, the resulting colony would contain the pSB1C3 + Fragment 1 + Fragment 2 complex and thus the completed BioBrick.</li>
 +
</br></br>
 +
Our attempts to carry out this procedure were foiled by our repeated failure to successfully execute digests. If we were to attempt this again, we would design a geneblock comprising the entire Factor C sequence save ~70 bases on each end, then use extra-long primers to add in the rest. This would require fewer total steps and thus have a lower chance of failure.
 +
</p>
 +
<center><img src="https://static.igem.org/mediawiki/2018/3/3e/T--iTesla-SoundBio--Fragment_1_Cloning_Flowchart.png" style=" width: 60%;"></img></center>
  
 +
<u><h2 style="margin-left: 40px; font-size: 26px;">BBa_K2563001: pAX01 w/xylR+PxylA</h2></u>
  
 +
<p style="font-size: 20px; margin-left: 40px">This would be a BioBrick-compatible version of the Bacillus integration vector pAX01. Unlike BBa_J179001--to which it is otherwise identical--it would include the xylose-inducible xylR+PxylA repressor-promoter system specified by the part BBa_K733002. This would allow transcriptional regulation of the cloned gene through the addition and removal of xylose.
 +
</br></br>
 +
After getting the pAX01 plasmid from BGSC, we would need to make numerous modifications to make it BioBrick-compatible, including the insertion of the BioBrick prefix and suffix at the MCS. The first step, however, would be confirming the sequence of the plasmid in our possession. We would use twelve sequencing primers to do this (see Table 1). Once the sequence of the plasmid was confirmed, we would carry out a series of steps that, if completed correctly, would result in the successful synthesis of the pAX01 BioBrick.
 +
</br></br>
 +
The first step would be to swap out the xylose cassette in pAX01 with BBa_K733002, removing a few BioBrick-incompatible restriction sites. This would require FastCloning: we would begin by running PCRs of BBa_K733002 and pAX01 such that the product of pAX01 would exclude its xylose cassette (using the FastClone primers in Table 1), then we would digest the PCR products with DpnI, transform them into E. coli, and miniprep the resulting plasmids. We would then send these off for sequencing; if the FastClone were successful, its product would be pAX01 with its xylose cassette region replaced by BBa_K733002.
 +
</br></br>
 +
Next, we would need to perform site-directed mutagenesis on pAX01’s AmpR region by running a PCR with the primers pAX01 Point Mut Fwd and pAX01 Point Mut Rev (see Table 1). We would digest the PCR products with DpnI, transform them into E. coli, then miniprep and sequence the resulting plasmids.
 +
</br></br>
 +
We would next run two deletions, each using the same protocol as that of the AmpR mutagenesis except for the primers (see Table 1). Finally, we would run an insertion, again using the same protocol except for the primers (see Table 1).
 +
</br></br>
 +
We began by trying to FastClone the xylose cassette BBa_K733002 into pAX01, but our PCRs and transformations consistently failed and we were unable to construct the BioBrick. This may have been a result of poor primer design, incorrect annealing temperatures, incorrect transformation procedures, and/or human error in carrying out the procedures. If we were to do this again, we would document our labs much more thoroughly and possibly try a technique other than FastClone for the BBa_K733002 insertion.
 +
</br></br>
 +
<b>Table 1:</b>
 +
</p>
  
 +
<center><img src="https://static.igem.org/mediawiki/2018/d/d7/T--iTesla-SoundBio--pAX01_Primer_Table.png", style="width: 60%"></center>
  
 
<div class="column two_thirds_size">
 
<div class="highlight decoration_B_full">
 
 
<h3>Adding parts to the registry</h3>
 
<p>You can add parts to the Registry at our <a href="http://parts.igem.org/Add_a_Part_to_the_Registry">Add a Part to the Registry</a> link.</p>
 
 
<p>We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The sooner you put up your parts, the better you will remember all the details about your parts. Remember, you don't need to send us the DNA sample before you create an entry for a part on the Registry. (However, you <b>do</b> need to send us the DNA sample before the Jamboree. If you don't send us a DNA sample of a part, that part will not be eligible for awards and medal criteria.)</p>
 
<div class="button_link">
 
<a href="http://parts.igem.org/Add_a_Part_to_the_Registry">
 
ADD PARTS
 
</a>
 
 
</div>
 
</div>
 
</div>
 
</div>
 
 
 
 
<div class="column third_size">
 
<div class="highlight decoration_A_full">
 
<h3>Inspiration</h3>
 
<p>We have a created  a <a href="http://parts.igem.org/Well_Documented_Parts">collection of well documented parts</a> that can help you get started.</p>
 
 
<p> You can also take a look at how other teams have documented their parts in their wiki:</p>
 
<ul>
 
<li><a href="https://2014.igem.org/Team:MIT/Parts"> 2014 MIT </a></li>
 
<li><a href="https://2014.igem.org/Team:Heidelberg/Parts"> 2014 Heidelberg</a></li>
 
<li><a href="https://2014.igem.org/Team:Tokyo_Tech/Parts">2014 Tokyo Tech</a></li>
 
</ul>
 
</div>
 
</div>
 
 
 
<div class="clear extra_space"></div>
 
 
 
 
 
<div class="column full_size">
 
 
<h3>What information do I need to start putting my parts on the Registry?</h3>
 
<p>The information needed to initially create a part on the Registry is:</p>
 
<ul>
 
<li>Part Name</li>
 
<li>Part type</li>
 
<li>Creator</li>
 
<li>Sequence</li>
 
<li>Short Description (60 characters on what the DNA does)</li>
 
<li>Long Description (Longer description of what the DNA does)</li>
 
<li>Design considerations</li>
 
</ul>
 
 
<p>
 
We encourage you to put up <em>much more</em> information as you gather it over the summer. If you have images, plots, characterization data and other information, please also put it up on the part page. </p>
 
 
</div>
 
 
 
<div class="clear extra_space"></div>
 
<div class="line_divider"></div>
 
<div class="clear extra_space"></div>
 
 
<div class="column full_size">
 
<h3>Part Table </h3>
 
 
<p>Please include a table of all the parts your team has made during your project on this page. Remember part characterization and measurement data must go on your team part pages on the Registry. </p>
 
 
</html>
 
<groupparts>iGEM18 iTesla-SoundBio</groupparts>
 
<html>
 
</div>
 
 
 
 
  
 
</html>
 
</html>

Latest revision as of 04:52, 16 October 2018


We did not successfully complete any BioBricks, but we had the construction of several planned and in progress.


BBa_K2563000: Limulus Factor C Coding Sequence

This would be the coding sequence for Limulus Clotting Factor C. To create this, we would first acquire the amino acid sequence from UniProt (UniProtKB - P28175 (LFC_TACTR)), then codon optimize for B. subtilis using JCat and add the BioBrick prefix and suffix. The Factor C sequence is just over the IDT length limit for free synthesis--the limit is 3kb, while the sequence was 3,133 bases long--so we would need to synthesize it as two separate parts. We would independently digest and ligate these fragments into two separate plasmid backbones, then PCR the plasmids, digest the fragments out, ligate them together, and finally ligate them into the backbone pSB1C3. To design those fragments, we would have them overlap at a BioBrick-compatible restriction site in the middle of the Factor C sequence. This would be used to ligate the fragments together once we had purified samples of each.


Each Factor C fragment would also be flanked by a BioBrick prefix and suffix, and the theoretical completed Factor C gene would be flanked by the restriction sites BamHI and SacII. These restriction sites are part of the BioBrick prefix and suffix and would be useful for future digestion and ligation into an expression vector. We would then separately digest Fragment 1 and our BioBricking vector (pSB1C3) using restriction enzymes PstI and EcoRI, then ligate those two components together and transform that Fragment 1 + pSB1C3 complex into E. coli. After growing copies of that plasmid with Fragment 1 inside, we would miniprep successful colonies and sequence them to ensure success.


Afterwards, we would digest the Fragment 1 + pSB1C3 complex with the BglII and PstI restriction enzymes, making an opening that would allow Fragment 2 to ligate with the appropriate side of Fragment 1. After digesting Fragment 2 with the same restriction enzymes, we would ligate and transform those components into E. coli. If all went according to plan, the resulting colony would contain the pSB1C3 + Fragment 1 + Fragment 2 complex and thus the completed BioBrick.

Our attempts to carry out this procedure were foiled by our repeated failure to successfully execute digests. If we were to attempt this again, we would design a geneblock comprising the entire Factor C sequence save ~70 bases on each end, then use extra-long primers to add in the rest. This would require fewer total steps and thus have a lower chance of failure.

BBa_K2563001: pAX01 w/xylR+PxylA

This would be a BioBrick-compatible version of the Bacillus integration vector pAX01. Unlike BBa_J179001--to which it is otherwise identical--it would include the xylose-inducible xylR+PxylA repressor-promoter system specified by the part BBa_K733002. This would allow transcriptional regulation of the cloned gene through the addition and removal of xylose.

After getting the pAX01 plasmid from BGSC, we would need to make numerous modifications to make it BioBrick-compatible, including the insertion of the BioBrick prefix and suffix at the MCS. The first step, however, would be confirming the sequence of the plasmid in our possession. We would use twelve sequencing primers to do this (see Table 1). Once the sequence of the plasmid was confirmed, we would carry out a series of steps that, if completed correctly, would result in the successful synthesis of the pAX01 BioBrick.

The first step would be to swap out the xylose cassette in pAX01 with BBa_K733002, removing a few BioBrick-incompatible restriction sites. This would require FastCloning: we would begin by running PCRs of BBa_K733002 and pAX01 such that the product of pAX01 would exclude its xylose cassette (using the FastClone primers in Table 1), then we would digest the PCR products with DpnI, transform them into E. coli, and miniprep the resulting plasmids. We would then send these off for sequencing; if the FastClone were successful, its product would be pAX01 with its xylose cassette region replaced by BBa_K733002.

Next, we would need to perform site-directed mutagenesis on pAX01’s AmpR region by running a PCR with the primers pAX01 Point Mut Fwd and pAX01 Point Mut Rev (see Table 1). We would digest the PCR products with DpnI, transform them into E. coli, then miniprep and sequence the resulting plasmids.

We would next run two deletions, each using the same protocol as that of the AmpR mutagenesis except for the primers (see Table 1). Finally, we would run an insertion, again using the same protocol except for the primers (see Table 1).

We began by trying to FastClone the xylose cassette BBa_K733002 into pAX01, but our PCRs and transformations consistently failed and we were unable to construct the BioBrick. This may have been a result of poor primer design, incorrect annealing temperatures, incorrect transformation procedures, and/or human error in carrying out the procedures. If we were to do this again, we would document our labs much more thoroughly and possibly try a technique other than FastClone for the BBa_K733002 insertion.

Table 1: