Line 2: | Line 2: | ||
<head> | <head> | ||
− | + | <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | < | + | <title>Team:HFUT-China</title> |
− | + | ||
− | + | ||
− | + | <link href="https://2017.igem.org/Template:HFUT-China/Safety/css/headerCss?action=raw&ctype=text/css" rel="stylesheet"/> | |
− | + | <link href="https://2017.igem.org/Template:HFUT-China/Safety/css/stylewikiCss?action=raw&ctype=text/css" rel="stylesheet"/> | |
− | + | <link href="https://2017.igem.org/Template:HFUT-China/MainPage/css/styleCss?action=raw&ctype=text/css" rel="stylesheet" /> | |
− | + | </head> | |
− | + | ||
− | + | ||
− | + | <center> | |
− | + | <div class="header" style="z-index:999;position:absolute"> | |
− | + | <ul class="nav"> | |
− | + | <li><a href="https://2017.igem.org/Team:HFUT-China"> Main page </a></li> | |
− | + | <li><a href="https://2017.igem.org/Team:HFUT-China/Description"> Project <img src="img/xia.png" width="12px";> </a> | |
− | + | <ul> | |
− | + | <li class="selfnav hef"><a href="https://2017.igem.org/Team:HFUT-China/Description"><font class="hef">Description</font></a></li> | |
− | + | <li class="selfnav hef"><a href="https://2017.igem.org/Team:HFUT-China/Design"><font class="hef">Design</font></a></li> | |
− | + | <li class="selfnav hef"><a href="https://2017.igem.org/Team:HFUT-China/Contribution"><font class="hef">Contribution</font></a></li> | |
− | + | <li class="selfnav hef"><a href="https://2017.igem.org/Team:HFUT-China/Demonstrate"><font class="hef">Demonstrate</font></a></li> | |
− | + | </ul> | |
− | + | </li> | |
− | + | <li><a href="https://2017.igem.org/Team:HFUT-China/Model"> Software <img src="img/xia.png" width="12px";> </a> | |
− | + | <ul> | |
− | + | <li class="selfnav"><a href="https://2017.igem.org/Team:HFUT-China/Model"><font class="hef" color="#000">Model</font></a></li> | |
− | + | <li class="selfnav"><a href="href="https://2017.igem.org/Team:HFUT-China/Improve"><font class="hef" color="#000">Improve</font></a></li> | |
− | + | </ul> | |
− | + | </li> | |
− | + | <li><a href="https://2017.igem.org/Team:HFUT-China/Notebook"> Documents <img src="img/xia.png" width="12px";> </a> | |
− | + | <ul> | |
− | + | <li class="selfnav"><a href="https://2017.igem.org/Team:HFUT-China/Notebook"><font class="hef" color="#000">Notebook</font></a></li> | |
− | + | <li class="selfnav"><a href="https://2017.igem.org/Team:HFUT-China/Safety"><font class="hef" color="#000">Safety</font></a></li> | |
− | + | <li class="selfnav"><a href="https://2017.igem.org/Team:HFUT-China/User_guide"><font class="hef" color="#000">User guide</font></a></li> | |
− | + | </ul> | |
− | + | </li> | |
− | + | <li><a href="https://2017.igem.org/Team:HFUT-China/Team">Team <img src="img/xia.png" width="12px";></a> | |
− | + | <ul> | |
− | + | <li class="selfnav"><a href="https://2017.igem.org/Team:HFUT-China/Team"><font class="hef" color="#000">Members</font></a></li> | |
− | + | <li class="selfnav"><a href="https://2017.igem.org/Team:HFUT-China/Collaborations"><font class="hef" color="#000">Collaborations</font></a></li> | |
− | + | <li class="selfnav"><a href="https://2017.igem.org/Team:HFUT-China/Attributions"><font class="hef" color="#000">Attributions</font></a></li> | |
− | + | </ul> | |
− | + | </li> | |
− | + | <li><a href="#"> Human practice </a> | |
− | + | <ul> | |
− | + | <li class="selfnav"><a href="https://2017.igem.org/Team:HFUT-China/Silver"><font class="hef" color="#000">Silver HP</font></a></li> | |
− | + | <li class="selfnav"><a href="https://2017.igem.org/Team:HFUT-China/Gold_Integrated"><font class="hef" color="#000">Integrated<br>and Gold</font></a></li> | |
− | + | </ul> | |
− | + | </li> | |
− | + | </ul> | |
− | + | </div> | |
− | + | <div style="height:160px"></div> | |
− | + | <div class="title" style="margin-top: 10px"><b><font color="#0089a7">Project</font> <font color="#555555">Safety</font></b></div> | |
− | + | <div class="subtitle"><font color="#555555">We will use a conversation to prove that our software is safe ~ :)</font></div> | |
− | + | <div class="title" style="margin-top: 90px"><b><font color="#666">Q & A</font></b></div> | |
− | + | <div class="p"> | |
− | + | <div class="q">Q1: Who will use your product?<br> What opinions do these people have about your project?<br><br></div> | |
− | + | <div class="a">A1:Synthetic biologists who want to improve their working efficiency in labs and simplify the preparation procedure of their experiments. </div> | |
− | + | <hr class="line"> | |
− | + | </div> | |
− | + | <div class="p"> | |
− | + | <div class="q">Q2: Where will your product be used?<br> On a farm, in a factory, inside human bodies, in the ocean?<br><br> | |
− | + | </div> | |
− | + | <div class="a">A2:We can use the product in the lab.</div> <hr class="line"> | |
− | + | </div> | |
− | + | <div class="p"> | |
− | + | <div class="q">Q3: If your product is successful, who will receive benefits and who will be harmed?<br><br></div> | |
− | + | <div class="a">A3:The researchers whose assignment is scrutinizing large volumes of literature to find useful information for their project will receive benefits if our product is successful. This procedure can be done by our software. However, the software may replace some people`s work, which would lower their salary.</div> | |
− | + | <hr class="line"> | |
− | + | </div> | |
− | + | <div class="p"> | |
− | + | <div class="q">Q4: What happens when it's all used up? Will it be sterilized, discarded, or recycled?<br><br></div> | |
− | + | <div class="a">A4:Software will never be used up.</div> | |
− | + | <hr class="line"> | |
− | + | </div> | |
− | + | <div class="p"> | |
− | + | <div class="q">Q5: Is it safer, cheaper, or better than other technologies that do the same thing?<br><br></div> | |
− | + | <div class="a">A5:According to our investigation, there is currently no other software that aims at literature analysis, which is our new function this year.</div> | |
− | + | <hr class="line"> | |
− | + | </div> | |
− | + | <div class="p"> | |
− | + | <div class="q">Q6: Does your software allow users to submit new data into any public lists or databases?<br> If so, do you check the new data for errors before allowing it to be written?<br><br></div> | |
− | + | <div class="a">A6:No, we do not allow users to submit new data into any public lists or databases, like ncbi or iGEM website. Users can only submit their data to our own project database.</div> | |
− | + | <hr class="line"> | |
− | + | </div> | |
− | + | <div class="p"> | |
− | + | <div class="q">Q7: Are you using the iGEM Software repository at github.com/igemsoftware?<br> If you have instead stored your code elsewhere, please explain where and why you have put it there.<br> If your code is not in the iGEM repository, are you using any version control system such as Git, CVS, or SVN?<br><br></div> | |
− | + | <div class="a">A7:Because it will be freer for us to design the software. What’s more, we can correct the errors which need specific permission more easily. We will submit the code to the iGEM Github Repository when we are about to accomplish the design progress. We use git as the version controlling system.</div> | |
− | + | <hr class="line"> | |
− | + | </div> | |
− | + | <div class="p"> | |
− | + | <div class="q">Q8: What is the URL or IP address where the user's private data is stored?<br> Where is the physical computer or hard drive that contains the user's private data?<br><br></div> | |
− | + | <div class="a">A8:When it comes to server, we use Cloud Host provided by safe and reliable host service providers, which are able to offer us security services on both hardware and system level. Unit test and system test will be done to ensure the security of our software.</div> | |
− | + | <hr class="line"> | |
− | + | </div> | |
− | + | <div class="p"> | |
− | + | <div class="q">Q9: What other actions do you take to enhance the security of your software?<br><br></div> | |
− | + | <div class="a">A9:We do not open outside visit permission, which means the users’ information in the database can only be accessed locally. For more information, you can refer to our API document.</div> | |
− | + | </div> | |
− | + | <div class="footer"> | |
− | + | <div class="foot-icon"> | |
− | + | ||
− | + | <a href=""><img src="https://static.igem.org/mediawiki/2017/5/51/Fb.png" class="icon"></a> | |
− | + | <a href=""><img src="https://static.igem.org/mediawiki/2017/d/da/Emial.png" class="icon"></a> | |
− | + | <a href=""><img src="https://static.igem.org/mediawiki/2017/5/51/Git.png" class="icon"></a> | |
− | + | </div> | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
</div> | </div> | ||
+ | </center> | ||
+ | |||
</html> | </html> |
Revision as of 13:22, 15 October 2017
Project Safety
We will use a conversation to prove that our software is safe ~ :)
Q & A
Q1: Who will use your product?
What opinions do these people have about your project?
What opinions do these people have about your project?
A1:Synthetic biologists who want to improve their working efficiency in labs and simplify the preparation procedure of their experiments.
Q2: Where will your product be used?
On a farm, in a factory, inside human bodies, in the ocean?
On a farm, in a factory, inside human bodies, in the ocean?
A2:We can use the product in the lab.
Q3: If your product is successful, who will receive benefits and who will be harmed?
A3:The researchers whose assignment is scrutinizing large volumes of literature to find useful information for their project will receive benefits if our product is successful. This procedure can be done by our software. However, the software may replace some people`s work, which would lower their salary.
Q4: What happens when it's all used up? Will it be sterilized, discarded, or recycled?
A4:Software will never be used up.
Q5: Is it safer, cheaper, or better than other technologies that do the same thing?
A5:According to our investigation, there is currently no other software that aims at literature analysis, which is our new function this year.
Q6: Does your software allow users to submit new data into any public lists or databases?
If so, do you check the new data for errors before allowing it to be written?
If so, do you check the new data for errors before allowing it to be written?
A6:No, we do not allow users to submit new data into any public lists or databases, like ncbi or iGEM website. Users can only submit their data to our own project database.
Q7: 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?
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?
A7:Because it will be freer for us to design the software. What’s more, we can correct the errors which need specific permission more easily. We will submit the code to the iGEM Github Repository when we are about to accomplish the design progress. We use git as the version controlling system.
Q8: 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?
Where is the physical computer or hard drive that contains the user's private data?
A8:When it comes to server, we use Cloud Host provided by safe and reliable host service providers, which are able to offer us security services on both hardware and system level. Unit test and system test will be done to ensure the security of our software.
Q9: What other actions do you take to enhance the security of your software?
A9:We do not open outside visit permission, which means the users’ information in the database can only be accessed locally. For more information, you can refer to our API document.