Team:UT-Tokyo-Software/Safety

From 2012.igem.org

(Difference between revisions)
 
(8 intermediate revisions not shown)
Line 1: Line 1:
 +
{{:Team:UT-Tokyo-Software/Template}}
<html>
<html>
<head>
<head>
-
<title>UT-Tokyo-Software</title>
+
<title>Safety</title>
-
<style type="text/css">
+
-
.firstHeading{
+
-
  display: none;
+
-
}
+
-
 
+
-
a:link {
+
-
color: #6699ff
+
-
text-decoration: none;
+
-
}
+
-
a:visited {
+
-
  color: #6699ff
+
-
  text-decoration: none;
+
-
}
+
-
a:active {
+
-
color: #6699cc
+
-
}
+
-
a:hover {
+
-
  color: #6699cc
+
-
}
+
-
 
+
-
#catlinks{
+
-
  display:none;
+
-
}
+
-
div#globalWrapper{
+
-
  font-size: 13px;
+
-
}
+
-
div#content{
+
-
  line-height: 1.7;
+
-
}
+
-
h1, h2, h3{
+
-
  line-height: 1.5em;
+
-
}
+
-
body {
+
-
  font-family:'ヒラギノ角ゴ Pro W3','Hiragino Kaku Gothic Pro','メイリオ',Meiryo,'MS Pゴシック',sans-serif;
+
-
  letter-spacing: 0;
+
-
}
+
-
#honbun{
+
-
  width:830px;
+
-
}
+
-
header{
+
-
  width:800px;
+
-
  float:top; margin:20px;
+
-
}
+
-
menuu{
+
-
  width:150px;
+
-
  float:left;
+
-
}
+
-
article{
+
-
  width:620px;
+
-
  float:right;
+
-
}
+
-
footer{
+
-
  height:100px;
+
-
  width:800px;
+
-
  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>
+
</head>
</head>
Line 134: Line 9:
<header>
<header>
-
<span style="font:300% 'Courier';">Project description</span><br>
+
<span style="font:300% 'Courier';">Safety</span><br>
-
<span style="font:200% 'Courier';">UT-Tokyo-Software</span>
+
</header>
</header>
-
 
-
<menuu>
 
-
  <div id="wrapper"> 
 
-
    <div id="info"> 
 
-
      <br /> 
 
-
      <div id="positioner"> 
 
-
        <div id="holder"> 
 
-
          <dl class="menu"> 
 
-
            <dt><a href="https://2012.igem.org/Team:UT-Tokyo-Software">Home</a> </dt> 
 
-
          </dl> 
 
-
          <dl class="menu"> 
 
-
            <dt><a href="https://2012.igem.org/Team:UT-Tokyo-Software/Team">Team</a> </dt> 
 
-
<dd> 
 
-
              <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>
<div>
<div>
-
<h2>Background</h2>
+
<h4>1. Would any of your project ideas raise safety issues in terms of
-
The UT-Tokyo-Software team is planning software projects aimed to <b>assist iGEM teams</b>.  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".
+
researcher safety, public safety, or environmental safety?</h4>
-
</div>
+
<p>
-
<br>
+
-
<div>
+
-
 
+
-
<h2>1. Would any of your project ideas raise safety issues in terms of
+
-
researcher safety, public safety, or environmental safety?</h2>
+
-
 
+
No. None of our software projects raise research, public, or
No. None of our software projects raise research, public, or
environmental safety issues.
environmental safety issues.
-
 
+
</p>
-
 
+
<h4>2. Do any of the new BioBrick parts (or devices) that you made this
-
<h2>2. Do any of the new BioBrick parts (or devices) that you made this
+
year raise safety issues?</h4>
-
year raise safety issues?</h2>
+
<p>
-
 
+
No. We do not plan to develop new parts in our projects.
No. We do not plan to develop new parts in our projects.
-
 
+
</p>
-
 
+
<h4>3. Is there a local biosafety group, committee, or review board at our
-
<h2>3. Is there a local biosafety group, committee, or review board at our
+
institution?</h4>
-
institution?</h2>
+
<p>
-
 
+
We do not plan to conduct any wet experiments that involve DNA manipulation.
-
We do not plan to conduct any wet experiments that involve gene manipulation.
+
Our instructors and advisors think our projects do not raise any
-
Our instructors and advisors think our projects does not raise any
+
safety problems.
safety problems.
-
 
+
</p>
-
 
+
<h4>4. Do you have any other ideas to deal with safety issues that could
-
<h2>4. Do you have any other ideas to deal with safety issues that could
+
be useful for future iGEM competitions?</h4>
-
be useful for future iGEM competitions?</h2>
+
<p>
-
 
+
It might be helpful if there are more comprehensive learning materials
It might be helpful if there are more comprehensive learning materials
that promote awareness of biosafety issues.
that promote awareness of biosafety issues.
It would be more desirable if the materials are interactive, as users
It would be more desirable if the materials are interactive, as users
can actively learn with fun.
can actively learn with fun.
 +
</p>
</div>
</div>
</article>
</article>
 +
</div>
</div>
<footer>
<footer>

Latest revision as of 17:03, 18 September 2012

Safety
Safety

1. Would any of your project ideas raise safety issues in terms of researcher safety, public safety, or environmental safety?

No. None of our software projects raise research, public, or environmental safety issues.

2. Do any of the new BioBrick parts (or devices) that you made this year raise safety issues?

No. We do not plan to develop new parts in our projects.

3. Is there a local biosafety group, committee, or review board at our institution?

We do not plan to conduct any wet experiments that involve DNA manipulation. Our instructors and advisors think our projects do not raise any safety problems.

4. Do you have any other ideas to deal with safety issues that could be useful for future iGEM competitions?

It might be helpful if there are more comprehensive learning materials that promote awareness of biosafety issues. It would be more desirable if the materials are interactive, as users can actively learn with fun.