"
Team:UCSF/Safety
From 2012.igem.org
(Difference between revisions)
(Prototype team page) |
|||
| (12 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
| - | + | {{Template:UCSF}} | |
<html> | <html> | ||
| - | < | + | |
| - | <div id=" | + | |
| - | + | <style> | |
| + | #mission {width: 500px; float:left; background-color: #F5F5F5; margin-left:8px; padding: 10px; margin-top:8px;} | ||
| + | #opensource {width:306px; float:left; background-color: #F5F5F5; margin-left:8px; padding: 10px; margin-top:8px;} | ||
| + | #rightcontent {width:755px; float:right; background-color: #F5F5F5; margin-left: 8px; margin-top:10px;} | ||
| + | #photos {width:155px; float:left; background-color: #F5F5F5; margin-left: 8px; margin-top:10px;} | ||
| + | #description{width:450px; height:110px;float:left; background-color: #F5F5F5; margin-left: 8px; margin-top:10px;} | ||
| + | #flickr{width:755px; float:right;} | ||
| + | #leftcolumntotal{width:200px; height:1800px; float: left; margin-top:0px;} | ||
| + | |||
| + | </style> | ||
| + | </head> | ||
| + | <div id="rightcontent"> | ||
| + | <img align="left" style="margin-bottom:0px; width: 755px; margin-top:-3px; padding:0;" src="http://i53.tinypic.com/35cljrt.png" usemap="#headermap" alt="Queen's"> | ||
| + | <br> | ||
| + | |||
| + | |||
| + | <div id="description" style = "width:600px; height:175px"> | ||
| + | |||
| + | <h3orange1> | ||
| + | 1. Would any of your project ideas raise safety issues in terms of: researcher safety, public safety, or environmental safety? | ||
| + | </h3orange1> <p> <br><regulartext1> No, the materials used in our project are not hazardous and do not pose as a safety or health threat toward any of our team members, the public, or environment. </regulartext1> | ||
</div> | </div> | ||
| - | <div id=" | + | |
| - | + | <div id="description" style = "width:600px; height:220px"> | |
| + | <h3orange1>2. Do any of the new BioBrick parts (or devices) that you made this year raise any safety issues? If yes: | ||
| + | did you document these issues in the Registry? how did you manage to handle the safety issue? How could other teams learn from your experience? | ||
| + | </h3orange1> | ||
| + | <p> <br><regulartext1> While one of our systems is a “toxin-anti-toxin” system, it occurs naturally in <i>E. coli </i> and does not effect other organisms in a toxic manner. Many researchers have used these toxins without further precautions <a href=http://www.plosbiology.org/article/info%3Adoi%2F10.1371%2Fjournal.pbio.1001281>(For example, Ariel Erental of the Institute for Medical Research Israel-Canada)</a> <br> We are entering in new pairs of toxin anti-toxin pairs, but the parts registry already documents a pair of toxin-antitoxin from <i>E. coli</i>: <a href=http://partsregistry.org/Part:BBa_K185004>RelE Toxin<a/>. </regulartext1> | ||
</div> | </div> | ||
| - | <div id=" | + | |
| - | + | <br> | |
| + | <div id="description" style = "width:600px; height:250px"> | ||
| + | <h3orange1>3. Is there a local biosafety group, committee, or review board at your institution? If yes, what does your local biosafety group think about your project? If no, which specific biosafety rules or guidelines do you have to consider in your country? </h3orange1> | ||
| + | <p><br> <regulartext1> <FONT COLOR="black"> The UCSF iGEM Team works under the Biological Use Agreement (BUA) approved by UCSF Health and Safety (EH&S). http://industry.ucsf.edu/ehs/8046-DSY/version/default/part/4/data/ <p> | ||
| + | UCSF has a Biosafety Committee (http://or.ucsf.edu/ehs/7240-DSY/7422-DSY/8777), but it was not deemed necessary to meet with them regarding our project because all of our work falls under standard laboratory procedures that have prescribed regulations and safety protocols. </regulartext1> | ||
| + | |||
| + | <p> <regulartext1> Additionally, the United States has a manual with biosafety guidelines for biological laboratories: http://www.cdc.gov/biosafety/publications/bmbl5/index.htm </regulartext1> | ||
</div> | </div> | ||
| + | |||
| + | |||
| + | <br> | ||
| + | <div id="description" style = "width:600px; height:220px"> | ||
| + | <h3orange1>4. Do you have any other ideas how to deal with safety issues that could be useful for future iGEM competitions? How could parts, devices and systems be made even safer through biosafety engineering? | ||
| + | </h3orange1> <p><br> <regulartext1> We believe that all parts and devices, especially those created by young scientists on iGEM teams, should be created after consultation with team advisers and mentors. Additionally, the use of a variety of selective markers should be employed to ensure that laboratory strains are only stable in a lab environment. </regulartext1> | ||
</div> | </div> | ||
| - | |||
| - | |||
| - | + | </html> | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
Latest revision as of 23:35, 7 September 2012
iGEM 2012
The Team
Our Projects
Our Results
Parts
Bootcamp
Requisites
Attributions
Extras
Protocols
We are entering in new pairs of toxin anti-toxin pairs, but the parts registry already documents a pair of toxin-antitoxin from E. coli: RelE Toxin.
UCSF has a Biosafety Committee (http://or.ucsf.edu/ehs/7240-DSY/7422-DSY/8777), but it was not deemed necessary to meet with them regarding our project because all of our work falls under standard laboratory procedures that have prescribed regulations and safety protocols.
