Difference between revisions of "Team:UI Indonesia/Safety"

Line 211: Line 211:
 
.ref{
 
.ref{
 
font-size:18px;
 
font-size:18px;
 +
}
 +
#myBtn {
 +
  display: none;
 +
  position: fixed;
 +
  bottom: 20px;
 +
  right: 30px;
 +
  z-index: 99;
 +
  font-size: 18px;
 +
  border: none;
 +
  outline: none;
 +
  background-color:transparent;
 +
  color: white;
 +
  cursor: pointer;
 +
  padding: 15px;
 +
  border-radius: 4px;
 +
}
 +
 +
#myBtn:hover {
 +
  background-color: #555;
 
}
 
}
 
</style>
 
</style>
  
 
<body>
 
<body>
 +
<button onclick="topFunction()" id="myBtn" title="Go to top"><img src="https://image.flaticon.com/icons/png/512/14/14747.png" style="width:50px;height:50px;"></button>
 +
 
<!-- Navbar -->
 
<!-- Navbar -->
 
<nav class="navbar navbar-default">
 
<nav class="navbar navbar-default">
Line 285: Line 306:
 
   <script src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
 
   <script src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
 
   <script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/js/bootstrap.min.js"></script>
 
   <script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/js/bootstrap.min.js"></script>
 +
<script>
 +
// When the user scrolls down 20px from the top of the document, show the button
 +
window.onscroll = function() {scrollFunction()};
 +
 +
function scrollFunction() {
 +
    if (document.body.scrollTop > 20 || document.documentElement.scrollTop > 20) {
 +
        document.getElementById("myBtn").style.display = "block";
 +
    } else {
 +
        document.getElementById("myBtn").style.display = "none";
 +
    }
 +
}
 +
 +
// When the user clicks on the button, scroll to the top of the document
 +
function topFunction() {
 +
    document.body.scrollTop = 0;
 +
    document.documentElement.scrollTop = 0;
 +
}
 +
</script>
 
<!-- Footer -->
 
<!-- Footer -->
 
<footer class="w3-center w3-green w3-padding-64 w3-opacity w3-hover-opacity-off">
 
<footer class="w3-center w3-green w3-padding-64 w3-opacity w3-hover-opacity-off">

Revision as of 06:58, 11 October 2018

SAFETY AND SECURITY ASPECTS
In accordance to the iGEM safety rules, our team used a cellular organism classified in the Risk Group 1. For the purpose of cloning and expression, Escherichia coli K-12-strain derivates were primarily applied in the lab as the main experimental subjects. Standard plasmids with standard antibiotic resistance markers were designed to enhance functions of recombinants selection. To ensure the safety of ourselves and the project, we worked in a BSL-1 (Biosafety type 1) laboratory, following standard safety protocols (e.g. masks, gloves, googles, and protective clothing). The lab also includes the “clean-to-dirty” workflow area, which means that lab staffs do not return to a “clean” area after working in a “dirty” area. For instance, entering PCR room is forbidden after working with DNA isolation or bacterial cultures in DNA room.

One of our project’s part which raised concern about biosecurity is the synthetic hand-made Affitoxin (i.e. the binding domain of AB diphtheria exotoxin) design. The details regarding this part would be discussed in this page. The fact that this part originates from the modification of diphtheria toxin raises concern about safety and security, including the possibilities of dual-use research. Regarding safety issues, the main purpose of the creation of this part is to eliminate the toxic domain of the exotoxin, leaving only the binding domain to be used to test our chimeric HB-EGF/Tar receptor. However, this condition still leaves a security issue regarding dual-use possibilities. Additionally, the creation of this part, if successful, means that we have only isolated the necessary domains needed for binding assays. The full sequence could be used to construct another chimeric protein in which the Affitoxin is linked to a more harmful toxin or material and used to deliver that harmful part into the cytoplasm of human cells containing HB-EGF surface receptor. To handle this, our team are required to comply with rules of iGEM safety committee to be allowed to not publish the full sequence in the iGEM UI 2018 Wiki pages.
Team UI Indonesia
  igemui2018@gmail.com