Difference between revisions of "Team:East Chapel Hill/Parts"

(Prototype team page)
 
 
(25 intermediate revisions by 3 users not shown)
Line 3: Line 3:
  
  
−
<div class="column full_size">
+
<head>
−
<h1>Parts</h1>
+
<meta name="viewport" content="width=device-width, initial-scale=1">
−
<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>
+
<style>
−
<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>
+
body {
−
</div>
+
    font-family: "Lato", sans-serif;
 +
}
 +
<head>
 +
<meta name="viewport" content="width=device-width, initial-scale=1">
 +
<style>
 +
body {
 +
  margin: 0px;
 +
  font-family: Arial, Helvetica, sans-serif;
 +
}
  
−
<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>
+
.navbar {
−
<div class="line_divider"></div>
+
  overflow: hidden;
−
<div class="clear extra_space"></div>
+
  background-color: #A9A9A9;
 +
  position: fixed;
 +
  bottom: 0;
 +
  width:40%;
 +
  height:1%;
 +
  left: 31%;
 +
  display: flex;
 +
  align-items: center;
 +
  justify-content: center;
 +
 
 +
}
  
 +
.navbar a {
 +
  float: left;
 +
  display: block;
 +
  color: #f2f2f2;
 +
  text-align: center;
 +
  padding: 14px 16px;
 +
  text-decoration: none;
 +
  font-size: 17px;
 +
}
  
 +
.navbar a:hover {
 +
  background: #ADD8E6;
 +
  color: black;
 +
}
  
 +
.navbar a.active {
 +
  background-color: #ADD8E6;
 +
  color: white;
 +
}
  
 +
.main {
 +
  padding: 16px;
 +
  margin-bottom: 0px;
 +
}
 +
</style>
 +
</head>
 +
<body>
  
−
<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>
 
  
  
 +
<!-- Define p2 type -->
 +
<style>
 +
p2 {
 +
    display: block;
 +
    margin-top: 1em;
 +
    margin-bottom: 1em;
 +
    margin-left: 8em;
 +
    margin-right: 8em;
 +
}
 +
</style>
 +
<!-- Define horizontal bar type -->
 +
<style>
 +
hr {
 +
border: 2px solid;
 +
margin-right: 80px;
 +
margin-left:80px;
 +
}
 +
</style>
  
 +
<!-- Define h2 -->
 +
<style>
 +
h2 {
 +
  margin-top: 1em;
 +
            margin-bottom: 1em;
 +
            margin-left: 6em;
 +
            margin-right: 6em;
 +
            text-align: left;
 +
                font-size: 20px;
 +
}
 +
</style>
  
 
<div class="column full_size">
 
<div class="column full_size">
 +
<h1>Parts</h1>
 +
<p2 style= "font-size: 18-x;">
 +
<b>BBa_K2843000</b>
 +
</p2>
 +
<center>
 +
<img src="https://static.igem.org/mediawiki/2018/f/f1/T--East_Chapel_Hill--PROMOTER.png"</img>
 +
</center>
 +
<p2 style= "font-size: 18-x;"> This part is an improvement of the 2017 East Chapel Hill iGem "CHOP" operon. At fluoride concentrations of 2uM and above, the <i>delta</i>-<i>CRCB E. coli</i> strain (strain JW0619-1 from the Yale Coli Genetics Stock Center) will grow on chloramphenicol. This vector is designed with Xhol cutting sites so one may easily remove and replace different segments of the operon to screen for combinations of riboswitch and promoter with highest effectivity.
 +
<br><br>
 +
To summarize, here is how this part functions in the presence of fluoride:
 +
<br> 1. <I> delta</I>-<I>CRCB E. coli</I> accumulates fluoride intracellularly due to the lack of the fluoride efflux channel.
 +
<br> 2. Fluoride binds to the fluoride riboswitch and activates the chloramphenicol acetyltransferase enzyme, which allows for bacterial growth on plates that contain the antibiotic chloramphenicol.
 +
</p2>
  
−
<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 East_Chapel_Hill</groupparts>
 
−
<html>
 
−
</div>
 
  
 +
<p2 style= "font-size: 24-x;">
 +
<b>BBa_K2843002 </b></p2>
 +
<center>
 +
<img src="https://static.igem.org/mediawiki/2018/f/fd/T--East_Chapel_Hill--WITHFRS1.png"</img>
 +
</center>
  
 +
<p2 style= "font-size: 18-x;">
 +
This is BBa_K2843002 operon with the "Fluoride Binding Mutant", which is a mutant of the fluoride RBS. This served as a control for our experiments because if there is growth of <I> delta</I>-<I>CRCB E. coli </I> on the chloramphenicol plates than this indicates that growth of<i> delta</i>-<i>CRCB</i> is not entirely dependent only on the presence of fluoride.</p2>
  
  
 
</html>
 
</html>

Latest revision as of 02:53, 18 October 2018

East Chapel Hill

Parts

BBa_K2843000
This part is an improvement of the 2017 East Chapel Hill iGem "CHOP" operon. At fluoride concentrations of 2uM and above, the delta-CRCB E. coli strain (strain JW0619-1 from the Yale Coli Genetics Stock Center) will grow on chloramphenicol. This vector is designed with Xhol cutting sites so one may easily remove and replace different segments of the operon to screen for combinations of riboswitch and promoter with highest effectivity.

To summarize, here is how this part functions in the presence of fluoride:
1. delta-CRCB E. coli accumulates fluoride intracellularly due to the lack of the fluoride efflux channel.
2. Fluoride binds to the fluoride riboswitch and activates the chloramphenicol acetyltransferase enzyme, which allows for bacterial growth on plates that contain the antibiotic chloramphenicol. BBa_K2843002
This is BBa_K2843002 operon with the "Fluoride Binding Mutant", which is a mutant of the fluoride RBS. This served as a control for our experiments because if there is growth of delta-CRCB E. coli on the chloramphenicol plates than this indicates that growth of delta-CRCB is not entirely dependent only on the presence of fluoride.