Team:CBNU-Korea/Safety

From 2011.igem.org

(Difference between revisions)
 
(10 intermediate revisions not shown)
Line 1: Line 1:
-
{{:Team:CBNU-Korea/header}}
 
-
{{:Team:CBNU-Korea/Menu}}
 
-
 
<HTML>
<HTML>
-
<body>
+
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 +
<HEAD>
 +
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-
<br>
+
<Style type = "text/css">
-
<center>
+
-
<img src="https://static.igem.org/mediawiki/2011/3/3c/Cbnu_SI_001.png">
+
-
</center>
+
-
<br><br>
+
html{
 +
  scrollbar-face-color:#bfc4c1;
 +
  scrollbar-3dlight-color:#778a7f;
 +
  scrollbar-highlight-color:#7fa891;
 +
  scrollbar-shadow-color:#7fa891;
 +
  scrollbar-darkshadow-color:#778a7f;
 +
  scrollbar-arrow-color:#171315;
 +
  scrollbar-track-color:#7fa891;
 +
}
-
<p><img src="https://static.igem.org/mediawiki/2011/f/fa/Cbnu_bar.png"></p>
+
::-webkit-scrollbar {width: 8px; height: 8px; border: 3px solid #fff; }
 +
::-webkit-scrollbar-button:start:decrement, ::-webkit-scrollbar-button:end:increment {display: block; height: 10px; background: url('./images/bg.png') #efefef}
 +
::-webkit-scrollbar-track {background: #efefef; -webkit-border-radius: 10px; border-radius:10px; -webkit-box-shadow: inset 0 0 4px rgba(0,0,0,.2)}
 +
::-webkit-scrollbar-thumb {height: 50px; width: 50px; background: rgba(0,0,0,.2); -webkit-border-radius: 8px; border-radius: 8px; -webkit-box-shadow: inset 0 0 4px rgba(0,0,0,.1)}
 +
body{
 +
background-color:#000000;
 +
}
-
<br>
+
#test{
-
<p>
+
background-color:#000000;
-
<font size="4" color="yellow">
+
}
-
<b>Would any of your project ideas raise safety issues in terms of: <br><br>
+
-
researcher safety</b>
+
-
</font>
+
-
<br>
+
#top-section{
 +
border:none;
 +
}
-
<p>
+
#p-logo{
-
<font size="3" color="white">
+
overflow:hidden;
-
All of our protocols and experiments were basic cloning techniques. And experiment members of our team were trained to standard safety
+
display:none;
-
</font>
+
border:none;
-
</p>
+
}
-
<br>
+
#menubar{
 +
background-color:#000000;
 +
}
 +
#menubar:hover{
 +
background-color:transparent;
 +
}
 +
.left-menu li a {
 +
color: #ffffff;
 +
}
 +
.right-menu ul a {
 +
background-color:transparent;
 +
}
 +
.left-menu ul a {
 +
background-color:transparent;
 +
}
-
<p>
+
#search-controls{
-
<font size="4" color="yellow">
+
display:none;
-
<b>public safety</b>
+
}
-
</font>
+
-
<br>
+
#content {
 +
background:transparent;
 +
border:none;
 +
}
-
<font size="3" color="white">
+
.firstHeading{
-
Our project is consists of two parts that are experiments and software. The experiments are basic cloning procedure for synthesizing minimal chromosome with V. cholerae chromosomes. We are not using ‘BACTERIA’ V. cholerae but genome of V. cholerae is used to our experiments.
+
display:none;
-
</font>
+
}
-
</p>
+
#catlinks {
 +
display:none;
 +
}
-
<br>
 
-
<p>
+
#footer-box{
-
<font size="4" color="yellow">
+
display:none;
-
<b>environmental safety</b>
+
}
-
</font>
+
-
<br>
+
#test{
 +
margin-right:auto;
 +
margin-left:auto;
-
<font size="3" color="white">
+
line-height:30px;
-
To prevent the leak of transformed bacteria to environment, we always sterilize all the instruments and Bacteria and media containing bacteria were bleached before disposal.
+
-
</font>
+
-
</p><br>
+
 +
}
-
<img src="https://static.igem.org/mediawiki/2011/f/fa/Cbnu_bar.png">
+
#logo{
 +
width:700px;
 +
background:transparent;
 +
overflow:auto;
 +
margin-right:auto;
 +
margin-left:auto;
 +
}
-
<br><br>
 
-
<p>
+
</Style>
-
<font size="4" color="yellow">
+
</HEAD>
-
<b>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?</b>
+
-
</font>
+
-
<br>
+
-
<font size="3" color="white">
+
<body>
-
Every component of our new biobricks came from the iGEM 2011 distribution kit. The components thereof are guaranteed to be safe.
+
<div>
-
</font>
+
<a href="javascript:history.go(-1);"><img src="https://static.igem.org/mediawiki/2011/7/77/Synb_back.png"></a>
-
</p>
+
</div>
-
<br>
+
-
<img src="https://static.igem.org/mediawiki/2011/f/fa/Cbnu_bar.png"><br><br>
+
<div id="logo">
-
 
+
<img src="https://static.igem.org/mediawiki/2011/5/59/Synb_Biosecurity.png">
-
<p>
+
</div>
-
<font size="4" color="yellow"><b>Is there a local biosafety group, committee, or review board at your institution?
+
<div id="test" style="width:700px; height:450px; background:transparent; overflow:auto;">
-
If yes, what does your local biosafety group think about your project?
+
<br><font color=white size="4" face="Tahoma">
-
If no, which specific biosafety rules or guidelines do you have to consider in your country?
+
<u><b>a</b></u>. The software, the genome database, and the genome design tool which we plan to use are already in public domain. Therefore we do not need to establish additional limited access for biosecurity.<br>
-
</b>
+
<u><b>b</b></u>. Our database has only essential gene data that the organism must have for survival. The information will be obtained from the DEG database (<a href="http://tubic.tju.edu.cn/deg/" target="_blank">http://tubic.tju.edu.cn/deg/</a>). In addition most pathogenic genes are not essential genes. In case any pathogenic gene is included in the essential genes, we will establish limited access of gene database for biosecurity. There is no domestic regulation in Korea on obtaining the sequence of pathogenic genes.<br>
 +
<u><b>c</b></u>. In order to prevent any intentional abuse of pathogenic gene information (if which are included in this study), first, we will not make a disclosure of pathogenic or toxin gene data to our database. Second, the genome design tool developed will be released only with an official request from the head of the organization or department which should include nation, affiliation, group, name of PI, purpose, address, contact information (address, telephone, e-mail), etc. .   
</font>
</font>
 +
</div>
 +
</body>
-
<br>
 
-
 
-
<font size="3" color="white">
 
-
There is no organization that is specialized in safety issue of synthetic biology in Korea. So, we obey the guidelines that provided by Chung-Buk national Univ.
 
-
</font>
 
-
</p>
 
-
 
-
 
-
<br>
 
-
<img src="https://static.igem.org/mediawiki/2011/f/fa/Cbnu_bar.png"><br><br>
 
-
 
-
<p>
 
-
<font size="4" color="yellow"><b>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?</b>
 
-
</font>
 
-
<br>
 
-
<font size="3" color="white">
 
-
We think the best way to deal with safety issues is to encourage all iGEM teams to contribute in making one solid safety standard and make it official. Also, lectures related to safety issues can help ensure the enforcement of rules and requirements put forth by this official standard.
 
-
</font>
 
-
</p>
 
-
<br>
 
-
 
-
<p><img src="https://static.igem.org/mediawiki/2011/f/fa/Cbnu_bar.png"></p><br><br>
 
-
</body>
 
</HTML>
</HTML>

Latest revision as of 10:48, 29 September 2011


a. The software, the genome database, and the genome design tool which we plan to use are already in public domain. Therefore we do not need to establish additional limited access for biosecurity.
b. Our database has only essential gene data that the organism must have for survival. The information will be obtained from the DEG database (http://tubic.tju.edu.cn/deg/). In addition most pathogenic genes are not essential genes. In case any pathogenic gene is included in the essential genes, we will establish limited access of gene database for biosecurity. There is no domestic regulation in Korea on obtaining the sequence of pathogenic genes.
c. In order to prevent any intentional abuse of pathogenic gene information (if which are included in this study), first, we will not make a disclosure of pathogenic or toxin gene data to our database. Second, the genome design tool developed will be released only with an official request from the head of the organization or department which should include nation, affiliation, group, name of PI, purpose, address, contact information (address, telephone, e-mail), etc. .