Team:BU Wellesley Software/Safety
From 2011.igem.org
(→Safety) |
|||
(33 intermediate revisions not shown) | |||
Line 1: | Line 1: | ||
- | |||
- | |||
<html> | <html> | ||
- | < | + | <head> |
- | < | + | <title>BU-Wellesley iGEM Team: Meet the Team Members</title> |
- | + | <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> | |
- | + | <script src="http://cdn.jquerytools.org/1.2.5/full/jquery.tools.min.js?foo"></script> | |
- | + | <style type="text/css"> | |
- | + | /*hide default igem banner and reformat style into blank slate*/ | |
- | + | #globalWrapper {width: 100%;} | |
- | + | #top-section {width: 100%; height:30px; 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:5px 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;} | ||
- | + | /*actual content styles*/ | |
+ | body {width: 800px; margin:auto;} | ||
+ | #bu-wellesley_wiki_content {height:auto; line-height:100%;} | ||
+ | /*#bu-wellesley_wiki_content a {color:#69d01d;}*/ | ||
+ | #bu-wellesley_wiki_content a:hover {text-decoration:none; color:#3d3f3c;} | ||
+ | .navbar li {color: #ffffff;} | ||
+ | .navbar li a {color: #ffffff;} | ||
+ | .navbar li a:hover {background:#69d01d; color: #ffffff;} | ||
- | + | /*only use for current page content header (i.e. Team, G-nomeSurferPro, etc)*/ | |
- | + | H6 { | |
- | + | font-family: Helvetica; | |
- | + | text-transform: uppercase; | |
- | + | text-decoration: none; | |
- | + | text-align: left; | |
- | + | color: #3d3f3c; | |
- | + | font-size: 32pt; | |
- | + | } | |
- | + | ||
- | + | ||
- | < | + | </style> |
+ | <link rel="stylesheet" type="text/css" href="http://cs.wellesley.edu/~hcilab/iGEM_wiki/css/Team.css"> | ||
- | + | </head> | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
+ | <body class="basiclayout"> | ||
+ | <div id="bu-wellesley_wiki_content"> | ||
- | == | + | <p style="text-align:center;"><a href="https://2011.igem.org/Team:BU_Wellesley_Software"><img src="http://cs.wellesley.edu/~hcilab/iGEM_wiki/images/banner.png" width="800px"></a></p> |
- | + | <ul id="nav"> | |
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Team">Team</a></li> | ||
+ | <li><a href="#">Project</a> | ||
+ | <ul> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Project_Overview">Overview</a></li> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Clotho">Clotho</a></li> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/G-nomeSurferPro">G-nome Surfer Pro</a></li> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/OptimusPrimer">Optimus Primer</a></li> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Trumpet">Trumpet</a></li> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Puppetshow">Puppetshow</a></li> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/eLabNotebook">eLabNotebook</a></li> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Wet_Lab">Wet Lab</a></li> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Downloads_and_Tutorials">Downloads and Tutorials</a></li> | ||
+ | </ul> | ||
+ | </li> | ||
+ | <li><a href="#">Process</a> | ||
+ | <ul> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Methodology">Methodology</a></li> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Safety">Safety</a></li> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Notebook">Notebook</a></li> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Outreach">Outreach</a></li> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Tips">Tips and Tricks</a></li> | ||
+ | </ul> | ||
+ | </li> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Gold">Medal Fulfillment</a></li> | ||
+ | <li><a href="#">Additional Info</a> | ||
+ | <ul> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Acknowledgement">Acknowledgement</a></li> | ||
+ | <li><a href="https://2011.igem.org/Team:BU_Wellesley_Software/Social">Fun</a></li> | ||
+ | </ul> | ||
+ | </li> | ||
+ | </ul> | ||
- | + | <br> | |
+ | <h6>Safety</h6> | ||
- | In | + | <div id="tracking_nav"> |
+ | JUMP TO...<br> | ||
+ | <a href="#bu-wellesley_wiki_content">Top</a><br> | ||
+ | <a href="#comp">Computational Team</a><br> | ||
+ | <a href="#wetlab">Wet Lab Team</a> | ||
+ | </div> | ||
+ | |||
+ | <div id="comp" class="team_box"> | ||
+ | <h1>Computational Team Safety</h1> | ||
+ | <p> | ||
+ | For the computational team, safety was still an important component, as we tested our software on human subjects. We considered a user's physical, emotional, and mental demand during a study. We had consent forms for every participant in every study, letting them know that the studies were voluntary and that they could leave at any time they felt uncomfortable. We were very reassuring throughout every study, letting users know that any crashes or difficulties were our fault as designers and programmers; not theirs. We also compensated our participants with lunch or gift cards. | ||
+ | </p> | ||
+ | </div> | ||
+ | |||
+ | <div id="wetlab" class="team_box"> | ||
+ | <h1>Wet Lab Safety</h1> | ||
+ | <p> | ||
+ | Safety is of the utmost importance to the wet lab division of the BU/Wellesley iGEM team. In our research exploration of transcription factor interactions in ''Mycobacterium tuberculosis'', we strive to conduct experiments and construct DNA plasmids using the most biologically safe methods possible. | ||
+ | <br><br> | ||
+ | |||
+ | None of the materials used in our iGEM project pose a significant risk to the health and safety of our team members and laboratory. We work in a standard BSL1 certified lab space and mainly work with ''E. coli'' bacteria. Furthermore, there is no risk to the public health or environment if the materials of our project were released. This is because the genes that we are using and studying code for transcriptional proteins and are not pathogenic or toxic. There is no threat of security through misuse of our materials because of their nonlethal nature. | ||
+ | <br><br> | ||
+ | |||
+ | Specifically, despite the design of our parts and devices focus on ''M.tuberculosis'' transcription factors, the actual genes we are implementing in our BioBrick devices are genes from the nonpathogenic strain of ''M.tuberculosis'', ''Mycobacterium smegmatis''. The genes are made from a PCR reaction using primers designed from the ''M. smegmatis'' genome. Additionally, we are inserting these genes into ''E. coli'' bacteria, thus we are never in contact or work directly with ''M. tuberculosis'' or ''M. smegmatis''. This eliminates any risks associated with our Biobrick devices affecting our team members as well as the overall public health and environment. The genes we are using are available to the <a href="http://www.tbdb.org/"> public</a>, thus there is no threat to security with our parts. | ||
+ | <br><br> | ||
+ | |||
+ | In terms of lab safety and institutional standards, there is an <a href="http://www.bu.edu/orccommittees/ibc/">Institutional Biosafety Committee</a> (IBC) at Boston University which evaluates all research projects, primarily those involved with recombinant DNA, and insures proper biosafety guidelines. We are in contact with the IBC and are in the process of approving our project. | ||
+ | <br><br> | ||
+ | |||
+ | There is also a <a href="http://www.bu.edu/orccommittees/laboratory-safety/">Laboratory Safety Committee</a> through which all | ||
+ | wet lab members have taken a mandatory laboratory safety training. This training provides a basic overview to chemical and biosafety, fire and life safety, emergency management, and waste management. In the United States, the major centers for biosafety procedures and guidelines are the National Institutes of Health (NIH) <a href="http://oba.od.nih.gov/rdna/nih_guidelines_oba.html">Guidelines</a> and the <a href="http://www.cdc.gov/">Center for Disease Control and Prevention</a> (CDC). | ||
+ | <br><br> | ||
+ | |||
+ | The BU/Wellesley wet lab division will be documenting all of our safety procedures and guidelines in our online notebooks for future iGEM teams to see. Our hope is that future iGEM projects can continue to maintain, and even excel, biosafety standards to ensure the unintentional exposure or release of pathogens or toxins into the environment. | ||
+ | </p> | ||
+ | </div> | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | </div> | ||
+ | </body> | ||
+ | </html> |
Latest revision as of 21:02, 21 September 2011
Safety
Computational Team Safety
For the computational team, safety was still an important component, as we tested our software on human subjects. We considered a user's physical, emotional, and mental demand during a study. We had consent forms for every participant in every study, letting them know that the studies were voluntary and that they could leave at any time they felt uncomfortable. We were very reassuring throughout every study, letting users know that any crashes or difficulties were our fault as designers and programmers; not theirs. We also compensated our participants with lunch or gift cards.
Wet Lab Safety
Safety is of the utmost importance to the wet lab division of the BU/Wellesley iGEM team. In our research exploration of transcription factor interactions in ''Mycobacterium tuberculosis'', we strive to conduct experiments and construct DNA plasmids using the most biologically safe methods possible.
None of the materials used in our iGEM project pose a significant risk to the health and safety of our team members and laboratory. We work in a standard BSL1 certified lab space and mainly work with ''E. coli'' bacteria. Furthermore, there is no risk to the public health or environment if the materials of our project were released. This is because the genes that we are using and studying code for transcriptional proteins and are not pathogenic or toxic. There is no threat of security through misuse of our materials because of their nonlethal nature.
Specifically, despite the design of our parts and devices focus on ''M.tuberculosis'' transcription factors, the actual genes we are implementing in our BioBrick devices are genes from the nonpathogenic strain of ''M.tuberculosis'', ''Mycobacterium smegmatis''. The genes are made from a PCR reaction using primers designed from the ''M. smegmatis'' genome. Additionally, we are inserting these genes into ''E. coli'' bacteria, thus we are never in contact or work directly with ''M. tuberculosis'' or ''M. smegmatis''. This eliminates any risks associated with our Biobrick devices affecting our team members as well as the overall public health and environment. The genes we are using are available to the public, thus there is no threat to security with our parts.
In terms of lab safety and institutional standards, there is an Institutional Biosafety Committee (IBC) at Boston University which evaluates all research projects, primarily those involved with recombinant DNA, and insures proper biosafety guidelines. We are in contact with the IBC and are in the process of approving our project.
There is also a Laboratory Safety Committee through which all
wet lab members have taken a mandatory laboratory safety training. This training provides a basic overview to chemical and biosafety, fire and life safety, emergency management, and waste management. In the United States, the major centers for biosafety procedures and guidelines are the National Institutes of Health (NIH) Guidelines and the Center for Disease Control and Prevention (CDC).
The BU/Wellesley wet lab division will be documenting all of our safety procedures and guidelines in our online notebooks for future iGEM teams to see. Our hope is that future iGEM projects can continue to maintain, and even excel, biosafety standards to ensure the unintentional exposure or release of pathogens or toxins into the environment.