Difference between revisions of "Team:NCTU Formosa/Parts"

(Prototype team page)
 
 
(8 intermediate revisions by 3 users not shown)
Line 1: Line 1:
−
{{NCTU_Formosa}}
+
{{NCTU Formosa/Navigation}} {{NCTU Formosa}}
 
<html>
 
<html>
  
 +
<head>
 +
    <meta charset="UTF-8">
 +
    <title>NCTI_Formosa: Parts</title>
 +
    <script src="https://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js"></script>
 +
    <script src="jQueryAssets/jquery-1.11.1.min.js"></script>
 +
    <script src="jQueryAssets/jquery.ui-1.10.4.dialog.min.js"></script>
 +
    <link href="Parts.css" rel="stylesheet" type="text/css">
 +
    <script src="Parts.js" type="text/javascript"></script>
 +
    <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=no, minimum-scale=1.0, maximum-scale=1.0" />
  
 +
    <style>
 +
body {
 +
    margin: 0;
 +
    padding: 0;
 +
    overflow-x: hidden;
 +
    height: 100vh;
 +
}
  
 +
html, body{
 +
overflow-x: hidden !important;
 +
-ms-overflow-x: hidden !important;
 +
}
  
 +
#fut{
 +
background: white;
 +
width: 100vw;
 +
height: 200px;
 +
}
  
  
−
<div class="column full_size">
+
p {
 +
    text-align: justify;
 +
    font-size: 1.3em !important;
 +
    font-family: Arial, sans-serif;
 +
    margin: 10px 0 0;
 +
}
  
−
<h1>Parts</h1>
+
h1{
 +
    border: 0;
 +
}
  
−
<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>
+
h4{
−
<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>
+
    text-align: center;
 +
    margin-top: 0px;
 +
    margin-bottom: 50px !important;
 +
    font-size: 15px;
 +
}
  
 +
h3{
 +
    text-align: center;
 +
    margin-top: 50px;
 +
    margin-bottom: 0px !important;
 +
    font-size: 15px;
 +
}
  
−
</div>
 
  
  
  
 +
@font-face {
 +
  font-family: neo_latina;
 +
  src: url(https://static.igem.org/mediawiki/2017/4/46/Neo-latina-demo-FFP.ttf);
 +
}
  
 +
.subtitle>h6{
 +
    font-family: neo_latina;
 +
    font-size: 3.9em;
 +
    position: relative;
 +
    left: 25px;
 +
    margin-top: 50px;
 +
    margin-bottom: 10px;
 +
    line-height: 1em;
 +
}
  
−
<div class="column half_size">
+
.subtitle>h5{
−
<div class="highlight">
+
    font-family: neo_latina;
−
<h5>Note</h5>
+
    font-size: 1.95em;
−
<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>
+
    position: relative;
−
</div>
+
    left: 50px;
−
</div>
+
    margin-top: -10px;
 +
    margin-bottom: 10px;
 +
    line-height: 1em;
 +
}
  
 +
.latex{
 +
    font-size: 20px;
 +
}
  
 +
.sub_text{
 +
    width:65vw;
 +
    position: relative;
 +
    left: 5vw;
 +
}
  
 +
.sub2_text{
 +
    width:60vw;
 +
    position: relative;
 +
    left: 10vw;
 +
    line-height: 15px;
 +
    margin-bottom: 10px;
 +
}
  
−
<div class="column half_size">
+
.parts_content{
 +
    margin: 0vh 10vw 0vh;
 +
}
  
−
<h5>Adding parts to the registry</h5>
+
#groupparts{
−
<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>
+
margin: auto;
−
<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>
+
    </style>
 +
    <!----------------------------------------------------------------------------->
 +
    <script>
 +
    </script>
 +
    <!----------------------------------------------------------------------------->
  
 +
</head>
  
 +
<body>
 +
    <div class="parts_head"><img src="https://static.igem.org/mediawiki/2017/2/23/Parts_title1.png" width="100%"></div>
 +
    <div class="parts_content">
  
 +
        <div class="subtitle"><h6>Parts</h6></div>
  
 +
        <p>
 +
            &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Our goal is to realize our Parabase system to work in reality and do further applications. In hopes that our system can apply to farmlands, we first attempted to produce antifungal peptides from <i>E. coli</i> in order to cost down to prepare for the mass production in the future. We have selected several peptides from our antifungal database and also by our antifungal peptide prediction system. So far, we have done experiments to prove antifungal function of these peptides.
 +
        </p>
  
−
<div class="column half_size">
+
        <p>
 +
            &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;We have provided a collection of antifungal peptides, including validated peptides and predicted peptides that have been proved by our team. All the new Biobricks have been submitted to the Registry of iGEM.
  
−
<h5>What information do I need to start putting my parts on the Registry?</h5>
+
        </p>
−
<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>
−
 
+
−
 
+
−
<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">
+
  
 +
</body>
  
 
</html>
 
</html>
−
<groupparts>iGEM17 NCTU_Formosa</groupparts>
+
<p class="content-image" style="text-align:center !important;">Table 1. Registry of Standard Biological Parts</p>
 +
<groupparts>iGEM2017 NCTU_Formosa</groupparts>
  
 
<html>
 
<html>
−
</div>
 
−
</div>
 
  
 +
    <div id="fut"></div>
  
 +
</html>
  
−
 
+
{{NCTU_Formosa/Footer}}
−
</html>
+

Latest revision as of 01:02, 2 November 2017

navigation

HOME
TEAM
PROJECT
Description
Design
Experiments
Notebook
InterLab
Contribution
Model
Results
Demonstrate
Improve
Attributions
PARTS
Parts
Basic Parts
Composite Parts
Part Collection
SAFETY
HUMAN PRACTICES
Silver HP
Integrated and Gold
Public Engagement
AWARDS
Applied Design
Entrepreneurship
Hardware
Measurement
Model
Plant
Software
JUDGING FORM
NCTI_Formosa: Parts
Parts

     Our goal is to realize our Parabase system to work in reality and do further applications. In hopes that our system can apply to farmlands, we first attempted to produce antifungal peptides from E. coli in order to cost down to prepare for the mass production in the future. We have selected several peptides from our antifungal database and also by our antifungal peptide prediction system. So far, we have done experiments to prove antifungal function of these peptides.

     We have provided a collection of antifungal peptides, including validated peptides and predicted peptides that have been proved by our team. All the new Biobricks have been submitted to the Registry of iGEM.

Table 1. Registry of Standard Biological Parts

<groupparts>iGEM2017 NCTU_Formosa</groupparts>

Untitled Document