Difference between revisions of "Team:Tokyo-NoKoGen/Parts"

Line 85: Line 85:
 
   <div id="main">
 
   <div id="main">
 
         <div id="box1">
 
         <div id="box1">
−
          <h2>Introduction</h2>
+
−
             
+
<h2> Part Documentation</h2>
−
<h2> Team Project Descriptions </h2>
+
−
<h4>-Background-</h4>
+
−
<p> Do you know serious pest damages that is harmful to human house and buildings…?<br>
+
−
<p>The criminal is one of the flagitious vermin….termites.</p>
+
−
<p>Termites are insects that feed on wood and paper, and eat like pillars of houses or books. There are a lot of  pesticides developed to exterminate termites. However, many of the pesticides against termites is an organophosphorus agent which has an immediate effect to the individual, while has a negative effect on the human body.</p>
+
−
<p>To solve this problem of pesticides, NoKogen aim to engineer new termites extermination system in iGEM project. </p>
+
  
−
<h4>-Object-</h4>
+
<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> We have two objectives to realize our project.<br>
+
<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>
−
      ・Exterminate termite in slow-acting method on a long-term basis<br>
+
−
      ・Create a new pesticide which is not harmful to man  </p>
+
  
−
<h4>-Method-</h4>
 
−
<p> To achieve these objective, we are engineering the E. coli which produce poison against termites and work in termite’s guts.</p>
 
−
<p> In our project, we focused on the two properties of termites.<br>
 
−
First, we  became aware of that cockroaches and termites are the same order and both of them use trehalose as the primary energy source. <br>
 
−
Actually, NoKoGen engineered E. coli which has ability to kill cockroaches. So we thought that we can apply part of the method of previous project to exterminate termites. <br>
 
−
In concrete method, we are planning to use 3,3-diketotrehalose.  it is an inhibitor of trehalase which converts trehalose to glucose.
 
−
Cockroach and termites digested carbohydrates and metabolized to trehalose.
 
−
Trehalose stored in the blood and is taken up by cells additionally converts trehalose to glucose.
 
−
3,3-diketotrehalose is produced by the enzymatic reaction of glucose 3 dehydrogenase (G3DH).<br>
 
−
We aim to express the G3DH in E. coli and prevent the trehalase activity by competitive inhibition.
 
−
</p>
 
−
<p> Moreover, we construct OtsA and OtsB which convert glucose to trehalose.<br>
 
−
Many more trehalose is converted to 3,3-diketotrehalose which inhibits termite’s passway.</p>
 
  
−
<p>
+
<div class="highlightBox">
−
Second properties of termites is that termites carry and lick their eggs.<br>
+
<h4>Note</h4>
−
Termites recognize their egg as spherical material has a diameter of 0.5 mm  and pheromone.
+
<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>
−
Based on this feature of termites, we try to make the pseudo-eggs to use the habit.<br>
+
</div>
−
We are planning to make pseudo-eggs with LB agar which is cut to the spherical  and engineered E. coli in it.
+
−
We will treat this material as pseudo egg and apply the Lysozyme as termite’s pheromone so that
+
−
termites recognize them as eggs and take them to termites colony.<br>
+
−
We expect that this pseudo-eggs are effective to exterminate termites.</p>
+
−
<p>By these methods based on the feature of termites , we hope that we can achieve our objectives.</p>
+
  
−
<h4>-Biosafety-</h4>
 
−
<p>When we think about practical application of our termite extermination system, there are one big problem. <br>
 
−
It is that we can’t avoid spreading gene recombinant microorganisms to the natural world.
 
−
However, there are many restriction about application of gene recombinant microorganisms not to destroy the balance of nature.<br>
 
−
To solve this problem and protect biosafety standards, we are planning to introduce bacteriolysis system in our project. <br>
 
−
Our target, termites usually form colonies around dark and shadowy area, like under the floor.
 
−
Inversely, our termites extermination system has no need to work in some places which are exposed to direct sunlight. So we are looking for some systems which can induce bacteriolysis to our engineered E.coli under white light or UV light.</p>
 
  
−
<h4>-Human practice-</h4>
 
−
<p>
 
−
Medical drugs, cosmetics, genetically modified foods, detergents, and also pesticides….our everyday life is supported by cutting-edge biotechnology, but few people realize what you really use.<br>
 
−
Tokyo-Nokogen is has some plans to spread some tips and knowledges about bioengineering and biotechnology.<br>
 
−
One of our plan is educational activity. We have already had a small class to teach biotechnology familiar to the students  in the high-school. Also we asked them what kind of device they wanted  to create. There were some interesting ideas for us.<br>
 
−
Also, we are planning to take a survey to the people at large in Japan and other countries. </p>
 
−
<p>We expect that our survey will be one of a chance for people to take an interest in biotechnology. </p>
 
  
 +
<h4>Adding parts to the registry</h4>
 +
<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>
  
−
       
 
  
−
 
+
<h4>What information do I need to start putting my parts on the Registry?</h4>
−
<h4>==============Default Wiki Page ===============</h4>
+
<p>The information needed to initially create a part on the Registry is:</p>
−
<p> Please read the following pages:</p>
+
 
<ul>
 
<ul>
−
<li> <a href="https://2015.igem.org/Requirements">Requirements page </a> </li>
+
<li>Part Name</li>
−
<li> <a href="https://2015.igem.org/Wiki_How-To">Wiki Requirements page</a></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>
 
</ul>
  
−
<div class="highlightBox">
+
<p>
−
<h4> Styling your wiki </h4>
+
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>
−
<p>You may style this page as you like or you can simply leave the style as it is. You can easily keep the styling and edit the content of these default wiki pages with your project information and completely fulfill the requirement to document your project.</p>
+
−
<p>While you may not win Best Wiki with this styling, your team is still eligible for all other awards. This default wiki meets the requirements, it improves navigability and ease of use for visitors, and you should not feel it is necessary to style beyond what has been provided.</p>
+
−
</div>
+
  
−
<h4> Editing your wiki </h4>
 
−
<p>On this page you can document your project, introduce your team members, document your progress and share your iGEM experience with the rest of the world! </p>
 
−
<p> <a href="https://2015.igem.org/wiki/index.php?title=Team:Tokyo-NoKoGen&action=edit"> Click here to edit this page! </a></p>
 
−
<p>See tips on how to edit your wiki on the <a href="https://2015.igem.org/TemplatesforTeams_Code_Documentation">Template Documentation</a> page.</p>
 
  
  
−
<h4>Templates </h4>
 
−
<p> This year we have created templates for teams to use freely. More information on how to use and edit the templates can be found on the
 
−
<a href="https://2015.igem.org/TemplatesforTeams_Code_Documentation">Template Documentation </a> page.</p>
 
  
  
−
<h4>Tips</h4>
+
 
−
<p>This wiki will be your team’s first interaction with the rest of the world, so here are a few tips to help you get started: </p>
+
<h4>Inspiration</h4>
 +
<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>
 
<ul>
−
<li>State your accomplishments! Tell people what you have achieved from the start. </li>
+
<li><a href="https://2014.igem.org/Team:MIT/Parts"> 2014 MIT </a></li>
−
<li>Be clear about what you are doing and how you plan to do this.</li>
+
<li><a href="https://2014.igem.org/Team:Heidelberg/Parts"> 2014 Heidelberg</a></li>
−
<li>You have a global audience! Consider the different backgrounds that your users come from.</li>
+
<li><a href="https://2014.igem.org/Team:Tokyo_Tech/Parts">2014 Tokyo Tech</a></li>
−
<li>Make sure information is easy to find; nothing should be more than 3 clicks away.  </li>
+
</ul>
−
<li>Avoid using very small fonts and low contrast colors; information should be easy to read.  </li>
+
−
<li>Start documenting your project as early as possible; don’t leave anything to the last minute before the Wiki Freeze. For a complete list of deadlines visit the <a href="https://2015.igem.org/Calendar_of_Events">iGEM 2015 calendar</a> </li>
+
−
<li>Have lots of fun! </li>
+
−
</ul>  
+
  
  
−
</div>
+
 
 +
<h4>Part Table </h4>
 +
</html>
 +
<groupparts>iGEM015 Example</groupparts>
  
 
         </div>
 
         </div>
  
 +
 +
 +
 +
 +
 +
</div>
  
  
Line 202: Line 166:
 
     width:100%;
 
     width:100%;
 
　　margin-left:300px ;
 
　　margin-left:300px ;
−
     bottom:-3000px;
+
     bottom:-1000px;
 
         }
 
         }
  

Revision as of 15:07, 27 August 2015

　

Part Documentation

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 <groupparts> tag (see below) will generate a table with all of the parts that your team adds to your team sandbox.

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.

Note

Note that parts must be documented on the Registry. This page serves to showcase 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.

Adding parts to the registry

You can add parts to the Registry at our Add a Part to the Registry link.

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 do 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.)

What information do I need to start putting my parts on the Registry?

The information needed to initially create a part on the Registry is:

  • Part Name
  • Part type
  • Creator
  • Sequence
  • Short Description (60 characters on what the DNA does)
  • Long Description (Longer description of what the DNA does)
  • Design considerations

We encourage you to put up much more 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.

Inspiration

We have a created a collection of well documented parts that can help you get started.

You can also take a look at how other teams have documented their parts in their wiki:

Part Table

<groupparts>iGEM015 Example</groupparts> 

       </div>




</div>


<style> div#wrapper2 { width:80%; text-align:center; position:relative; min-height:100%; margin-left:auto; margin-right:auto; } 


div#footer {
    position:absolute;
    width:100%;

　　margin-left:300px ; 

    bottom:-1000px;
        }



div#footer img {
    width:200px;
        }

p { 

    font-size:16px;
    font-family:Georgia;
    line-height:2; 
 }

h2 { 

    font-size:20px;
    font-family:fantasy;
    text-decoration:none;
  }
</style>


<body>

</body>


</html>