Difference between revisions of "Team:Cardiff Wales/Parts"

Line 31: Line 31:
 
<div class="column full_size">
 
<div class="column full_size">
 
<h1>Parts</h1>
 
<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> Our team added several useful parts to the PhytoBrick registry, all of which are easy to use with either conventional iGEM cloning or using GoldenGate cloning. While we are happy with the parts we have created, we could only submit basic parts due to the iGEM plasmid backbone specifications, which present problems for submission of level 1 parts made with GoldenGate cloning. For this reason, all of our submitted parts are in the pSB1C3 plasmid, and are all individual parts, with the exception of one part, <a href="http://parts.igem.org/wiki/index.php?title=Part:BBa_K2810011">http://parts.igem.org/wiki/index.php?title=Part:BBa_K2810011,</a>, which is a composite part ordered as a gBlock, so didn't need to be assembled using GoldenGate cloning. We were aware of this limitation starting our project, but thought its ease of use and flexibility outweighed the fact that we wouldn't be able to submit level 1 parts. Nevertheless, we have made and tested several composite parts, adding data to existing registry parts, and to our newer ones.</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>
 +
<!--
 +
<groupparts>iGEM18 Cardiff_Wales</groupparts> -->
  
<div class="column full_size">
+
<br><br><br>
<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>
+
<groupparts>iGEM18 Cardiff_Wales</groupparts>
+
<html>
+
</div>
+
 
+
<br><br><br><br><br><br>
+
  
 
<center>
 
<center>

Revision as of 11:04, 26 September 2018

Parts

Our team added several useful parts to the PhytoBrick registry, all of which are easy to use with either conventional iGEM cloning or using GoldenGate cloning. While we are happy with the parts we have created, we could only submit basic parts due to the iGEM plasmid backbone specifications, which present problems for submission of level 1 parts made with GoldenGate cloning. For this reason, all of our submitted parts are in the pSB1C3 plasmid, and are all individual parts, with the exception of one part, http://parts.igem.org/wiki/index.php?title=Part:BBa_K2810011,, which is a composite part ordered as a gBlock, so didn't need to be assembled using GoldenGate cloning. We were aware of this limitation starting our project, but thought its ease of use and flexibility outweighed the fact that we wouldn't be able to submit level 1 parts. Nevertheless, we have made and tested several composite parts, adding data to existing registry parts, and to our newer ones.






Name Type Description Designer Length
BBa_BBa_K2810000 Regulatory WRKY intron for plant-targeted RNAi constructs Geraint Parry 295bp
BBa_BBa_K2810001 Reporter GUS reporter for plant expression Geraint Parry 1817bp
BBa_BBa_K2810002 Regulatory RTBV Vascular Specific Promotor Geraint Parry 759bp
BBa_BBa_K2810003 RNA Full sequence for Myzus persisae BCR3 secreted protein Geraint Parry 257bp
BBa_BBa_K2810004 RNA Complimentary sequence to Myzus persisae BCR3 secreted protein Geraint Parry 257bp
BBa_BBa_K2810005 RNA Coding sequence from 5' region of Myzus persisae BCR3 secreted protein Geraint Parry 102bp
BBa_BBa_K2810006 RNA Complimentary sequence from 5' region of Myzus persisae BCR3 secreted protein Geraint Parry 102bp
BBa_BBa_K2810007 RNA siRNA from 5' region of Myzus persicae SP3 secreted protein Ryan Coates 291bp
BBa_BBa_K2810008 RNA siRNA* from 5' region of Myzus persicae SP3 secreted protein Ryan Coates 291bp
BBa_BBa_K2810009 Reporter mCherry, codon optimised for Nicotiana benthamiana and GoldenGate compatible Ryan Coates 676bp
BBa_BBa_K2810010 Regulatory Regulatory region derived from the ribitol-responsive operon Ryan Coates 169bp
BBa_BBa_K2810011 Composite mCherry under control of the bacterial promoter and terminato Ryan Coates 858bp