Difference between revisions of "Team:Waterloo/Parts"

Line 1: Line 1:
−
{{Template:Waterloo}}
+
{{Template:Waterloo/Bootstrap}}
 +
{{Template:Waterloo/style.css}}
 +
{{Template:Waterloo/sidenav.css}}
 
<html>
 
<html>
 +
<head>
  
 +
  <script type="text/javascript" src="https://2016.igem.org/Template:Waterloo/angular?action=raw&ctype=text/javascript"></script>
 +
  <script type="text/javascript" src="https://2016.igem.org/Template:Waterloo/app?action=raw&ctype=text/javascript"></script>
 +
  <script type="text/javascript" src="https://2016.igem.org/Template:Waterloo/nav?action=raw&ctype=text/javascript"></script>
 +
  <script type="text/javascript" src="https://2016.igem.org/Template:Waterloo/modernizr?action=raw&ctype=text/javascript"></script>
  
 +
  <script type="text/javascript" src="https://2016.igem.org/Template:Waterloo/sidebar?action=raw&ctype=text/javascript"></script>
 +
  <script type="text/javascript" src="https://2016.igem.org/Team:Waterloo/bootstrapmin?action=raw&ctype=text/javascript"></script>
 +
  <script type="text/javascript" src="https://2016.igem.org/Template:Waterloo/jquery?action=raw&ctype=text/javascript"></script>
 +
  <script type="text/javascript" src="https://2016.igem.org/Template:Waterloo/jquery-color?action=raw&ctype=text/javascript"></script>
 +
</head>
 +
<div ng-app="waterloo">
 +
<header >
 +
<div class="cd-auto-hide-header" ng-mouseleave="hider(); toggleclicked()"  ng-controller="nav">
  
 +
  <nav class="cd-primary-nav">
 +
    <a href="#cd-navigation" class="nav-trigger">
 +
      <span>
 +
        <em aria-hidden="true"></em>
 +
        Menu
 +
      </span>
 +
    </a>
 +
    <!-- .nav-trigger -->
  
 +
    <ul id="cd-navigation">
 +
      <li><a href="#" ng-click="clickety=true"
 +
      ng-mouseover="subnav='project'">PROJECT</a></li>
 +
      <li><a href="#" ng-click="clickety=true" ng-mouseover="subnav='project'">{{clickety}}</a></li>
 +
      <li><a href="#" ng-click="clickety=true" ng-mouseover="subnav='design'">BLUEPRINT</a></li>
 +
      <li><a href="#" ng-click="clickety=true" ng-mouseover="subnav='results'">RESULTS</a></li>
 +
      <li><a href="#" ng-click="clickety=true" ng-mouseover="subnav='lab'">LAB</a></li>
 +
      <li><a href="#" ng-click="clickety=true" ng-mouseover="subnav='practices'">POLICY</a></li>
 +
      <li><a href="#" ng-click="clickety=true" ng-mouseover="subnav='team'">TEAM</a></li>
 +
    </ul>
 +
  </nav>
 +
  <!-- .cd-primary-nav -->
  
 +
  <nav class="cd-secondary-nav" id="projecttab" ng-show="subnav=='project'">
 +
    <ul>
 +
      <li><a href="/Team:Waterloo/Description">Description</a></li>
 +
      <li><a href="/Team:Waterloo/Design">Design</a></li>
 +
      <li><a href="/Team:Waterloo/Requirements">Requirements</a></li>
 +
    </ul>
 +
  </nav>
 +
  <!-- .cd-secondary-nav -->
 +
  <nav class="cd-secondary-nav" id="designtab" ng-show="subnav == 'design'">
 +
    <ul>
 +
      <li><a href="/Team:Waterloo/InDepthDesign/HowItWorks">How It Works</a></li>
 +
              <li><a href="/Team:Waterloo/Software">Premature Stop Codon</a></li>
 +
              <li><a href="/Team:Waterloo/InDepthDesign/PromoterSelection">Promoter Selection</a></li>
 +
              <li><a href="/Team:Waterloo/InDepthDesign/PromoterSelection">Gene Retention Model</a></li>
 +
              <li><a href="/Team:Waterloo/Model">Aggregation Model</a></li>
 +
              <li><a href="/Team:Waterloo/InDepthDesign/Crispr">Aggregation Model</a></li>
 +
    </ul>
 +
  </nav>
 +
  <!-- .cd-secondary-nav -->
 +
  <nav class="cd-secondary-nav" id="resultstab" ng-show="subnav == 'results'">
 +
    <ul>
 +
<li><a href="https://2016.igem.org/Team:Waterloo/Proof">Proof Of Concept</a></li>
 +
              <li><a href="/Team:Waterloo/Results/PlasmidLoss">Gene Retention</a></li>
 +
              <li><a href="/Team:Waterloo/Results/PromoterAnalysis">Promoter Analysis</a></li>
  
−
<div class="column full_size">
+
    </ul>
−
 
+
  </nav>
−
 
+
  <!-- .cd-secondary-nav -->
−
<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>
+
  <nav class="cd-secondary-nav" id="labtab" ng-show="subnav == 'lab'">
−
<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>
+
    <ul>
−
 
+
      <li><a href="/Team:Waterloo/Parts">Parts</a></li>
 +
                <li><a href="/Team:Waterloo/Experiments">Protocols</a></li>
 +
                <li><a href="/Team:Waterloo/Notebook">Notebook</a></li>
 +
                <li><a href="/Team:Waterloo/Safety">Safety</a></li>
 +
    </ul>
 +
  </nav>
 +
  <!-- .cd-secondary-nav -->
 +
  <nav class="cd-secondary-nav" id="practices" ng-show="subnav == 'practices'">
 +
    <ul>
 +
      <li><a href="/Team:Waterloo/HP/Silver">Silver</a></li>
 +
      <li><a href="/Team:Waterloo/HP/Gold">Gold</a></li>
 +
      <li><a href="/Team:Waterloo/Engagement">Overview</a></li>
 +
      <li><a href="/Team:Waterloo/Engagement/Gender_Equity">Gender Equity</a></li>
 +
      <li><a href="/Team:Waterloo/Engagement/Ethics">Ethics</a></li>
 +
      <li><a href="/Team:Waterloo/Engagement/Collaboration">Collaboration</a></li>
 +
      <li><a href="/Team:Waterloo/Engagement/Openness">Openness</a></li>
 +
      <li><a href="/Team:Waterloo/Integrated_Practices">Overview</a></li>
 +
      <li><a href="/Team:Waterloo/Integrated_Practices/Open_Science">Open Science</a></li>
 +
      <li><a href="/Team:Waterloo/Integrated_Practices/Networks">Networks</a></li>
 +
             
 +
    </ul>
 +
  </nav>
 +
  <!-- .cd-secondary-nav -->
 +
  <nav class="cd-secondary-nav" id="teamtab" ng-show="subnav == 'team'">
 +
    <ul>
 +
      <li><a href="/Team:Waterloo/Team">Our Team</a></li>
 +
            <li><a href="/Team:Waterloo/Attributions">Attributions</a></li>
 +
            <li><a href="/Team:Waterloo/Sponsors">Sponsors</a></li>
 +
            <li><a href="/Team:Waterloo/Collaborations">Collaboration</a></li>
 +
    </ul>
 +
  </nav>
 +
  <!-- .cd-secondary-nav -->
  
 
</div>
 
</div>
−
 
+
<!-- .cd-auto-hide-header -->
−
 
+
</header>
−
 
+
<div ng-controller="protocols" ng-cloak>
−
 
+
        <div class="header" ng-include="'../HomePage/Waterloo_Header.html'"></div>
−
 
+
    <div class="protocol-page">
−
<div class="column half_size">
+
   
−
<div class="highlight">
+
<div class="col-lg-4">
−
<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 class="wcontent-protocol">
−
</div>
+
<div class="wcontent-title">
−
</div>
+
<i>Part</i>
−
 
+
</div>  
−
 
+
<div class="wcontent">
−
 
+
<a href="" ng-click="active='inoculation'">Inoculating liquid cultures</a>
−
 
+
</div>  
−
<div class="column half_size">
+
</div>
−
 
+
<div class="wcontent-protocol">
−
<h5>Adding parts to the registry</h5>
+
<div class="wcontent-title">
−
<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>
+
<i>Biobrick</i>
−
<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="wcontent">
−
 
+
−
 
+
</div>  
−
 
+
</div>
−
 
+
<div class="wcontent-protocol">
−
 
+
<div class="wcontent-title">
−
<div class="column half_size">
+
<i>Yeast</i>
−
 
+
</div>
−
<h5>What information do I need to start putting my parts on the Registry?</h5>
+
<div class="wcontent">
−
<p>The information needed to initially create a part on the Registry is:</p>
+
−
<ul>
+
</div>  
−
<li>Part Name</li>
+
</div>
−
<li>Part type</li>
+
</div>
−
<li>Creator</li>
+
<div class="col-lg-8">
−
<li>Sequence</li>
+
<div class="wcontent-box" id="inoculation" ng-show="active == 'inoculation'">
−
<li>Short Description (60 characters on what the DNA does)</li>
+
<div class="wcontent-title">
−
<li>Long Description (Longer description of what the DNA does)</li>
+
Inoculating Liquid Culture
−
<li>Design considerations</li>
+
</div>
−
</ul>
+
<div class="wcontent">
−
 
+
<ol>
−
<p>
+
<li>
−
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>
+
Asceptically pipette 5mL sterile liquid broth into a test tube. If there are no large pipette tips able to transfer 5mL of liquid broth, use a fresh falcon tube to measure.
−
 
+
</li>
−
</div>
+
<li>
−
 
+
Add appropriate antibiotic, if required, to desired concentration using a pipette. You will have to tilt the test tube so that the broth is close enough to the top of the tube that you can add the antibiotic to the broth. Dropping it in won’t work because you will typically be adding ~2.5mL and the drop will be too small to fall.
−
 
+
</li>
−
<div class="column half_size">
+
<li>
−
 
+
It is recommended that you make a “mastermix” with broth and antibiotics in it when you have many tubes that require the same antibiotic.
−
<h5>Inspiration</h5>
+
</li>
−
<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>
+
</ol>
−
 
+
</div>
−
<p> You can also take a look at how other teams have documented their parts in their wiki:</p>
+
</div>
−
<ul>
+
<div class="wcontent-box" ng-show="active=='inoculation'"></div>
−
<li><a href="https://2014.igem.org/Team:MIT/Parts"> 2014 MIT </a></li>
+
</div>
−
<li><a href="https://2014.igem.org/Team:Heidelberg/Parts"> 2014 Heidelberg</a></li>
+
    </div>
−
<li><a href="https://2014.igem.org/Team:Tokyo_Tech/Parts">2014 Tokyo Tech</a></li>
+
</div>
−
</ul>
+
−
</div>
+
−
 
+
−
<div class="column full_size">
+
−
<h5>Part Table </h5>
+
−
<div class="highlight">
+
−
 
+
−
 
+
−
</html>
+
−
<groupparts>iGEM2016 Example</groupparts>
+
−
<html>
+
−
</div>
+
−
</div>
+
−
 
+
−
 
+
−
 
+
−
 
+
 
</html>
 
</html>

Revision as of 19:04, 15 October 2016

Part
Inoculating liquid cultures
Biobrick
Yeast
Inoculating Liquid Culture
  1. Asceptically pipette 5mL sterile liquid broth into a test tube. If there are no large pipette tips able to transfer 5mL of liquid broth, use a fresh falcon tube to measure.
  2. Add appropriate antibiotic, if required, to desired concentration using a pipette. You will have to tilt the test tube so that the broth is close enough to the top of the tube that you can add the antibiotic to the broth. Dropping it in won’t work because you will typically be adding ~2.5mL and the drop will be too small to fall.
  3. It is recommended that you make a “mastermix” with broth and antibiotics in it when you have many tubes that require the same antibiotic.