Difference between revisions of "Team:USTC-Software/Safety"

(Prototype team page)
 
 
(6 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{USTC-Software}}
+
{{USTC-Software/html/header}}
 +
 
 
<html>
 
<html>
  
 +
<link href="https://2019.igem.org/Template:USTC-Software/css/default?action=raw&ctype=text/css" rel="stylesheet"
 +
      type="text/css"/>
 +
<link href="https://2019.igem.org/Template:USTC-Software/css/bootstrap?action=raw&ctype=text/css" rel="stylesheet"
 +
      type="text/css"/>
 +
<script src="https://2019.igem.org/Template:USTC-Software/js/jquery?action=raw&ctype=text/javascript"
 +
        type="text/javascript"></script>
 +
<script src="https://2019.igem.org/Template:USTC-Software/js/popper?action=raw&ctype=text/javascript"
 +
        type="text/javascript"></script>
 +
<script src="https://2019.igem.org/Template:USTC-Software/js/bootstrap?action=raw&ctype=text/javascript"
 +
        type="text/javascript"></script>
  
<div class="column full_size">
+
<div id="autoMenu2" class="autoMenu2"></div>
 +
<div class="container">
 +
  <div class="row">
 +
<!--    <div class="col-lg-2 col-md-0">-->
 +
<!--      <div class="autoMenu d-none d-lg-block" data-autoMenu id="autoMenu"></div>-->
 +
<!--    </div>-->
 +
    <div class="col-lg-12 col-md-12">
 +
      <div class="card page-content">
 +
        <div class="card-body">
 +
          <h1 class="text-center">Safety</h1>
 +
          <h3>Safety concerns with Forsyn</h3>
 +
          <div class="passage">
 +
          Foresyn is a user-friendly platform that was designed specifically for synthetic biologists to solve such issues above. Just like its name, Foresyn can foresee the targeted improvements to the users' experiment, give advise and therefore increase productivity, literally by the neoteric workflow management based on our customized database.
 +
          </div>
 +
          <h4>Q: Will Forsyn harm the human body or the environment?</h4>
 +
          <div class="passage">
 +
            A: As a software, Forsyn runs on the computer. It is safe for the human body and the environment.
 +
          </div>
 +
          <h4>Q: Is Forsyn harmful to the user's personal computer?</h4>
 +
          <div class="passage">
 +
            A: Forsyn is safe for the user's personal computer. All functions on Forsyn run on our server.
 +
            Users only need to upload their files, and the server will automatically transfer the result to the user's browser.
 +
          </div>
 +
          <h4>Q: Does It Have Any Risks In Laboratory?</h4>
 +
          <div class="passage">
 +
            A: Forsyn runs as a web page. It aims to provide more detailed and comprehensive biobrick information
 +
            and accurate prediction results of promoters to synthetic biologists. We won’t use any plasmid or bacteria.
 +
            No wet-lab experiments and no pollution to the environment.
 +
          </div>
 +
          <h4>Q: Does Forsyn have any potential threats to users’ personal information?</h4>
 +
          <div class="passage">
 +
            A: Forsyn never collects any personal information. Users can use it freely without worrying about personal information disclosure.
 +
          </div>
 +
          <h4>Q: Will our project infringe on database copyright?</h4>
 +
          <div class="passage">
 +
            A: Not at all. We listened to Dr. Lei Ruipeng’s report on “Ethical issues and governance of synthetic biology” on CCic,
 +
            and mentioned the issue of database copyright. At the same time, we also discussed with the judges about database copyright.
 +
          </div>
 +
        </div>
 +
      </div>
 +
    </div>
 +
  </div>
  
<h1> Safety </h1>
 
<p>Please visit the <a href="https://2019.igem.org/Safety">Safety Hub</a> to find this year's safety requirements & deadlines, and to learn about safe & responsible research in iGEM.</p>
 
 
<p>On this page of your wiki, you should write about how you are addressing any safety issues in your project. The wiki is a place where you can <strong>go beyond the questions on the safety forms</strong>, and write about whatever safety topics are most interesting in your project. (You do not need to copy your safety forms onto this wiki page.)</p>
 
  
 
</div>
 
</div>
 +
<!--autoMenu css and js files, generate Menu of each article-->
 +
<!--<link href="https://2019.igem.org/Template:USTC-Software/css/autoMenu?action=raw&ctype=text/css" rel="stylesheet">-->
 +
<!--<script src="https://2019.igem.org/Template:USTC-Software/js/autoMenu?action=raw&ctype=text/javascript"></script>-->
  
 +
<!--autoMenu css and js files, generate Menu of each article-->
 +
<link href="https://2019.igem.org/Template:USTC-Software/css/autoMenu2?action=raw&ctype=text/css" rel="stylesheet">
 +
<script src="https://2019.igem.org/Template:USTC-Software/js/autoMenu2?action=raw&ctype=text/javascript"></script>
  
<div class="column two_thirds_size">
+
<!--scrollBar js. when scroll down, a cat will be there-->
<h3>Safe Project Design</h3>
+
<script src="https://2019.igem.org/Template:USTC-Software/js/addScrollBar?action=raw&ctype=text/javascript"></script>
  
<p>Does your project include any safety features? Have you made certain decisions about the design to reduce risks? Write about them here! For example:</p>
+
<!-- make content Menu fixed-->
 +
<script src="https://2019.igem.org/Template:USTC-Software/js/makeIndexFixed?action=raw&ctype=text/javascript"></script>
  
<ul>
+
<!--add background-->
<li>Choosing a non-pathogenic chassis</li>
+
<script src="https://2019.igem.org/Template:USTC-Software/js/addBackground?action=raw&ctype=text/javascript"></script>
<li>Choosing parts that will not harm humans / animals / plants</li>
+
<li>Substituting safer materials for dangerous materials in a proof-of-concept experiment</li>
+
<li>Including an "induced lethality" or "kill-switch" device</li>
+
</ul>
+
  
</div>
+
<link href="https://2019.igem.org/Template:USTC-Software/css/pageContent?action=raw&ctype=text/css" rel="stylesheet">
  
<div class="column third_size">
+
<!-- some updated css style -->
<h3>Safe Lab Work</h3>
+
<!--<style>-->
 +
<!--div.card p {margin: 20px;}-->
 +
<!--div.card h2,h3,h4 {margin: 25px;}-->
 +
<!--div.card h1 {margin-top: 30px;}-->
 +
<!--div.card img {margin-left: 30px; margin-right:30px;}-->
 +
<!--</style>-->
  
<p>What safety procedures do you use every day in the lab? Did you perform any unusual experiments, or face any unusual safety issues? Write about them here!</p>
+
</html>
  
 
+
{{USTC-Software/html/footer}}
 
+
</html>
+

Latest revision as of 14:52, 20 October 2019

Safety

Safety concerns with Forsyn

Foresyn is a user-friendly platform that was designed specifically for synthetic biologists to solve such issues above. Just like its name, Foresyn can foresee the targeted improvements to the users' experiment, give advise and therefore increase productivity, literally by the neoteric workflow management based on our customized database.

Q: Will Forsyn harm the human body or the environment?

A: As a software, Forsyn runs on the computer. It is safe for the human body and the environment.

Q: Is Forsyn harmful to the user's personal computer?

A: Forsyn is safe for the user's personal computer. All functions on Forsyn run on our server. Users only need to upload their files, and the server will automatically transfer the result to the user's browser.

Q: Does It Have Any Risks In Laboratory?

A: Forsyn runs as a web page. It aims to provide more detailed and comprehensive biobrick information and accurate prediction results of promoters to synthetic biologists. We won’t use any plasmid or bacteria. No wet-lab experiments and no pollution to the environment.

Q: Does Forsyn have any potential threats to users’ personal information?

A: Forsyn never collects any personal information. Users can use it freely without worrying about personal information disclosure.

Q: Will our project infringe on database copyright?

A: Not at all. We listened to Dr. Lei Ruipeng’s report on “Ethical issues and governance of synthetic biology” on CCic, and mentioned the issue of database copyright. At the same time, we also discussed with the judges about database copyright.