Team:VCU/Safety

From 2011.igem.org

(Difference between revisions)
(Prototype team page)
 
(15 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 *** -->
+
[[File:VCU iGEM banner.png|960px|center]]
 +
<br />
 +
<center>
 +
===THE 2011 VCU iGEM PROJECT===
 +
</center>
 +
{|align="justify"
 +
|
 +
|
 +
|-
 +
|}
 +
<br />
<html>
<html>
-
<div id="box" style="width: 700px; margin-left: 137px; padding: 5px; border: 3px solid #000; background-color: #fe2b33;">
+
<head>
-
<div id="template" style="text-align: center; font-weight: bold; font-size: large; color: #f6f6f6; padding: 5px;">
+
<title>wiki_prototype</title>
-
This is a template page. READ THESE INSTRUCTIONS.
+
-
</div>
+
<style type="text/css">
-
<div id="instructions" style="text-align: center; font-weight: normal; font-size: small; color: #f6f6f6; padding: 5px;">
+
-
You are provided with this team page template with which to start the iGEM season.  You may choose to personalize it to fit your team but keep the same "look." Or you may choose to take your team wiki to a different level and design your own wiki.  You can find some examples <a href="https://2008.igem.org/Help:Template/Examples">HERE</a>.
+
-
</div>
+
-
<div id="warning" style="text-align: center; font-weight: bold; font-size: small; color: #f6f6f6; padding: 5px;">
+
-
You <strong>MUST</strong> have a team description page, a project abstract, a complete project description, a lab notebook, and a safety page.  PLEASE keep all of your pages within your teams namespace. 
+
-
</div>
+
-
</div>
+
-
</html>
+
-
<!-- *** End of the alert box *** -->
 
 +
#centeredmenu {
 +
  float:left;
 +
  width:100%;
 +
  background:#fff;
 +
  border-bottom:4px solid #000;
 +
  overflow:hidden;
 +
  position:relative;
 +
}
 +
#centeredmenu ul {
 +
  clear:left;
 +
  float:left;
 +
  list-style:none;
 +
  margin:0;
 +
  padding:0;
 +
  position:relative;
 +
  left:50%;
 +
  text-align:center;
 +
}
 +
#centeredmenu ul li {
 +
  display:block;
 +
  float:left;
 +
  list-style:none;
 +
  margin:0;
 +
  padding:0;
 +
  position:relative;
 +
  right:50%;
 +
}
 +
#centeredmenu ul li a {
 +
  display:block;
 +
  margin:0 0 0 1px;
 +
  padding:3px 10px;
 +
  background:#FDD017;
 +
  color:black;
 +
  text-decoration:none;
 +
  line-height:1.3em;
 +
  font: bold 12px Verdana;
 +
}
 +
#centeredmenu ul li a:hover {
 +
  background:#414141;
 +
  color:white;
 +
}
 +
#centeredmenu ul li a:hover {
 +
  color:#fff;
 +
  background:#000;
 +
  font-weight:bold;
 +
}
-
{|align="justify"
+
</style>
-
|You can write a background of your team here.  Give us a background of your team, the members, etc.  Or tell us more about something of your choosing.
+
-
|[[Image:VCU_logo.png|200px|right|frame]]
+
-
|-
+
-
|
+
-
''Tell us more about your project.  Give us background.  Use this is the abstract of your project.  Be descriptive but concise (1-2 paragraphs)''
+
-
|[[Image:VCU_team.png|right|frame|Your team picture]]
+
-
|-
+
-
|
+
-
|align="center"|[[Team:VCU | Team Example]]
+
-
|}
+
-
<!--- The Mission, Experiments --->
+
</head>
-
{| style="color:#1b2c8a;background-color:#0c6;" cellpadding="3" cellspacing="1" border="1" bordercolor="#fff" width="62%" align="center"
+
<body>
-
!align="center"|[[Team:VCU|Home]]
+
-
!align="center"|[[Team:VCU/Team|Team]]
+
-
!align="center"|[https://igem.org/Team.cgi?year=2010&team_name=VCU Official Team Profile]
+
-
!align="center"|[[Team:VCU/Project|Project]]
+
-
!align="center"|[[Team:VCU/Parts|Parts Submitted to the Registry]]
+
-
!align="center"|[[Team:VCU/Modeling|Modeling]]
+
-
!align="center"|[[Team:VCU/Notebook|Notebook]]
+
-
!align="center"|[[Team:VCU/Safety|Safety]]
+
-
!align="center"|[[Team:VCU/Attributions|Attributions]]
+
-
|}
+
-
==Safety==
 
-
Please use this page to answer the safety questions posed on the [[Safety | safety page]].
+
<div id="centeredmenu">
 +
  <ul>
 +
      <li><a href="https://2011.igem.org/Team:VCU">Home</a></li>
 +
      <li><a href="https://2011.igem.org/Team:VCU/Abstract">Abstract</a></li>
 +
      <li><a href="https://2011.igem.org/Team:VCU/Project">Project</a></li>
 +
      <li><a href="https://2011.igem.org/Team:VCU/Team">Team</a></li>
 +
  <li><a href="https://2011.igem.org/Team:VCU/Safety">Safety</a></li>
 +
  <li><a href="https://2011.igem.org/Team:VCU/SyntheticBiologyatVCU">Synthetic Biology at VCU</a></li>
 +
  </ul>
 +
</div>
 +
 
 +
<br>
 +
<br>
 +
 
 +
1. Safety issues raised by the project<br>
 +
:No safety issues for the researcher or the public were presented in our project outside what is typically found in a BSL-1 lab and when working with genetically modified organisms (GMOs).  We used standard non-pathogenic model organisms (Escherichia. coli and Synechococcus elongatus) in our research.  The chemical compound of interest, nerolidol, is classified as an irritant to skin and eyes.  As a result, BSL-1 containment is adequate to ensure individual and public safety involving both biological and chemical hazards in our project. It has been proposed that nerolidol may be toxic to aquatic organisms at heightened concentrations.  To prevent environmental exposure, the MSDS directs researchers to avoid putting nerolidol down drains.  We dispose of nerolidol in a chemical waste bottle that is collected and processed by our institution’s chemical waste management.  Biomachines capable of producing nerolidol are autoclaved before leaving the lab to ensure that no nerolidol-producing organisms are exposed to the environment.  Due to the fact that E. coli dh5α growth is greatly inhibited at temperatures below its incubation range, it would be unlikely that they would produce significant ecological damage in the event that they were released into the environment.  Their decreased reproduction would prevent horizontal gene transfer, and their reduced metabolism would prevent nerolidol production.  This effectively prevents the typically suspected issues with GMOs and the environment.<br>
 +
 
 +
2. Safety issues raised by our new BioBrick parts<br>
 +
: Our project only worked with Biobrick parts that involved promoters and reporters analogous to existent parts in the registery. As a result, no new safety issues were raised by our constructs, that were not already present from current Biobrick parts.<br>
 +
 
 +
3. Safety review board at our institution<br>
 +
:  VCU employs an Institutional Biosafety oversight committee, which requires the Vice President of Research to review all research projects, proposed or in progress, involving the use of hazardous chemicals, carcinogens, or recombinant DNA.  Upon review of our project, the committee has found no outstanding safety concerns, and endorses our project as a safe and legitimate research project.<br>
 +
 
 +
4. Future suggestions for safety<br>
 +
:  The use of reporter genes to test expression is one of the best tools available for safety when working with a biomachine designed to produce a compound that has any adverse environmental effects.  We utilized reporter genes such as GFP extensively during our promoter analysis, before linking any of them to nerolidol.  This reduced the amount of nerolidol waste and environmental burden generated in by our lab.<br>
 +
 
 +
</html>

Latest revision as of 22:47, 25 September 2011

VCU iGEM banner.png


THE 2011 VCU iGEM PROJECT


wiki_prototype



1. Safety issues raised by the project
:No safety issues for the researcher or the public were presented in our project outside what is typically found in a BSL-1 lab and when working with genetically modified organisms (GMOs). We used standard non-pathogenic model organisms (Escherichia. coli and Synechococcus elongatus) in our research. The chemical compound of interest, nerolidol, is classified as an irritant to skin and eyes. As a result, BSL-1 containment is adequate to ensure individual and public safety involving both biological and chemical hazards in our project. It has been proposed that nerolidol may be toxic to aquatic organisms at heightened concentrations. To prevent environmental exposure, the MSDS directs researchers to avoid putting nerolidol down drains. We dispose of nerolidol in a chemical waste bottle that is collected and processed by our institution’s chemical waste management. Biomachines capable of producing nerolidol are autoclaved before leaving the lab to ensure that no nerolidol-producing organisms are exposed to the environment. Due to the fact that E. coli dh5α growth is greatly inhibited at temperatures below its incubation range, it would be unlikely that they would produce significant ecological damage in the event that they were released into the environment. Their decreased reproduction would prevent horizontal gene transfer, and their reduced metabolism would prevent nerolidol production. This effectively prevents the typically suspected issues with GMOs and the environment.
2. Safety issues raised by our new BioBrick parts
: Our project only worked with Biobrick parts that involved promoters and reporters analogous to existent parts in the registery. As a result, no new safety issues were raised by our constructs, that were not already present from current Biobrick parts.
3. Safety review board at our institution
: VCU employs an Institutional Biosafety oversight committee, which requires the Vice President of Research to review all research projects, proposed or in progress, involving the use of hazardous chemicals, carcinogens, or recombinant DNA. Upon review of our project, the committee has found no outstanding safety concerns, and endorses our project as a safe and legitimate research project.
4. Future suggestions for safety
: The use of reporter genes to test expression is one of the best tools available for safety when working with a biomachine designed to produce a compound that has any adverse environmental effects. We utilized reporter genes such as GFP extensively during our promoter analysis, before linking any of them to nerolidol. This reduced the amount of nerolidol waste and environmental burden generated in by our lab.