Team:WPI-Worcester/Safety

From 2014.igem.org

(Difference between revisions)
m
 
(19 intermediate revisions not shown)
Line 1: Line 1:
-
<!-- *** What falls between these lines is the Alert Box! You can remove it from your pages once you have read and understood the alert *** -->
+
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en" dir="ltr">
 +
<head>
 +
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
 +
<meta name="generator" content="MediaWiki 1.16.5" />
 +
<link rel="shortcut icon" href="/favicon.ico" />
 +
<link rel="search" type="application/opensearchdescription+xml" href="/wiki/opensearch_desc.php" title="2014.igem.org (en)" />
 +
<link title="Creative Commons" type="application/rdf+xml" href="/wiki/index.php?title=Team:WPI-Worcester&amp;action=creativecommons" rel="meta" />
 +
<link rel="copyright" href="http://creativecommons.org/licenses/by/3.0/" />
 +
<link rel="alternate" type="application/atom+xml" title="2014.igem.org Atom feed" href="/wiki/index.php?title=Special:RecentChanges&amp;feed=atom" /> <title>Team:WPI-Worcester - 2014.igem.org</title>
 +
<style type="text/css" media="screen, projection">/*<![CDATA[*/
 +
@import "/wiki/skins/common/shared.css?270";
 +
@import "/wiki/skins/igem/main.css?270";
 +
/*]]>*/
 +
#contentSub, #footer-box, #catlinks, #search-controls, #p-logo, .printfooter, .firstHeading,.visualClear {display: none;}
 +
</style>
 +
<link rel="stylesheet" type="text/css" media="print" href="/wiki/skins/common/commonPrint.css?270" />
 +
<!--[if lt IE 5.5000]><style type="text/css">@import "/wiki/skins/igem/IE50Fixes.css?270";</style><![endif]-->
 +
<!--[if IE 5.5000]><style type="text/css">@import "/wiki/skins/igem/IE55Fixes.css?270";</style><![endif]-->
 +
<!--[if IE 6]><style type="text/css">@import "/wiki/skins/igem/IE60Fixes.css?270";</style><![endif]-->
 +
<!--[if IE 7]><style type="text/css">@import "/wiki/skins/igem/IE70Fixes.css?270";</style><![endif]-->
 +
<!--[if lt IE 7]><script type="text/javascript" src="/wiki/skins/common/IEFixes.js?270"></script>
 +
<meta http-equiv="imagetoolbar" content="no" /><![endif]-->
 +
 +
<script>
 +
var skin="igem",
 +
stylepath="/wiki/skins",
 +
wgUrlProtocols="http\\:\\/\\/|https\\:\\/\\/|ftp\\:\\/\\/|irc\\:\\/\\/|gopher\\:\\/\\/|telnet\\:\\/\\/|nntp\\:\\/\\/|worldwind\\:\\/\\/|mailto\\:|news\\:|svn\\:\\/\\/",
 +
wgArticlePath="/$1",
 +
wgScriptPath="/wiki",
 +
wgScriptExtension=".php",
 +
wgScript="/wiki/index.php",
 +
wgVariantArticlePath=false,
 +
wgActionPaths={},
 +
wgServer="https://2014.igem.org",
 +
wgCanonicalNamespace="",
 +
wgCanonicalSpecialPageName=false,
 +
wgNamespaceNumber=0,
 +
wgPageName="Team:WPI-Worcester",
 +
wgTitle="Team:WPI-Worcester",
 +
wgAction="view",
 +
wgArticleId=1881,
 +
wgIsArticle=true,
 +
wgUserName=null,
 +
wgUserGroups=null,
 +
wgUserLanguage="en",
 +
wgContentLanguage="en",
 +
wgBreakFrames=false,
 +
wgCurRevisionId=232197,
 +
wgVersion="1.16.5",
 +
wgEnableAPI=true,
 +
wgEnableWriteAPI=true,
 +
wgSeparatorTransformTable=["", ""],
 +
wgDigitTransformTable=["", ""],
 +
wgMainPageTitle="Main Page",
 +
wgFormattedNamespaces={"-2": "Media", "-1": "Special", "0": "", "1": "Talk", "2": "User", "3": "User talk", "4": "2014.igem.org", "5": "2014.igem.org talk", "6": "File", "7": "File talk", "8": "MediaWiki", "9": "MediaWiki talk", "10": "Template", "11": "Template talk", "12": "Help", "13": "Help talk", "14": "Category", "15": "Category talk"},
 +
wgNamespaceIds={"media": -2, "special": -1, "": 0, "talk": 1, "user": 2, "user_talk": 3, "2014.igem.org": 4, "2014.igem.org_talk": 5, "file": 6, "file_talk": 7, "mediawiki": 8, "mediawiki_talk": 9, "template": 10, "template_talk": 11, "help": 12, "help_talk": 13, "category": 14, "category_talk": 15, "image": 6, "image_talk": 7},
 +
wgSiteName="2014.igem.org",
 +
wgCategories=[],
 +
wgMWSuggestTemplate="https://2014.igem.org/wiki/api.php?action=opensearch\x26search={searchTerms}\x26namespace={namespaces}\x26suggest",
 +
wgDBname="2014_igem_org",
 +
wgSearchNamespaces=[0],
 +
wgMWSuggestMessages=["with suggestions", "no suggestions"],
 +
wgRestrictionEdit=[],
 +
wgRestrictionMove=[];
 +
</script>               
 +
<script type="text/javascript" src="/wiki/skins/common/wikibits.js?270"><!-- wikibits js --></script>
 +
<!-- Head Scripts -->
 +
<script src="/wiki/skins/common/ajax.js?270"></script>
 +
<script src="/wiki/skins/common/mwsuggest.js?270"></script>
 +
<script type="text/javascript" src="/wiki/index.php?title=-&amp;action=raw&amp;gen=js&amp;useskin=igem"><!-- site js --></script>
 +
<!-- jQuery Javascript -->
 +
<script type='text/javascript'        src ='/common/jquery-latest.min.js'></script>
 +
<script type='text/javascript'        src ='/common/tablesorter/jquery.tablesorter.min.js'></script>
 +
        <link rel='stylesheet' type='text/css' href='/common/tablesorter/themes/groupparts/style.css' />
 +
        <link rel='stylesheet' type='text/css' href='/common/table_styles.css' />
 +
        <link rel='stylesheet' type='text/css' href='/forum/forum_styles.css' />
 +
<script type='text/javascript'        src ='/forum/forum_scripts.js'></script>
 +
</head>
 +
<body              class="mediawiki  ltr ns-0 ns-subject page-Team_WPI-Worcester">
 +
  <div id="globalWrapper">
-
{{CSS/Main}}
+
    <div id="top-section">
 +
<div id="p-logo">
 +
    <a href="/Main_Page"
 +
      title="Main Page">
 +
    <img src='/wiki/skins/common/images/wiki.jpg'>"
 +
    </a>
 +
</div>  <!-- end p-logo -->
 +
<script type="text/javascript"> if (window.isMSIE55) fixalpha(); </script>
-
<html>
+
<div id="search-controls" class="noprint">
 +
<form action="/Special:Search" id="searchform">
 +
<input id="searchInput" name="search" type="text" title="Search 2014.igem.org [f]" accesskey="f" value="" />
 +
<input type='submit' name="go" class="searchButton" id="searchGoButton" value="Go" title="Go to a page with this exact name if exists" />&nbsp;
 +
      <input type='submit' name="fulltext" class="searchButton" id="mw-searchButton" value="Search" title="Search the pages for this text" />
 +
</form>
 +
</div> <!-- close search controls -->
 +
    </div> <!-- close top-section-->
 +
    <div id="content">
 +
<a name="top" id="top"></a>
 +
<h1 class="firstHeading">Team:WPI-Worcester</h1>
 +
<div id="bodyContent">
 +
<h3 id="siteSub" class='noprint'>From 2014.igem.org</h3>
 +
<div id="contentSub"></div>
 +
<!--
 +
<div id="jump-to-nav">Jump to:                        <a href="#column-one">navigation</a>, <a href="#searchInput">search</a></div>-->
 +
<!-- start content -->
 +
<p>
 +
<style>
 +
a{
 +
color:#AC2B37;
 +
}
-
<!--CSS-->
+
a:hover {
-
<style>
+
color:#AC2B37;
-
body{ margin:0px; }
+
}
-
div#floatbar {
+
 
 +
a:visited{
 +
color:#AC2B37;
 +
}
 +
 
 +
td {
 +
    font-family: Georgia;
 +
    font-size: 10pt;
 +
    vertical-align: top;
 +
    text-align: left;
 +
    padding-right: 10px;
 +
}
 +
 
 +
tr {
 +
    vertical-align: top;
 +
}
 +
 
 +
H3 {
 +
      font-family: Georgia;
 +
      text-transform: none;
 +
      text-decoration: none;
 +
 +
      color: #A9B0B7;
 +
      font-size: 10pt;
 +
    }
 +
 
 +
H4 {
 +
      font-family: Georgia;
 +
      text-transform: uppercase;
 +
      text-decoration: none;
 +
      text-align: left;
 +
      color: #AC2B37;
 +
      font-size: 20pt;
 +
    }
 +
 
 +
 
 +
H8 {
 +
      font-family: Georgia;
 +
      text-transform: none;
 +
      text-decoration: none;
 +
      text-align: left;
 +
      color: #AC2B37;
 +
      font-size: 12pt;
 +
}
 +
 
 +
H9 {
 +
      font-family: Georgia;
 +
      text-transform: none;
 +
      text-decoration: none;
 +
      text-align: left;
 +
      color: #A9B0B7;
 +
      font-size: 16pt;
 +
    }
 +
 
 +
H10 {
 +
          font-family: Georgia;
 +
      text-transform: none;
 +
      text-decoration: none;
 +
      text-align: left;
 +
      color: #AC2B37;
 +
      font-size: 12pt;
 +
 
 +
    }
 +
 
 +
 
 +
img.headshot {
 +
width: 100px;
 +
height: auto;
 +
vertical-align: text-top;
 +
}
 +
 
 +
body {
 +
background: #FFFFFF;
 +
font-family: Arial;
 +
}
 +
 
 +
#tracking_nav
 +
{
 +
margin: 0px 0px 0px 900px;
position: fixed;
position: fixed;
-
right: 10px;
+
color:#bababa;
-
top: 0%;
+
border: 1px solid ##AC2B37;
-
width: 80px;
+
background:##AC2B37;
-
margin-top: 50px
+
font-size: 16pt;
 +
padding: 0px;
 +
line-height: 100%;
}
}
-
div#menubar1{ padding: 24px; border:#999 1 px dashed; }
+
 
-
div#menubar1 > a{
+
#tracking_nav a { color:#ffffff; text-transform: lowercase;font-size: 16pt;}
-
font-family:Arial, Helvetica, sans-serif;
+
#tracking_nav a:hover {background:#bababa;}
-
font-size:17px;
+
 
-
background: #666;
+
#nav li {
-
padding: 15px 10px;
+
color: #ffffff;
-
color:#000;
+
background-color:#A9B0B7;
-
margin-right: 10px;
+
margin: 0 0px;
-
margin-bottom: 5px;
+
float: left;
-
text-decoration:none;
+
position: relative;
-
border-radius:3px;
+
list-style: none;
-
float:left;
+
text-transform:none;
-
transition: background 0.3s ease-in-out 0s, color 0.4s ease-in-out 0s;
+
font-size:12pt;
}
}
-
div#menubar1 > a:hover{
+
 
-
background: #333;
+
/* main level link */
-
color: #FFF;
+
#nav a {
 +
font-weight: bold;
 +
color: #ffffff;
 +
text-decoration: none;
 +
border-left-style: solid;
 +
border-right-style: solid;
 +
        border-color: #000000;
 +
        border-width: 1px;
 +
 
 +
display: block;
 +
padding:  4px 16px;
 +
margin: 0;
 +
}
 +
#nav a:hover {
 +
background-color: #000000;
 +
color: #ffffff;
 +
}
 +
 
 +
/* main level link hover */
 +
#nav .current a, #nav li:hover > a {
 +
color: #ffffff;
 +
background-color: #AC2B37;
 +
}
 +
 
 +
/* sub levels link hover */
 +
#nav ul li:hover a, #nav li:hover li a {
 +
border: solid;
 +
        border-color: #000000;
 +
        border-width: 1px;
 +
background-color: #AC2B37;
 +
color: #ffffff;
 +
}
 +
 
 +
#nav ul a:hover {
 +
background: #fff url(img/gradient.png) repeat-x 0 -100px !important;
 +
color: #AC2B37 !important;
 +
text-shadow: 0 1px 1px rgba(0,0,0, .1);
 +
}
 +
 
 +
/* dropdown */
 +
#nav li:hover > ul {
 +
display: block;
 +
background-color: #fff;
 +
}
 +
 
 +
/* level 2 list */
 +
#nav ul {
 +
display: none;
 +
margin: 0;
 +
padding: 0;
 +
width: 205px;
 +
position: absolute;
 +
top: 70px;
 +
left: 0;
 +
}
 +
 
 +
#nav ul li {
 +
float: none;
 +
margin: 0;
 +
padding: 0;
 +
}
 +
 
 +
#nav ul a {
 +
font-weight: normal;
 +
text-shadow: 0 1px 0 #fff;
 +
}
 +
 
 +
/* clearfix */
 +
#nav:after {
 +
content: ".";
 +
display: block;
 +
clear: both;
 +
visibility: hidden;
 +
line-height: 0;
 +
height: 0;
 +
}
 +
 
 +
#nav {
 +
display: inline-block;
 +
}
 +
 +
html[xmlns] #nav {
 +
display: block;
 +
}
 +
 +
* html #nav {
 +
height: 1%;
 +
}
 +
 
 +
@font-face {
 +
    font-family: HP PSG;
 +
    src: url(HP PSG.eot);
 +
}
 +
 
 +
#menuOverlay {
 +
  position:fixed; /*or  absolute*/
 +
  top:0;
 +
  left:0;
 +
  width:100%:
 +
  height:30px;
 +
  z-index: 999; /* or  greater value */
}
}
-
 
</style>
</style>
-
<!--Float Bar-->
+
<head>
-
<body>
+
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-
<div id="floatbar">
+
<style type="text/css">
-
<a href="https://2014.igem.org/Main_Page"> <img src= "https://static.igem.org/mediawiki/igem.org/6/60/Igemlogo_300px.png" align="right" width="55px"></a>
+
-
</div>
+
-
<!--main content -->
+
/*hide default igem banner and reformat style into blank slate*/
-
<table width="70%" align="center">
+
#globalWrapper {width: 100%;}
 +
#top-section {width: 100%; height:5px; border:none;}
 +
#p-logo {display:none;}
 +
#search-controls {display:none;}
 +
#menubar a {color:#000000;}
 +
#menubar a:hover{text-decoration:none; color:#52749C;}
 +
.left-menu {background-color:#FFFFFF; margin:0px 0px 0px 0px; padding:0;}
 +
.left-menu ul {background-color:#FFFFFF; margin:0; padding:0;}
 +
.right-menu ul li a {background-color:#FFFFFF;}
 +
.printfooter {display:none;}
 +
#footer-box {border:none;}
 +
#catlinks {display:none;}
 +
.firstHeading {display:none;}
 +
#content {width: 100%; border:none;}
 +
#bodyContent {border:none;}
-
<tr>
 
-
<!--navigation menu -->
+
/*actual content styles*/
-
<td align="center" colspan="3">
+
body {width: 800px; margin:auto;}
-
<table  width="100%">
+
#bu-wellesley_wiki_content {height:auto; line-height:100%;}
-
<tr heigth="15px"></tr>
+
/*#bu-wellesley_wiki_content a {color:#69d01d;}*/
-
<tr heigth="75px">
+
#bu-wellesley_wiki_content a:hover {text-decoration:none; color:#3d3f3c;}
-
<img src="http://i.imgur.com/ta0HIn9.png" align="center"/>
+
.navbar li {color: #ffffff;}
 +
.navbar li a {color: #ffffff;}
 +
.navbar li a:hover {background:#69d01d; color: #ffffff;}
-
<body>
+
/*only use for current page content header*/
-
<div id="menubar1">
+
-
<a href="https://2014.igem.org/Team:WPI-Worcester"> Home </a>
+
-
<a href="https://2014.igem.org/Team:WPI-Worcester/Team"> Team </a>
+
-
<a href="https://igem.org/Team.cgi?id=1423"> Official Team Profile </a>
+
-
<a href="https://2014.igem.org/Team:WPI-Worcester/Project"> Project </a>
+
-
<a href="https://2014.igem.org/Team:WPI-Worcester/Parts"> Parts </a>
+
-
<a href="https://2014.igem.org/Team:WPI-Worcester/Modeling"> Modeling </a>
+
-
<a href="https://2014.igem.org/Team:WPI-Worcester/Notebook"> Notebook </a>
+
-
<a href="https://2014.igem.org/Team:WPI-Worcester/Safety"> Safety </a>
+
-
<a href="https://2014.igem.org/Team:WPI-Worcester/Attributions"> Attributions </a>
+
-
</div>
+
-
</body>
+
 +
</style>
-
<td align ="center">  </td>
+
<link href='http://fonts.googleapis.com/css?family=Signika:300,400' rel='stylesheet' type='text/css'>
-
</tr>
+
<link href='http://fonts.googleapis.com/css?family=Averia+Serif+Libre:300,400,700' rel='stylesheet' type='text/css'>
-
</table>
+
-
<!--end navigation menu -->
+
<style type="text/css">
-
</tr>
+
/* MAIN STYLE DEFINITIONS */
-
</tr>
+
a{
-
</td>
+
color:#AC2B37;
 +
}
-
<tr> <td colspan="3"  height="15px"> </td></tr>
+
a:hover {
-
<tr><td bgColor="#e7e7e7" colspan="3" height="1px"> </tr>
+
color:#AC2B37;
-
<tr> <td colspan="3"  height="5px"> </td></tr>
+
}
 +
a:visited{
 +
color:#AC2B37;
 +
}
-
<!--safety content-->
+
td
-
<tr><td > <h3> Welcome! </h3></td>
+
{
-
<td ></td >
+
font-family: Georgia;
-
<td > <h3> Timeline</h3></td>
+
font-size: 10pt;
-
</tr>
+
vertical-align: top;
 +
text-align: left;
 +
padding-right: 10px;
 +
}
-
<tr>
+
tr
-
<td width="45%"  valign="top">
+
{
-
<p> Visit the <a href="https://2014.igem.org/Safety" >Safety Hub</a> to see this year's safety requirements. The Safety Hub is the central page for everything related to safety in iGEM. You can also go there to learn about general biosafety topics, and how to think about the future implications of your project.</p>
+
vertical-align: top;
 +
}
 +
H1 {
 +
    font-family: Georgia;
 +
    text-transform: none;
 +
    color: #AC2B37;
 +
    text-align: left;
 +
    }
 +
H4 {
 +
    font-family: Georgia;
 +
    text-transform: none;
 +
    color: #AC2B37;
 +
    text-align: left;
 +
    }
-
<br>
+
img.headshot {
-
<h3> Edit this page!</h3>
+
width: 100px;
-
<p>
+
height: auto;
-
Please use this page to write about anything related to safety in your project. <!--Be sure to talk about both
+
vertical-align: text-top;
-
<ul>
+
}
-
<li> <a href=" ">Learn about lab Safety for Today</a></li>
+
-
<li> <a href="">Learn about Safety for the future of your project.</a></li>
+
-
</ul>
+
-
-->
+
-
</p>
+
-
<h3> Your Lab </h3>
+
body {
 +
background: #FFFFFF;
 +
font-family: Arial;
 +
}
 +
#tracking_nav
 +
{
 +
margin: 0px 0px 0px 900px;
 +
position: fixed;
 +
color:#bababa;
 +
border: 1px solid ##AC2B37;
 +
background:##AC2B37;
 +
font-size: 16pt;
 +
padding: 0px;
 +
line-height: 100%;
 +
}
-
<p> Use this section to tell us about your laboratory. Where is it located? What sort of equipment do you use every day? Have you decorated it for the summer? How do you look wearing a lab coat? Take pictures! Show off your space! </p>
 
-
<!--
 
-
<gallery>
 
-
Image:Example2_Lab_1.png|The building our lab is in!
 
-
Image:Example2_Lab_2.png|The inside of our lab!
 
-
Image:Example2_Lab_3.png|Team Member 3 doing an experiment
 
-
Image:Example2_Lab_4.png|Working in biosafety cabinets
 
-
Image:Example2_Lab_5.png|Team all gloved up and ready for work!
 
-
Image:Example2_Lab_6.png|Equipment that we use to do SCIENCE!
 
-
Image:Example2_Lab_7.png|We decorated this part of our lab
 
-
Image:Example2_Lab_8.png|Whatever else you want
 
-
</gallery>-->
 
-
</td>
+
#tracking_nav a { color:#ffffff; text-transform: lowercase;font-size: 16pt;}
-
<td></td>
+
#tracking_nav a:hover {background:#bababa;}
-
<td width="45%"  valign="top">
+
#nav li {
 +
color: #ffffff;
 +
background-color:#A9B0B7;
 +
margin: 0 0px;
 +
float: left;
 +
position: relative;
 +
list-style: none;
 +
text-transform:none;
 +
font-size:12pt;
 +
}
 +
/* main level link */
 +
#nav a {
 +
font-weight: bold;
 +
color: #ffffff;
 +
text-decoration: none;
 +
border-left-style: solid;
 +
border-right-style: solid;
 +
        border-color: #000000;
 +
        border-width: 1px;
-
<ul>
+
display: block;
-
<li> <b>Now :</b> Read the <a href="https://2014.igem.org/Safety">Safety Hub </a> and learn about safety in iGEM. Ask questions by emailing safety at <i> igem DOT org </i>. </li>
+
padding4px 16px;
-
<li><b>Now - Jamboree:</b> Complete <b>Check-Ins</b> and receive approval before acquiring and using certain materials in your lab</li>
+
margin: 0;
-
<li><b>Now - Wiki Freeze:</b> Edit this Safety page to tell us about what you're doing</li>
+
}
-
<li><b>June 9: </b>Submit the About Our Lab form.</li>
+
-
<li><b>Let us know by June 25 </b>if you will need an extension on the Preliminary Version, or your Preliminary Version will be significantly incomplete.</li>
+
-
<li><b>June 30: </b>Submit the Preliminary Version of the <b>Safety Form</b>.</li>
+
-
<li>Participate in Virtual Open Office Hours to ask questions and discuss safety topics (exact date to be determined).</li>
+
-
<li><b>September 1:</b> Submit the Final Version of the Safety Form.</li>
+
-
<li><b>October: </b> Wiki freeze (exact date to be determined)</li>
+
-
<li><b>October 30 - November 3: </b>GIANT JAMBOREE!</li>
+
-
</ul>
+
#nav a:hover {
-
</td>
+
background-color: #000000;
 +
color: #ffffff;
 +
}
-
</tr>
+
/* main level link hover */
 +
#nav .current a, #nav li:hover > a {
 +
color: #ffffff;
 +
background-color: #AC2B37;
 +
}
 +
/* sub levels link hover */
 +
#nav ul li:hover a, #nav li:hover li a {
 +
border: solid;
 +
        border-color: #000000;
 +
        border-width: 1px;
 +
background-color: #AC2B37;
 +
color: #ffffff;
 +
}
 +
#nav ul a:hover {
 +
background: #fff url(img/gradient.png) repeat-x 0 -100px !important;
 +
color: #AC2B37 !important;
 +
text-shadow: 0 1px 1px rgba(0,0,0, .1);
 +
}
 +
/* dropdown */
 +
#nav li:hover > ul {
 +
display: block;
 +
background-color: #fff;
 +
}
-
<tr>
+
/* level 2 list */
 +
#nav ul {
 +
display: none;
 +
margin: 0;
 +
padding: 0;
 +
width: 205px;
 +
position: absolute;
 +
top: 70px;
 +
left: 0;
 +
}
 +
#nav ul li {
 +
float: none;
 +
margin: 0;
 +
padding: 0;
 +
}
 +
#nav ul a {
 +
font-weight: normal;
 +
text-shadow: 0 1px 0 #fff;
 +
}
 +
/* clearfix */
 +
#nav:after {
 +
content: ".";
 +
display: block;
 +
clear: both;
 +
visibility: hidden;
 +
line-height: 0;
 +
height: 0;
 +
}
 +
#nav {
 +
display: inline-block;
 +
}
 +
 +
html[xmlns] #nav {
 +
display: block;
 +
}
 +
 +
* html #nav {
 +
height: 1%;
 +
}
 +
 +
@font-face {
 +
    font-family: HP PSG;
 +
    src: url(HP PSG.eot);
 +
}
 +
 +
#menuOverlay {
 +
  position:relative;
 +
  width:100%:
 +
  z-index: 999;
 +
}
 +
 +
</style>
 +
</head>
 +
 +
<body class="basiclayout">
 +
<div id="bu-wellesley_wiki_content"></div>
 +
 +
<div id="igemlogo">
 +
<a href="https://2014.igem.org/Main_Page"><img src="https://static.igem.org/mediawiki/igem.org/6/60/Igemlogo_300px.png" alt="iGEM 2014 main page" style="position: absolute; top: 10px; right: 10px;"width="50"></a>
 +
</div>
 +
 +
<p  style="text-align:center;"><a href="https://2014.igem.org/Team:WPI-Worcester"><img src="https://static.igem.org/mediawiki/2014/3/3f/Wpibanner.png" width="800px" length="200px"></a></p>
 +
 +
<div id="menuOverlay">
 +
<ul id="nav">
 +
<li> <a href="#"><center><img src="https://static.igem.org/mediawiki/2014/6/64/WPI_Team_Link.png"/></center> <p>Team</p></a>
 +
<ul>
 +
<li><a href="https://2014.igem.org/Team:WPI-Worcester/Team">Bios</a></li>
 +
<li><a href="https://2014.igem.org/Team:WPI-Worcester/Team-Gallery">Team Gallery</a></li>
 +
<li><a href="https://igem.org/Team.cgi?id=1423">Official Team Page</a></li>
 +
</ul>
 +
</li>
 +
 +
<li><a href="#"><center><img src="https://static.igem.org/mediawiki/2014/4/41/WPI_Project_Link.png"/></center><p>Project</p></a>
 +
<ul>
 +
    <li><a href="https://2014.igem.org/Team:WPI-Worcester/Motivation">Motivation</a></li>
 +
            <li><a href="https://2014.igem.org/Team:WPI-Worcester/Background">Background</a></li>
 +
    <li><a href="https://2014.igem.org/Team:WPI-Worcester/Overview">Project Overview</a></li>
 +
    <li><a href="https://2014.igem.org/Team:WPI-Worcester/Future-Applications">Future Applications</a></li>
 +
 +
</ul>
 +
</li>
 +
 +
<li><a href="#"><center><img src="https://static.igem.org/mediawiki/2014/f/f1/Accomplishments_RealLink.png"/></center><p>Accomplishments</p></a>
 +
<ul>
 +
<li><a href="https://2014.igem.org/Team:WPI-Worcester/Our-Construct">Our Construct</a></li>
 +
<li><a href="https://2014.igem.org/Team:WPI-Worcester/Proof-of-Principle">Proof of Principle</a></li>
 +
<li><a href="https://2014.igem.org/Team:WPI-Worcester/ATF1">Better BioBrick Characterization</a></li>
 +
<li><a href="https://2014.igem.org/Team:WPI-Worcester/Biobricks">BioBricks</a></li>
 +
<li><a href="https://2014.igem.org/Team:WPI-Worcester/Medal-Fulfillment">Medal Fulfillment</a></li>
 +
 +
</ul>
 +
</li>
 +
 +
<li><a href="#"><center><img src="https://static.igem.org/mediawiki/2014/7/7e/WPI_Notes_Link.png"/></center><p>Notebook</p></a>
 +
<ul>
 +
<li><a href="https://2014.igem.org/Team:WPI-Worcester/Notebook">Weekly Log</a></li>
 +
<li><a href="https://2014.igem.org/Team:WPI-Worcester/Protocols">Protocols</a></li>
 +
 +
</ul>
 +
</li>
 +
 +
 +
<li><a href="#"><center><img src="https://static.igem.org/mediawiki/2014/d/d4/WPI_Safety_Link.png"/></center><p>Practices</p></a>
 +
<ul>
 +
                <li><a href="https://2014.igem.org/Team:WPI-Worcester/Outreach">Outreach</a></li>
 +
            <li><a href="https://2014.igem.org/Team:WPI-Worcester/Survey">Survey</a></li>
 +
<li><a href="https://2014.igem.org/Team:WPI-Worcester/Collaborations">Collaborations</a></li>
 +
<li><a href="https://2014.igem.org/Team:WPI-Worcester/Interlab">Interlab Study</a></li>
 +
  <li><a href="https://2014.igem.org/Team:WPI-Worcester/Safety">Safety</a></li>
 +
            <li><a href="https://2014.igem.org/Team:WPI-Worcester/Beyond-the-Bench">Beyond the Bench</a></li>
 +
 +
        </ul>
 +
 +
 +
<li><a href="#"><center><img src="https://static.igem.org/mediawiki/2014/e/e9/Acknowledgements_Link.png"/></center><p>Acknowledgements</p></a>
 +
<ul>
 +
<li><a href="https://2014.igem.org/Team:WPI-Worcester/Sponsors">Sponsors</a></li>
 +
<li><a href="https://2014.igem.org/Team:WPI-Worcester/Attributions">Attributions</a></li>
 +
 +
</ul>
 +
</li>
 +
</li>
 +
</ul>
 +
</div>
 +
</body>
 +
</br>
 +
<h4>Safety</h4><p>At the beginning of the summer, each iGEM member received safety training for our lab space at the WPI Life Sciences and Bioengineering Center at Gateway Park in Worcester, Ma. We were trained in safe practices for handling biohazardous and infectious materials including safe working practices, clean up and disposal. We also received training in general laboratory and chemical safety practices, chemical use and disposal, and chemical spill response. Here is a link to <a href="http://www.wpi.edu/offices/safety/laboratory.html">WPI’s laboratory safety requirements</a>.</p>
 +
 +
<p>We also ensured to follow the biological safety protocol for our institution at the onset of this project. We discussed our proposed project with David Adams, who handles biological safety at WPI, and he determined our rDNA constructs were within our approved guidelines and did not pose any particular biohazard threats. Here is a link to <a href="http://www.wpi.edu/offices/safety/biological.html">WPI’s biological safety policies</a>.</p>
 +
 +
<p>When filling out the safety form for iGEM, we were forced to consider not only the immediate risks of our project in the lab, but also the long-term risks possible in the future if our construct was successful.  Our responses to the safety form prompts and a picture of one of our lab benches can be seen below.</p></br>
 +
<p><center><img src="https://static.igem.org/mediawiki/2014/b/b0/Wpi_2014_lab_space.png"/></center></p>
 +
<p><center><h3>Shawna and Corbyn's Lab Bench (Inspired by Ginkgo Bioworks).</h3></center></p></br>
 +
 +
<p><h9>Immediate Risks</h9></p>
 +
<p><b>Risks to the safety and health of team members, or other people working in the lab:</b></p>
 +
<p>The main, though extremely remote, risk involved with working with <i>E. coli</i> K-12
 +
strains is the potential infection and colonization of the gastrointestinal tract. We protect ourselves from this risk by wearing gloves, lab coats and safety glasses at all times while in the lab. We also never eat or drink in the lab, and always wash our hands and wipe the benches down with 70% ethanol before leaving the lab.  <a href="http://epa.gov/biotech_rule/pubs/fra/fra004.htm">This website</a> from the EPA summarizes the human health risks of <i>E. coli</i> K-12 strains.</p>
-
</table>
+
<p>In addition to the <i>E. coli</i>  K-12 strain, we are working with a BclA, a protein from <i>B. anthracis</i>, and CAEV p28, a protein from Caprine Arthritis Encephalitis Virus. Because these are single proteins, they should not be harmful to any team members or others working in the lab. Nevertheless, we take the same precautions with BclA and CAEV p28 that we take when handling the <i>E. coli</i> K-12 strain. </p>
 +
 +
<p><b>Risks to the safety and health of the general public (if any biological materials escaped from your lab):</b></p>
 +
<p><i>E coli</i> K-12 survives poorly in external environmental conditions. However if the strain mutated and escaped from the lab, gastrointestinal infection could result. Because antibiotic resistant plasmids are used for cloning in <i>E. coli</i>, the transfer of antibiotic resistant plasmids to human pathogens could also occur. This could result in the formation of a superbug, which could potentially threaten the lives of any people exposed to it.</p>
 +
 +
<p><b>Risks to the environment (from waste disposal, or from materials escaping from your lab):</b></p>
 +
<p>As stated above, use of antibiotic resistant plasmids for cloning in <i>E. coli</i> carries the inherent risk of transfer of antibiotic resistance genes to natural environmental bacterial strains. If any clones produced in the lab are not disposed of properly, they could transfer DNA to any naturally occurring bacterium, resulting in the creation of a novel strain that could be potentially harmful for humans or any other organisms that come in contact with it. </p>
 +
 +
<p><b>Risks to security through malicious misuse by individuals, groups, or countries:</p></b>
 +
<p>As mentioned above, it is possible that malicious misuse could result in the production of multi-drug resistant pathogenic bacterial strains. Also, it is possible malicious individuals could fuse the BclA N terminal domain to a known human toxin and express it of the cell surface in <i>E. coli</i>, thereby converting the harmless K-12 strain into a pathogen.</p>
 +
 +
 +
<p><b>What measures are you taking to reduce these risks? (For example: safe lab practices, choices of which organisms to use.)</p></b>
 +
<p>Our primary defense is good laboratory techniques (use of personal protective equipment, careful lab practices, and good hand hygiene). We bleach all <i>E. coli</i> cultures for 24 hours before disposing of them in the sink, to prevent escape of the cultures from the lab. The only fully functioning organism we are using is the relatively benign K-12 <i>E. coli</i> strain. We chose DNA synthesis, rather than cloning directly from the organisms, for the BclA and CAEV genes so that we could protect ourselves from exposure to these agents.</p></br>
 +
 +
 +
<p><h9>Long-Term Risks</h9></p>
 +
 +
<p><b>What new risks might arise from your project's growth? (Consider the categories of risk listed in parts a-d of the previous question: lab workers, the general public, the environment, and malicious misuses.) Also, what risks might arise if the knowledge you generate or the methods you develop became widely available?</b></p>
 +
<p>Based on these premises, it is likely that our diagnosis system would become a widespread tool for livestock health regulations. Used by both small scale sustenance farmers to corporate scale stockyards, our project would become a cornerstone of the modern livestock health system. As antibacterial resistance concern grows, as well as economic pressure from the funds needed to maintain our current practices, the need for cheap and effective diagnostic tools for livestock will expand exponentially. As part of our current objective, our methods of combating antibiotic resistance in bacteria will be recognized as the winner of the Longitude Prize, allowing us to expand our operations to accommodate this agricultural demand. One of the largest risks associated with this method of diagnosis is mutating pathogenic strains. Our project is currently dependent on very specific antigen-antibody bonds, and does not account for mutagenic strains that may lack the antigen we test for. Another risk is associated with our possible antigen blocking in the future, which involves blocking some our  <i>E. coli</i> antigens with synthetic antibodies to better improve agglutination test results. This process has the effect of creating <i>E. coli</i> that may be immune to certain antibodies, and not properly recognized by the immune system.</p>
 +
<p>The two new parts we created for our project pose little safety threat on their own.  The BclA is only a membrane localization domain and the CAEV capsid protein does not act as a virus while it is missing its other components. These proteins do not add anything to the behavior or to the biohazardous properties of the chimeric <i>E. coli</i>, merely acting as a target for antibodies. However, if our mechanism were to become widely available, the BclA surface domain could be used to attach malicious proteins to the cell's surface if someone with malicious intentions knew how to carry out the process.</p>
 +
<p>In terms of the agglutination assay, one concern with our project is that native <i>E. coli</i> antigens would produce a false positive result when testing for a particular disease if the host organism has an <i>E. coli</i> infection. While this in itself is not an issue with safety, in order to prevent this false positive, our team discussed the possibility of blocking the native <i>E. coli</i> antigens using either synthetic antibodies or llama/alpaca antibodies, which would leave only the antigen of the disease of interest available for antigen-antibody pairing. In doing this, we would essentially be creating a system for <i>E. coli</i> to prevent itself from being detected or attacked by the host organism's natural immune response. This could lead to an infection that is much more difficult to treat than a normal <i>E. coli</i> infection if a culture affected by the <i>E. coli</i> antigen-binding antibodies were to come into contact with humans or animals.</p>
 +
 +
<p><b>Does your project currently include any design features to reduce risks? Or, if you did all the future work to make your project grow into a popular product, would you plan to design any new features to minimize risks? (For example: auxotrophic chassis, physical containment, etc.) Such features are not required for an iGEM project, but many teams choose to explore them.</b></p>
 +
<p>At the current time, our project does not include any inherent safety considerations, so there are no current designed features to reduce risk. In the future, however, if this diagnostic tool were to be utilized large scale, some design features should be implemented in order to minimize potential risk. As mentioned above, in further development of this project, ideally the native <i>E. coli</i> antigens would be blocked using either synthetic antibodies or llama/alpaca antibodies. This would leave only the antigen of the disease of interest available for antigen-antibody pairing on the surface of <i>E. coli</i>.  This raises the concern of immune resistant <i>E. coli</i>, and our team considered the possibility of designing a fail-safe that would include a heavy metal inducible promoter, such as arsenic, which would only naturally be present in low concentrations in a host organism. Thus, the synthetic antibody that could block the <i>E. coli</i>’s native antigens would only be produced in vitro. This helps to minimize the risk that our immune resistant bacteria could be weaponized.</p>
 +
 +
 +
</br>
 +
</br>
 +
</br>
</html>
</html>

Latest revision as of 23:13, 17 October 2014

Team:WPI-Worcester - 2014.igem.org

 

Team:WPI-Worcester

From 2014.igem.org


Safety

At the beginning of the summer, each iGEM member received safety training for our lab space at the WPI Life Sciences and Bioengineering Center at Gateway Park in Worcester, Ma. We were trained in safe practices for handling biohazardous and infectious materials including safe working practices, clean up and disposal. We also received training in general laboratory and chemical safety practices, chemical use and disposal, and chemical spill response. Here is a link to WPI’s laboratory safety requirements.

We also ensured to follow the biological safety protocol for our institution at the onset of this project. We discussed our proposed project with David Adams, who handles biological safety at WPI, and he determined our rDNA constructs were within our approved guidelines and did not pose any particular biohazard threats. Here is a link to WPI’s biological safety policies.

When filling out the safety form for iGEM, we were forced to consider not only the immediate risks of our project in the lab, but also the long-term risks possible in the future if our construct was successful. Our responses to the safety form prompts and a picture of one of our lab benches can be seen below.


Shawna and Corbyn's Lab Bench (Inspired by Ginkgo Bioworks).


Immediate Risks

Risks to the safety and health of team members, or other people working in the lab:

The main, though extremely remote, risk involved with working with E. coli K-12 strains is the potential infection and colonization of the gastrointestinal tract. We protect ourselves from this risk by wearing gloves, lab coats and safety glasses at all times while in the lab. We also never eat or drink in the lab, and always wash our hands and wipe the benches down with 70% ethanol before leaving the lab. This website from the EPA summarizes the human health risks of E. coli K-12 strains.

In addition to the E. coli K-12 strain, we are working with a BclA, a protein from B. anthracis, and CAEV p28, a protein from Caprine Arthritis Encephalitis Virus. Because these are single proteins, they should not be harmful to any team members or others working in the lab. Nevertheless, we take the same precautions with BclA and CAEV p28 that we take when handling the E. coli K-12 strain.

Risks to the safety and health of the general public (if any biological materials escaped from your lab):

E coli K-12 survives poorly in external environmental conditions. However if the strain mutated and escaped from the lab, gastrointestinal infection could result. Because antibiotic resistant plasmids are used for cloning in E. coli, the transfer of antibiotic resistant plasmids to human pathogens could also occur. This could result in the formation of a superbug, which could potentially threaten the lives of any people exposed to it.

Risks to the environment (from waste disposal, or from materials escaping from your lab):

As stated above, use of antibiotic resistant plasmids for cloning in E. coli carries the inherent risk of transfer of antibiotic resistance genes to natural environmental bacterial strains. If any clones produced in the lab are not disposed of properly, they could transfer DNA to any naturally occurring bacterium, resulting in the creation of a novel strain that could be potentially harmful for humans or any other organisms that come in contact with it.

Risks to security through malicious misuse by individuals, groups, or countries:

As mentioned above, it is possible that malicious misuse could result in the production of multi-drug resistant pathogenic bacterial strains. Also, it is possible malicious individuals could fuse the BclA N terminal domain to a known human toxin and express it of the cell surface in E. coli, thereby converting the harmless K-12 strain into a pathogen.

What measures are you taking to reduce these risks? (For example: safe lab practices, choices of which organisms to use.)

Our primary defense is good laboratory techniques (use of personal protective equipment, careful lab practices, and good hand hygiene). We bleach all E. coli cultures for 24 hours before disposing of them in the sink, to prevent escape of the cultures from the lab. The only fully functioning organism we are using is the relatively benign K-12 E. coli strain. We chose DNA synthesis, rather than cloning directly from the organisms, for the BclA and CAEV genes so that we could protect ourselves from exposure to these agents.


Long-Term Risks

What new risks might arise from your project's growth? (Consider the categories of risk listed in parts a-d of the previous question: lab workers, the general public, the environment, and malicious misuses.) Also, what risks might arise if the knowledge you generate or the methods you develop became widely available?

Based on these premises, it is likely that our diagnosis system would become a widespread tool for livestock health regulations. Used by both small scale sustenance farmers to corporate scale stockyards, our project would become a cornerstone of the modern livestock health system. As antibacterial resistance concern grows, as well as economic pressure from the funds needed to maintain our current practices, the need for cheap and effective diagnostic tools for livestock will expand exponentially. As part of our current objective, our methods of combating antibiotic resistance in bacteria will be recognized as the winner of the Longitude Prize, allowing us to expand our operations to accommodate this agricultural demand. One of the largest risks associated with this method of diagnosis is mutating pathogenic strains. Our project is currently dependent on very specific antigen-antibody bonds, and does not account for mutagenic strains that may lack the antigen we test for. Another risk is associated with our possible antigen blocking in the future, which involves blocking some our E. coli antigens with synthetic antibodies to better improve agglutination test results. This process has the effect of creating E. coli that may be immune to certain antibodies, and not properly recognized by the immune system.

The two new parts we created for our project pose little safety threat on their own. The BclA is only a membrane localization domain and the CAEV capsid protein does not act as a virus while it is missing its other components. These proteins do not add anything to the behavior or to the biohazardous properties of the chimeric E. coli, merely acting as a target for antibodies. However, if our mechanism were to become widely available, the BclA surface domain could be used to attach malicious proteins to the cell's surface if someone with malicious intentions knew how to carry out the process.

In terms of the agglutination assay, one concern with our project is that native E. coli antigens would produce a false positive result when testing for a particular disease if the host organism has an E. coli infection. While this in itself is not an issue with safety, in order to prevent this false positive, our team discussed the possibility of blocking the native E. coli antigens using either synthetic antibodies or llama/alpaca antibodies, which would leave only the antigen of the disease of interest available for antigen-antibody pairing. In doing this, we would essentially be creating a system for E. coli to prevent itself from being detected or attacked by the host organism's natural immune response. This could lead to an infection that is much more difficult to treat than a normal E. coli infection if a culture affected by the E. coli antigen-binding antibodies were to come into contact with humans or animals.

Does your project currently include any design features to reduce risks? Or, if you did all the future work to make your project grow into a popular product, would you plan to design any new features to minimize risks? (For example: auxotrophic chassis, physical containment, etc.) Such features are not required for an iGEM project, but many teams choose to explore them.

At the current time, our project does not include any inherent safety considerations, so there are no current designed features to reduce risk. In the future, however, if this diagnostic tool were to be utilized large scale, some design features should be implemented in order to minimize potential risk. As mentioned above, in further development of this project, ideally the native E. coli antigens would be blocked using either synthetic antibodies or llama/alpaca antibodies. This would leave only the antigen of the disease of interest available for antigen-antibody pairing on the surface of E. coli. This raises the concern of immune resistant E. coli, and our team considered the possibility of designing a fail-safe that would include a heavy metal inducible promoter, such as arsenic, which would only naturally be present in low concentrations in a host organism. Thus, the synthetic antibody that could block the E. coli’s native antigens would only be produced in vitro. This helps to minimize the risk that our immune resistant bacteria could be weaponized.