Team:UT-Tokyo-Software

From 2012.igem.org

(Difference between revisions)
Line 1: Line 1:
<html>
<html>
<head>
<head>
-
<title>Project Description</title>
+
<title>UT-Tokyo-Software</title>
<style type="text/css">
<style type="text/css">
.firstHeading{
.firstHeading{
   display: none;
   display: none;
}
}
 +
a:link {
a:link {
color: #6699ff
color: #6699ff
Line 20: Line 21:
   color: #6699cc
   color: #6699cc
}
}
 +
#catlinks{
#catlinks{
   display:none;
   display:none;
Line 43: Line 45:
   float:top; margin:20px;
   float:top; margin:20px;
}
}
-
menu{
+
menuu{
   width:150px;
   width:150px;
   float:left;
   float:left;
Line 55: Line 57:
   width:800px;
   width:800px;
   clear:both;
   clear:both;
 +
}
 +
 +
<!--Menu-->
 +
#positioner
 +
{
 +
  position: relative;
 +
  width: 160px;
 +
  height: 160px;
 +
  margin-left: 10px;
 +
  z-index: 100;
 +
}
 +
#holder
 +
{
 +
  position: absolute;
 +
  width: 150px;
 +
  overflow: hidden;
 +
  border: 0px solid #000;
 +
}
 +
dl.menu
 +
{
 +
  width: 300px;
 +
  float: left;
 +
  margin: -32700px -150px 0 0;
 +
}
 +
dl.menu a
 +
{
 +
  display: block;
 +
  height: 30px;
 +
  color: #000;
 +
  font: normal 12px/28px sans-serif, sans-serif;
 +
  text-decoration: none;
 +
  text-align: center;
 +
}
 +
dl.menu dt
 +
{
 +
  float: left;
 +
  padding: 0;
 +
  margin: 32700px 0 0 0;
 +
  position: relative;
 +
  z-index: 50;
 +
}
 +
dl.menu dt a
 +
{
 +
  background: transparent;
 +
  width: 150px;
 +
}
 +
dl.menu dt a:hover, dl.menu dt a:focus, dl.menu dt a:active
 +
{
 +
  margin-right: 1px;
 +
}
 +
dl.menu dd
 +
{
 +
  float: left;
 +
  padding: 30px 0 0 0;
 +
  margin: -30px 0 0 0;
 +
  position: relative;
 +
  z-index: 10;
 +
}
 +
dl.menu dd a
 +
{
 +
  background: #666;
 +
  width: 150px;
 +
}
 +
 +
dl.menu dd a:hover, dl.menu dd a:focus, dl.menu dd a:active
 +
{
 +
  margin-right: 1px;
 +
  background: #ccc;
 +
  color: #000;
}
}
</style>
</style>
Line 67: Line 138:
</header>
</header>
-
<menu>
+
<menuu>
-
<ul>
+
  <div id="wrapper">
-
<li><a href="https://2012.igem.org/Team:UT-Tokyo-Software">Home</a></li>
+
    <div id="info"> 
-
<li><a href="https://2012.igem.org/Team:UT-Tokyo-Software/Team">Team</a></li>
+
      <br /> 
-
<li><a href="https://igem.org/Team.cgi?year=2012&team_name=UT-Tokyo-Software">Official Team Profile</a></li>
+
      <div id="positioner"> 
-
<li><a href="https://2012.igem.org/Team:UT-Tokyo-Software/Project">Project</a></li>
+
        <div id="holder"> 
-
<li><a href="https://2012.igem.org/Team:UT-Tokyo-Software/Parts">Parts submitted</a></li>
+
          <dl class="menu"> 
-
<li><a href="https://2012.igem.org/Team:UT-Tokyo-Software/Modeling">Modeling</a></li>
+
            <dt><a href="https://2012.igem.org/Team:UT-Tokyo-Software">Home</a> </dt>
-
<li><a href="https://2012.igem.org/Team:UT-Tokyo-Software/Notebook">Notebook</a></li>
+
          </dl> 
-
<li><a href="https://2012.igem.org/Team:UT-Tokyo-Software/Safety">Safety</a></li>
+
          <dl class="menu"> 
-
<li><a href="https://2012.igem.org/Team:UT-Tokyo-Software/Attributions">Attributions</a></li>
+
            <dt><a href="https://2012.igem.org/Team:UT-Tokyo-Software/Team">Team</a> </dt>
-
</ul>
+
<dd>
-
</menu>
+
              <a href="#url">Member</a> 
 +
              <a href="#url">Attribution</a>
 +
            </dd> 
 +
          </dl> 
 +
          <dl class="menu">
 +
            <dt><a href="https://2012.igem.org/Team:UT-Tokyo-Software/Project">Project</a> </dt>
 +
            <dd>
 +
              <a href="#url">Introduction</a>  
 +
              <a href="#url">BIOBRICK</a>  
 +
              <a href="#url">Genetic Network</a> 
 +
              <a href="#url">BIOBRICK Search</a>
 +
  <a href="#url">Team Search</a> 
 +
              <a  href="#url">Download</a>
 +
            </dd> 
 +
          </dl> 
 +
          <dl class="menu">
 +
            <dt><a href="https://2012.igem.org/Team:UT-Tokyo-Software/Notebook">Notebook</a> </dt>  
 +
          </dl> 
 +
          <dl class="menu"> 
 +
            <dt><a href="https://2012.igem.org/Team:UT-Tokyo-Software/Safety">Safety</a> </dt>
 +
          </dl> 
 +
  <dl class="menu"> 
 +
            <dt><a href="#url">Medal Fulfillment</a> </dt>
 +
          </dl> 
 +
        </div>
 +
      </div>
 +
    </div>
 +
  </div>
 +
 
 +
</menuu>
<article>
<article>
Line 105: Line 205:
-
 
+
<!--prev-->
-
 
+
-
 
+
-
 
+
<!-- *** What falls between these lines is the Alert Box!  You can remove it from your pages once you have read and understood the alert *** -->
<!-- *** What falls between these lines is the Alert Box!  You can remove it from your pages once you have read and understood the alert *** -->
<!--
<!--

Revision as of 13:31, 4 September 2012

UT-Tokyo-Software

Project description
UT-Tokyo-Software

Background

The UT-Tokyo-Software team is planning software projects aimed to assist iGEM teams. For many teams, the majority of members are new-comers. Therefore, many of these teams require a substantial amount of time and effort at the beginning of the year to get to know iGEM, after which they will finally be able to start thinking about what they want to do. We believe that if this learning period can be made more efficient, the productivity of teams can be greatly enhanced. Although tutorials and search systems are provided at the iGEM website, we have decided to create our own set of programs that fill in some of the important gaps that we feel are left open at the iGEM sites. Our project consist of two parts: "Tutorial" and "Search".

Tutorial

To make new-comers get used to the iGEM earlier, well-designed educational materials are needed. We're planning to improve on the current official web-based tutorial. As a software project, we’re aiming to make it interactive and enjoyable to help beginners understand iGEM concepts and techniques. The themes included in the planned tutorials are "Biobricks", "Notable past projects", "Genetic networks" and so on.

Search

When building iGEM projects, we have to investigate relevant past projects and Biobrick parts. However the current Biobrick search system implemented in the parts registry displays all the parts containing the search query, and beginners frequently cannot judge which part is usable. The present situation for searching past projects is also difficult, for example because a cross-year search does not exist. To solve these problems, we are developing a new parts and past projects search systems. We are planning to implement an ordering (by popularity, part workability, keyword-relevance etc.) algorithm, a tagging system and a relevance-search which will enable searching, for example, “which is the most popular GFP part?”,or “look up all bioremediation projects which have won a gold prize”,or “are there any projects similar to this?”.