Difference between revisions of "Team:UiOslo Norway/Parts"

(Prototype team page)
 
 
(23 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
{{UiOslo_Norway}}
 
{{UiOslo_Norway}}
 +
 
<html>
 
<html>
 +
<h1 class="h1-font-other">Biological parts</h1>
 +
</html>
 +
<groupparts>iGEM17 UiOslo_Norway</groupparts>
  
 
+
<html>
 
+
<div class="padding-right padding-left">
 
+
We used CYC1 (<a href='http://parts.igem.org/Part:BBa_K2110000'>BBa_K2110000</a>) as the terminator for our composite part.
 
+
 
+
<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>
  
 +
<div class="padding-right padding-left">
 +
As few previous teams have done any work on <i>Schizosaccharomyces Pombe</i>, there are few parts in the registry that have been documented as useful for this yeast species. We wanted to design and document a system to express GFP in <i>S. Pombe</i>, which meant that we had to design and test parts specifically for this.
 +
<br><br>
 +
NMT1 was chosen as the promoter of choice as it's the most commonly used expression system in <i>S. Pombe</i>. One of our supervisors has a lot of experience with this system, which we also considered to be beneficial as it would make it easier to troubleshoot problems. This is the background for why we elected to use this particular sequence.<br><br>
  
 +
We elected to use sfGFP as the fluorescent protein of choice as this is a more stably folded form of GFP, and we wanted to ensure that the protein we used wouldn't be damaged by high light intensity. None of the sfGFP-sequences we found in the parts registry had been optimized for use in <i>S. Pombe</i>, so we decided that making a version of sfGFP specifically for our organism would be a good choice. <br><br>
  
 +
Like with NMT1, CYC1 was chosen as terminator because one of our supervisors had experience with using it in expression systems, and thus a natural sequence of choice. <br><br>
  
 +
Combining all of these, we created our composite part, which was made with the intention of cloning it into the <a href="https://www.addgene.org/vector-database/3250/">pJK148 yeast expression vector</a>as well as into the pSB1C3 submission vector.
 +
<br><br>
  
<div class="column half_size">
+
While doing the parts design and comparing our planned parts to existing sequences, <a href="https://github.com/caniko2/iGEM-Tools">we made a script that allowed us to search through the annual parts distributions for parts with particular names or properties.</a>This sped up the process of figuring out if our parts were unique or had already been submitted greatly, and we are providing this as we believe this may be useful for future teams as well.<br>
<div class="highlight">
+
<h5>Note</h5>
+
<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="column half_size">
 
 
<h5>Adding parts to the registry</h5>
 
<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>
 
</div>
  
  
 
 
 
<div class="column half_size">
 
 
<h5>What information do I need to start putting my parts on the Registry?</h5>
 
<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="column half_size">
 
 
<h5>Inspiration</h5>
 
<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 class="column full_size">
 
<h5>Part Table </h5>
 
 
<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>
 
 
<div class="highlight">
 
  
  
 
</html>
 
</html>
<groupparts>iGEM17 UiOslo_Norway</groupparts>
 
  
<html>
+
{{UiOslo Norway/footerTemplate}}
</div>
+
</div>
+
 
+
 
+
 
+
 
+
</html>
+

Latest revision as of 23:05, 1 November 2017


Biological parts

<groupparts>iGEM17 UiOslo_Norway</groupparts>

We used CYC1 (BBa_K2110000) as the terminator for our composite part.
As few previous teams have done any work on Schizosaccharomyces Pombe, there are few parts in the registry that have been documented as useful for this yeast species. We wanted to design and document a system to express GFP in S. Pombe, which meant that we had to design and test parts specifically for this.

NMT1 was chosen as the promoter of choice as it's the most commonly used expression system in S. Pombe. One of our supervisors has a lot of experience with this system, which we also considered to be beneficial as it would make it easier to troubleshoot problems. This is the background for why we elected to use this particular sequence.

We elected to use sfGFP as the fluorescent protein of choice as this is a more stably folded form of GFP, and we wanted to ensure that the protein we used wouldn't be damaged by high light intensity. None of the sfGFP-sequences we found in the parts registry had been optimized for use in S. Pombe, so we decided that making a version of sfGFP specifically for our organism would be a good choice.

Like with NMT1, CYC1 was chosen as terminator because one of our supervisors had experience with using it in expression systems, and thus a natural sequence of choice.

Combining all of these, we created our composite part, which was made with the intention of cloning it into the pJK148 yeast expression vectoras well as into the pSB1C3 submission vector.

While doing the parts design and comparing our planned parts to existing sequences, we made a script that allowed us to search through the annual parts distributions for parts with particular names or properties.This sped up the process of figuring out if our parts were unique or had already been submitted greatly, and we are providing this as we believe this may be useful for future teams as well.