Team:SYSU-Software/saft

From 2013.igem.org

(Difference between revisions)
 
(57 intermediate revisions not shown)
Line 8: Line 8:
<link href="https://2012.igem.org/Team:SYSU-Software/bootstrap.css?action=raw&ctype=text/css" rel="stylesheet" type="text/css" />
<link href="https://2012.igem.org/Team:SYSU-Software/bootstrap.css?action=raw&ctype=text/css" rel="stylesheet" type="text/css" />
<link href="https://2012.igem.org/Team:SYSU-Software/flatui.css?action=raw&ctype=text/css" rel="stylesheet" type="text/css" />
<link href="https://2012.igem.org/Team:SYSU-Software/flatui.css?action=raw&ctype=text/css" rel="stylesheet" type="text/css" />
-
<script src="https://2013.igem.org/Team:SYSU-Software/jquery.js?action=raw&ctype=text/javascript" type="text/javascript"></script>
+
<link href="https://2013.igem.org/Team:SYSU-Software/safety.css?action=raw&ctype=text/css" rel="stylesheet" type="text/css" />
-
<!--
+
<!-- <link href="safety/css/safety.css" rel="stylesheet" type="text/css" /> -->
-
<script src="http://code.jquery.com/jquery-1.9.1.min.js?action=raw&ctype=text/javascript" type="text/javascript"></script>
+
<link href="https://2013.igem.org/Team:SYSU-Software/header.css?action=raw&amp;ctype=text/css" rel="stylesheet" type="text/css" />
-
-->
+
 
 +
 
 +
<script src="https://2013.igem.org/Team:SYSU-Software/jquery-1.9.1.min.js?action=raw&ctype=text/javascript" type="text/javascript"></script>
 +
<script src="https://2013.igem.org/Team:SYSU-Software/bootstrap.min.js?action=raw&ctype=text/javascript" type="text/javascript"></script>
<script src="https://2013.igem.org/Team:SYSU-Software/prefix.js?action=raw&ctype=text/javascript" type="text/javascript"></script>
<script src="https://2013.igem.org/Team:SYSU-Software/prefix.js?action=raw&ctype=text/javascript" type="text/javascript"></script>
 +
<head>
<head>
<meta charset="utf-8">
<meta charset="utf-8">
Line 19: Line 23:
<body>
<body>
-
<div id="main">
+
<div id="navigation"></div>
-
<div id="navigation"></div>
+
-
<span ><a href = "https://2013.igem.org/Main_Page"> <img style="height:55px;width:55px;margin-bottom:30px;margin-left:20px;margin-top:10px" src="https://static.igem.org/mediawiki/2012/1/13/Igemwhite_back.png"></a></span>
+
-
      <div id="main-box">
+
-
  <!--<img src="https://static.igem.org/mediawiki/2012/d/d9/Test.png" alt="test">-->
+
-
          <div id="title-box" class="tooltip fade top in">
+
-
          <div class="tooltip-arrow"></div>
+
-
            <div class="tooltip-inner">SAFTY</div>
+
-
          </div>
+
-
          <div id="detail-box">
+
-
          <article>
+
-
Q1:Would any of your project ideas raise safety issues in terms of: researcher safety, public safety, or environmental safety?
+
-
No, just like other office software, it doesn't involve harmful materials or attack. It concentrates on viewing and analyzing biological data and designing  regulatory elements of metabolic networks, which will be no possible to cause any public or environmental problem.
+
-
   
+
-
Q2: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?
+
-
    As a software team, we are not intended to make new biobricks and no safety issues could come out from it. For a software, the most important safety concern is network safety. Our software can be used offline, so it's safer to a large extent. Other software teams should also pay attention to the network safety of their software.
+
-
Q3: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?
+
<div class="wrapper colored-wrapper-ddf4ef">
-
    Yes, there is a biosafety committee in our school, and Center for Disease Control and Prevention in our city. We consulted to them, and they thought our project is safe for the reasons blow:
+
<div id="safety-container" > 
-
    There are four pars in the software. Among them, GenomeBrowser, MetaNetwork and Simulator are all tools assisting scientists to view or analyze biological data, which will not generate harmful outcomes. Riboswitch and SiRNA focus on the design of regulatory elements of metabolic networks, thus it's also away from harms.
+
    <div id="safety-header">
-
      
+
      <img id="safety-font" src="https://static.igem.org/mediawiki/2013/4/4d/Safety-font.png">
-
Q4: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?
+
    </div>
-
    We advise that it can establish a risk evaluating system, giving each BioBrick a safety index, to assess the quality and reliability of them.
+
        <div class="safety-q" id="safety-q1"> 
-
              </article>
+
      <span class="q-text" id="q2-text" style="color:orange">
-
          </div>
+
<span class="q-light" id="q2-light">
-
       </div>
+
<!--  <img src="https://static.igem.org/mediawiki/2013/d/d2/Pin4.png"> -->
-
       <footer></footer>
+
        </span><p style="display:inline-block">Safety forms were approved on September 17 2013,by Kelly Drinkwater<br><a href="https://static.igem.org/mediawiki/2013/0/07/IGEM_2013_Basic_Safety_Form%28SYSU-software%29-rev.pdf">IGEM_2013_Basic_Safety_Form.pdf</a><br><a href="https://static.igem.org/mediawiki/2013/5/5c/IGEM_2013_Software_form%28SYSU-software%29-rev.pdf">IGEM_2013_Software_form.pdf</a></p>
 +
      </span>   
 +
      <span class="q-text" id="q2-text"><span class="q-light" id="q2-light"><img src="https://static.igem.org/mediawiki/2013/d/d2/Pin4.png"></span><p>Q1: Are you using the iGEM Software repository at github.com/igemsoftware?If you have instead stored your code elsewhere, please explain where and why you have put it there.If your code is not in the iGEM repository, are you using any version control
 +
system such as Git, CVS, or SVN?</p></span>
 +
 
 +
      <span class="q-pen" id="q1-pen"><img src="https://static.igem.org/mediawiki/2013/f/f4/Pin2.png"></span>
 +
      <span class="q-answer" id="q1-answer">
 +
      We will push our code to github.com/igemsoftware in time. However, the network connection between an overseas server and us is not satisfactory. So our code is stored at https://git.oschina.net/guoskyhero/igem2013_sysu/, and we use Git as the version control system. If there is any demand for our code, please feel free to contact us.
 +
      </span>
 +
     </div>
 +
 
 +
    <div class="safety-q" id="safety-q2">
 +
      <span class="q-text" id="q2-text">
 +
          <span class="q-light" id="q2-light">
 +
          <img src="https://static.igem.org/mediawiki/2013/d/d2/Pin4.png">
 +
          </span>
 +
          <p>Q2: a. Does your software store any private data supplied by the user? (For example:
 +
the user's name and email address, passwords, DNA sequences, circuit designs,
 +
etc.) If yes, please describe what kind of data is stored. If no, skip the rest of this
 +
question and move on to question 3.</p>
 +
      </span>
 +
       <span class="q-pen" id="q2-pen"><img src="https://static.igem.org/mediawiki/2013/f/f4/Pin2.png"></span>
 +
       <span class="q-answer" id="q2-answer">
 +
        Yes, our software stores user's name, gender, password, DNA sequences, circuit designs.
 +
      </span>
</div>
</div>
 +
<div class="safety-q" id="safety-q2">
 +
      <span class="q-text" id="q2-text"><span class="q-light" id="q2-light"><img src="https://static.igem.org/mediawiki/2013/d/d2/Pin4.png"></span><p>Q2: b. What is the URL or IP address where the user's private data is stored? Where is
 +
the physical computer or hard drive that contains the user's private data?</p></span>
 +
 +
      <span class="q-pen" id="q2-pen"><img src="https://static.igem.org/mediawiki/2013/f/f4/Pin2.png"></span>
 +
      <span class="q-answer" id="q2-answer">
 +
        User's private data is stored on user's own PC or server.
 +
      </span>
 +
</div>
 +
<div class="safety-q" id="safety-q2">
 +
      <span class="q-text" id="q2-text"><span class="q-light" id="q2-light"><img src="https://static.igem.org/mediawiki/2013/d/d2/Pin4.png"></span><p>Q2: c. Please describe any encryption, password protection, etc. that you use to protect
 +
the user's data. (It is not mandatory to have such protections, but if you do,
 +
describe them.)</p></span>
 +
 +
      <span class="q-pen" id="q2-pen"><img src="https://static.igem.org/mediawiki/2013/f/f4/Pin2.png"></span>
 +
      <span class="q-answer" id="q2-answer">
 +
        User's password is encrypted by Message-Digest Algorithm 5 (MD5).
 +
      </span>
 +
    </div>
 +
 +
    <div class="safety-q" id="safety-q3">
 +
      <span class="q-text" id="q3-text"><span class="q-light" id="q2-light"><img src="https://static.igem.org/mediawiki/2013/d/d2/Pin4.png"></span><p>Q3: Does your software include any other security features? Please describe them here.</p></span>
 +
 +
      <span class="q-pen" id="q3-pen"><img src="https://static.igem.org/mediawiki/2013/f/f4/Pin2.png"></span>
 +
      <span class="q-answer" id="q3-answer">
 +
        The users are required to log in before using the software, and their designs are stored in their own account. We use a cryptographic algorithm to encrypt the user name and password when it is thansfered between the client and server. What's more, we  create a different session key each time before the user login, which can resist the replay attack.
 +
      </span>
 +
    </div>
 +
 +
    <div class="safety-q" id="safety-q4">
 +
      <span class="q-text" id="q4-text"><span class="q-light" id="q2-light"><img src="https://static.igem.org/mediawiki/2013/d/d2/Pin4.png"></span><p>Q4: Does your software let the user create a design by choosing parts/genes from a
 +
list/database, such as the Registry? If so, which lists/databases are included? Is there any
 +
restriction on which parts/genes the user can choose?
 +
<p></span>
 +
 +
      <span class="q-pen" id="q4-pen"><img src="https://static.igem.org/mediawiki/2013/f/f4/Pin2.png"></span>
 +
      <span class="q-answer" id="q4-answer">
 +
        Yes, our software let the users create a design by choosing parts/gene from the Registry. We didn't set restriction on which parts the user can choose, as the parts in the Registry is believed safe.
 +
      </span>
 +
    </div>
 +
 +
    <div class="safety-q" id="safety-q5">
 +
      <span class="q-text" id="q5-text"><span class="q-light" id="q2-light"><img src="https://static.igem.org/mediawiki/2013/d/d2/Pin4.png"></span><p>Q5: Does your software allow users to write new data into any public lists or databases? If so,
 +
do you check the new data for errors before allowing it to be written?</p></span>
 +
 +
      <span class="q-pen" id="q5-pen"><img src="https://static.igem.org/mediawiki/2013/f/f4/Pin2.png"></span>
 +
      <span class="q-answer" id="q5-answer">
 +
        No, our software doesn't allow users to write new data into public lists or database.
 +
      </span>
 +
    </div>
 +
 +
    <div class="safety-q" id="safety-q6">
 +
      <span class="q-text" id="q6-text"><span class="q-light" id="q2-light"><img src="https://static.igem.org/mediawiki/2013/d/d2/Pin4.png"></span><p>Q6: Does your software include any other features that encourage the user to create safe
 +
designs? Please describe them here.</p></span>
 +
 +
      <span class="q-pen" id="q6-pen"><img src="https://static.igem.org/mediawiki/2013/f/f4/Pin2.png"></span>
 +
      <span class="q-answer" id="q6-answer">
 +
        We set some reminders in the software, which encourage the user to create safe designs.
 +
      </span>
 +
    </div>
 +
 +
    <div class="safety-q" id="safety-q7">
 +
      <span class="q-text" id="q7-text"><span class="q-light" id="q2-light"><img src="https://static.igem.org/mediawiki/2013/d/d2/Pin4.png"></span><p>Q7: Is your team also doing biological work in a wet lab?If so, you need to complete the iGEM Biosafety form on 2013.igem.org/Safety.</p></span>
 +
      <span class="q-pen" id="q7-pen"><img src="https://static.igem.org/mediawiki/2013/f/f4/Pin2.png"></span>
 +
      <span class="q-answer" id="q7-answer">
 +
        Yes.     
 +
      </span>   
 +
     
 +
    </div>   
 +
  </div>
 +
<!--page footer-->
 +
  <div id="sysu-footer"> 
 +
    <img id="bottom-image" src="https://static.igem.org/mediawiki/2013/d/d9/Sysu-footer.png">
 +
  </div>
 +
</div>
 +
</body>
</body>
</html>
</html>

Latest revision as of 18:05, 27 September 2013

Team:SYSU-Software new

Safety forms were approved on September 17 2013,by Kelly Drinkwater
IGEM_2013_Basic_Safety_Form.pdf
IGEM_2013_Software_form.pdf

Q1: Are you using the iGEM Software repository at github.com/igemsoftware?If you have instead stored your code elsewhere, please explain where and why you have put it there.If your code is not in the iGEM repository, are you using any version control system such as Git, CVS, or SVN?

 We will push our code to github.com/igemsoftware in time. However, the network connection between an overseas server and us is not satisfactory. So our code is stored at https://git.oschina.net/guoskyhero/igem2013_sysu/, and we use Git as the version control system. If there is any demand for our code, please feel free to contact us.

Q2: a. Does your software store any private data supplied by the user? (For example: the user's name and email address, passwords, DNA sequences, circuit designs, etc.) If yes, please describe what kind of data is stored. If no, skip the rest of this question and move on to question 3.

 Yes, our software stores user's name, gender, password, DNA sequences, circuit designs.

Q2: b. What is the URL or IP address where the user's private data is stored? Where is the physical computer or hard drive that contains the user's private data?

 User's private data is stored on user's own PC or server.

Q2: c. Please describe any encryption, password protection, etc. that you use to protect the user's data. (It is not mandatory to have such protections, but if you do, describe them.)

 User's password is encrypted by Message-Digest Algorithm 5 (MD5).

Q3: Does your software include any other security features? Please describe them here.

 The users are required to log in before using the software, and their designs are stored in their own account. We use a cryptographic algorithm to encrypt the user name and password when it is thansfered between the client and server. What's more, we create a different session key each time before the user login, which can resist the replay attack.

Q4: Does your software let the user create a design by choosing parts/genes from a list/database, such as the Registry? If so, which lists/databases are included? Is there any restriction on which parts/genes the user can choose?

Yes, our software let the users create a design by choosing parts/gene from the Registry. We didn't set restriction on which parts the user can choose, as the parts in the Registry is believed safe.

Q5: Does your software allow users to write new data into any public lists or databases? If so, do you check the new data for errors before allowing it to be written?

 No, our software doesn't allow users to write new data into public lists or database.

Q6: Does your software include any other features that encourage the user to create safe designs? Please describe them here.

 We set some reminders in the software, which encourage the user to create safe designs.

Q7: Is your team also doing biological work in a wet lab?If so, you need to complete the iGEM Biosafety form on 2013.igem.org/Safety.

 Yes.

Retrieved from "http://2013.igem.org/Team:SYSU-Software/saft"