Difference between revisions of "Team:CIEI-BJ/Parts"

(Prototype team page)
 
Line 2: Line 2:
 
<html>
 
<html>
  
 +
<h2>Our team have summited two parts</h2>
 +
<h3> Part:BBa_K2631000</h3>
 +
<p>ADTZ Enzyme</p>
 +
<p>The construct contains the coding sequence of ADTZ. ADTZ is also called aflatoxin oxidase (AFO), is the first enzyme identified to be able to degrade AFB1(1). It can be isolated from intracellular extracts and show a strong affinity with AFB1. As a potential degradation enzyme candidate in our project. In order to express soluble ADTZ in E.coli,the DNA coding ADTZ was inserted into the vector pMAL-c5x to produce the fusion protein of maltose-binding protein (MBP) and ADTZ.</p>
 +
<h3>Part:BBa_K2631001</h3>
 +
<p>BD-ScFv2-pGAL1-eYFP</p>
 +
<p>This construct base on the IGEM parts (BBa_K2247009) contains an anti-AFB1 single chain variable fragments (ScFv2) targeting different affinity sites of AFB1 were fused with DNA binding domain (BD) , and ADH1 terminator (transcription terminator for alcohol dehydrogenase 1). We put another ADH1 terminator, the GAL1 promoter (inducible promoter, regulated by Gal4 in yeast, is used as the promoter in a standard yeast-two-hybrid system) cloned from S. cerevisiae (Johnston M et al, 1984) and an eYFP (enhanced YFP mutated from Aequorea Victoria GFP protein) downstream from the ScFv2 in the BamHI site of the vector (Biteen J S et al, 2008). This part, together with AD-ScFv1 (BBa_K2247008), plays the central role in the AFB1 biosensor system. The presence of AFB1 would draw near the two ScFvs, thus enabling the association of Gal4 AD and BD domains, and activate the EYFP protein, and driving the expression of the reporter gene in the AH109 yeast strain (from Takara). This design is that expression of eYFP under the control of the GAL4 induced promoter it regulates would produce a feedback, making the construct more sensitive to the AFB1 in the environment. eYFP act as a signal of the system are working.</p>
  
<div class="column full_size">
 
<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>
 
<div class="line_divider"></div>
 
<div class="clear extra_space"></div>
 
  
 
 
 
 
<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 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>
 
</html>
 
<groupparts>iGEM18 CIEI-BJ</groupparts>
 
<groupparts>iGEM18 CIEI-BJ</groupparts>
 
<html>
 
<html>
</div>
+
 
  
  

Revision as of 13:28, 11 October 2018

Top

Our team have summited two parts

Part:BBa_K2631000

ADTZ Enzyme

The construct contains the coding sequence of ADTZ. ADTZ is also called aflatoxin oxidase (AFO), is the first enzyme identified to be able to degrade AFB1(1). It can be isolated from intracellular extracts and show a strong affinity with AFB1. As a potential degradation enzyme candidate in our project. In order to express soluble ADTZ in E.coli,the DNA coding ADTZ was inserted into the vector pMAL-c5x to produce the fusion protein of maltose-binding protein (MBP) and ADTZ.

Part:BBa_K2631001

BD-ScFv2-pGAL1-eYFP

This construct base on the IGEM parts (BBa_K2247009) contains an anti-AFB1 single chain variable fragments (ScFv2) targeting different affinity sites of AFB1 were fused with DNA binding domain (BD) , and ADH1 terminator (transcription terminator for alcohol dehydrogenase 1). We put another ADH1 terminator, the GAL1 promoter (inducible promoter, regulated by Gal4 in yeast, is used as the promoter in a standard yeast-two-hybrid system) cloned from S. cerevisiae (Johnston M et al, 1984) and an eYFP (enhanced YFP mutated from Aequorea Victoria GFP protein) downstream from the ScFv2 in the BamHI site of the vector (Biteen J S et al, 2008). This part, together with AD-ScFv1 (BBa_K2247008), plays the central role in the AFB1 biosensor system. The presence of AFB1 would draw near the two ScFvs, thus enabling the association of Gal4 AD and BD domains, and activate the EYFP protein, and driving the expression of the reporter gene in the AH109 yeast strain (from Takara). This design is that expression of eYFP under the control of the GAL4 induced promoter it regulates would produce a feedback, making the construct more sensitive to the AFB1 in the environment. eYFP act as a signal of the system are working.

<groupparts>iGEM18 CIEI-BJ</groupparts>