(6 intermediate revisions by 3 users not shown) | |||
Line 52: | Line 52: | ||
form_info.ajax_URL = "https://2016.igem.org/cgi/forms/form.cgi"; | form_info.ajax_URL = "https://2016.igem.org/cgi/forms/form.cgi"; | ||
</script> | </script> | ||
− | <script src="https://igem.org/Template:JS/ | + | <script src="https://igem.org/Template:JS/KForms_2pt4?action=raw&ctype=text/javascript"></script> |
<div class="oneColumn"> | <div class="oneColumn"> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
<table id="safety_peas_container"> | <table id="safety_peas_container"> | ||
Line 70: | Line 60: | ||
<td colspan="2"> | <td colspan="2"> | ||
<img src="https://static.igem.org/mediawiki/igem.org/c/cd/Students_fill_safety_form.png" class="safety_peas"> | <img src="https://static.igem.org/mediawiki/igem.org/c/cd/Students_fill_safety_form.png" class="safety_peas"> | ||
− | <p>Students complete Final Safety Form (Deadline: | + | <p>Students complete Final Safety Form (Deadline: September 16)</p> |
</td> | </td> | ||
</tr> | </tr> | ||
Line 85: | Line 75: | ||
</table> | </table> | ||
− | <h2>Due | + | <h2>Due September 16</h2> |
<p>This form is for you to tell us all about your project, the organisms/parts you are using, the potential risks of your project, and what you are doing to reduce those risks.</p> | <p>This form is for you to tell us all about your project, the organisms/parts you are using, the potential risks of your project, and what you are doing to reduce those risks.</p> | ||
Line 92: | Line 82: | ||
<li><strong>We encourage STUDENTS, instead of instructors, to complete this form. However, you will need an Instructor or PI to sign and submit this form.</strong></li> | <li><strong>We encourage STUDENTS, instead of instructors, to complete this form. However, you will need an Instructor or PI to sign and submit this form.</strong></li> | ||
<li>While you type, this form will remember your answers. When you are finished, press the "Submit" button at the bottom to send your form to the iGEM Safety Committee.</li> | <li>While you type, this form will remember your answers. When you are finished, press the "Submit" button at the bottom to send your form to the iGEM Safety Committee.</li> | ||
− | <li>Submit this form by | + | <li>Submit this form by September 16.</li> |
<li>If you will not be able to complete this form before the deadline, please email us (safety AT igem DOT org) and tell us about your situation.</li> | <li>If you will not be able to complete this form before the deadline, please email us (safety AT igem DOT org) and tell us about your situation.</li> | ||
</ul> | </ul> | ||
Line 110: | Line 100: | ||
<br /> | <br /> | ||
− | <p>Please <a href="https:// | + | <p>Please <a href="https://2016.igem.org/File:TeamName_Safety2016_Spreadsheet.xlsx" target="_blank">visit this page</a> to download a blank copy of the spreadsheet for this question. (If you need a CSV version instead of XLSX, <a href="https://2016.igem.org/File:TeamName_Safety2016_Spreadsheet.csv" target="_blank">visit this page</a>.)</p> |
<p>Complete the spreadsheet. Include all whole organisms that you will handle in the lab, whether you are using them as a chassis or for some other reason. Include all <strong>new</strong> or <strong>highly modified</strong> protein coding parts that you are using. If you submitted a Check-In for an organism or part, you should still include it in this spreadsheet.</p> | <p>Complete the spreadsheet. Include all whole organisms that you will handle in the lab, whether you are using them as a chassis or for some other reason. Include all <strong>new</strong> or <strong>highly modified</strong> protein coding parts that you are using. If you submitted a Check-In for an organism or part, you should still include it in this spreadsheet.</p> | ||
Line 136: | Line 126: | ||
<br /> | <br /> | ||
− | <p><strong><a href="" target="_blank" id="spreadsheet_upload"><button type="button">Upload Spreadsheet</button></a> -- Please do not change the "Destination Filename"!</strong></p> | + | <p><strong><a href="" target="_blank" id="spreadsheet_upload"><button type="button">Upload Spreadsheet</button></a> -- Please do not change the "Destination Filename"!</strong> [File:<em>TeamName</em> Safety2016 Spreadsheet.xls]</p> |
<p>You may upload multiple versions of your spreadsheet, using the same Destination Filename. The wiki software will keep track of different versions, and list them in chronological order.</p> | <p>You may upload multiple versions of your spreadsheet, using the same Destination Filename. The wiki software will keep track of different versions, and list them in chronological order.</p> | ||
<p><strong><a href="" target="_blank" id="spreadsheet_view">Click here to VIEW your spreadsheet</a></strong></p> | <p><strong><a href="" target="_blank" id="spreadsheet_view">Click here to VIEW your spreadsheet</a></strong></p> | ||
Line 291: | Line 281: | ||
if(typeof owner_info !== "undefined") { | if(typeof owner_info !== "undefined") { | ||
//console.log("Setting spreadsheet links for team " + owner_info.team_name); | //console.log("Setting spreadsheet links for team " + owner_info.team_name); | ||
− | var url_start = "https:// | + | var url_start = "https://2016.igem.org/wiki/index.php?title=Special:Upload\u0026wpDestFile=" |
− | var url_end = " | + | var url_end = "_Safety2016_Spreadsheet.xls"; |
var whole_url = url_start + owner_info.team_name + url_end; | var whole_url = url_start + owner_info.team_name + url_end; | ||
jQuery("#spreadsheet_upload").attr("href", whole_url); | jQuery("#spreadsheet_upload").attr("href", whole_url); | ||
− | jQuery("#spreadsheet_view").attr("href", "https:// | + | jQuery("#spreadsheet_view").attr("href", "https://2016.igem.org/File:" + owner_info.team_name + "_Safety2016_Spreadsheet.xls"); |
} | } | ||
else { | else { |
Latest revision as of 19:41, 15 September 2016
Students complete Final Safety Form (Deadline: September 16) |
|
Instructor reads and approves Final Safety Form |
Instructor submits form (from his or her user account) |
Due September 16
This form is for you to tell us all about your project, the organisms/parts you are using, the potential risks of your project, and what you are doing to reduce those risks.
- We encourage STUDENTS, instead of instructors, to complete this form. However, you will need an Instructor or PI to sign and submit this form.
- While you type, this form will remember your answers. When you are finished, press the "Submit" button at the bottom to send your form to the iGEM Safety Committee.
- Submit this form by September 16.
- If you will not be able to complete this form before the deadline, please email us (safety AT igem DOT org) and tell us about your situation.
This form has been submitted.
You can unsubmit the form if you wish to make further edits.
-- Please choose a team
Orange stuff is only visible to wiki superusers (hide orange stuff)
Go to Admin Mode / Go to Team Example / Go to Username:
2. What is your chassis organism?
Check all species you are genetically modifying in your project.
Comments:
3. Do you plan to experiment with any other organisms, besides your chassis?
What organisms, and what experiments will you do? Please explain briefly. Please include the names of species / cell lines / strains.
- "Our bacteria is meant to live on plant leaves, so we will test them on tobacco (Nicotiana benthamiana) in a lab greenhouse."
- "We will handle P. aeruginosa in order to PCR the [example gene] from it."
- "Our bacteria need to interact with human cells for a medical application. We will test them in human cell culture using the HEK293 cell line."
- "We want to use a protein from ants, but its sequence is unknown. So we will capture ants (Camponotus spp.) to extract DNA and RNA to find the sequence of the protein we want."
4. How will your project work?
Describe the goal of your project: what is your engineered organism supposed to do? Please include specific technical details and names of important parts. (Even though your project might change, please describe the main project idea you are working on right now. See the example answers for help.)
Good example answers:
- "Our bacteria will live inside a human body. They will detect tumor cells that express biomarkers for liver cancer. They will use invasin to enter the tumor cells, and then secrete apoptin to kill the tumor cells."
- "Our algae will receive the exhaust from a factory, which is high in CO2. We will increase their expression of Photosystem II proteins to make them absorb more CO2, reducing the factory's emissions."
Bad example answers (not enough detail):
- "We are engineering E. coli to cure liver cancer."
- "Climate change is a very important problem. Our algae will reduce CO2 emissions and fight climate change."
5. What risks does your project pose at the laboratory stage? What actions are you taking to reduce those risks?
If you are working in a biology lab, you cannot answer "no risks". Even the simplest experiment, with the safest bacteria, poses some small risk. The actions you take to reduce that risk would include safety level 1 procedures, wearing gloves, sterilizing waste, etc.
6. How would your project be used in the real world?
Imagine that your project were fully developed into a real product that real people could use. How would people use it? Check all appropriate boxes.
(Note: iGEM teams should not release modified organisms into the natural environment.)
(Examples: library of standardized promoters, system for communication between cells)
(Examples: reporter strain for measuring the strength of promoters)
(Examples: cells that make a flavor chemical for food, cells that make biofuel)
(Examples: cells that clean your clothes, bread made with engineered yeast)
(Examples: cells that guard against pests, engineered rice plants, cells that promote growth of crop plants)
(Examples: a bio-sensing strip with cells that detect arsenic)
(Examples: cells that remove pollution from lakes, engineered forest trees that can resist drought)
(Examples: anti-cancer bacteria, bread made with engineered yeast, engineered rice plants)
(Examples: bacteria that live on Mars)
Comments:
7. What risks might your project pose, if it were fully developed into a real product that real people could use? What future work might you do to reduce those risks?
8. Any further comments about your project:
9. Comments about this form: Is it easy or difficult to use? Are the questions confusing?