(41 intermediate revisions by 3 users not shown) | |||
Line 3: | Line 3: | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
<noscript> | <noscript> | ||
Line 22: | Line 15: | ||
<div class="column full_size"> | <div class="column full_size"> | ||
<h1>iGEM 2019 Judging Applications</h1> | <h1>iGEM 2019 Judging Applications</h1> | ||
− | |||
− | < | + | <p> |
− | + | <span class="on_page"></span><b>On this page</b> | |
+ | you will find information on: | ||
+ | <a href="#jamboree"> Judging at the Giant Jamboree</a>, | ||
+ | <a href="#who"> Who Should Apply to be a Judge?</a>, | ||
+ | <a href="#why"> Why Should You be an iGEM Judge?</a>, | ||
+ | <a href="#process"> Application Process</a> | ||
+ | <a href="#benefits"> Judge Benefits</a>, and | ||
+ | the <a href="#application">Judge Application</a> | ||
+ | </p> | ||
+ | |||
+ | <br><br> | ||
+ | |||
+ | <div class="highlight post_item gray"> | ||
+ | <div class="details "> | ||
+ | <span class="icon announcement"></span> | ||
+ | <div class="title"> The iGEM 2019 Judging Application is Closed </div> | ||
+ | </div> | ||
+ | <p>Judge applications for the 2019 Giant Jamboree are now closed. Thank you to everyone who applied!</p> | ||
+ | </div> | ||
</div> | </div> | ||
− | |||
− | |||
− | |||
− | |||
− | < | + | <div class="clear extra_space" id="jamboree"></div> |
− | < | + | <div class="column full_size"> |
+ | <h3>Judging at the Giant Jamboree</h3> | ||
+ | <p>Judging in iGEM is a lot of fun, but it does require <b>a strong commitment</b>. iGEM teams work incredibly hard on their projects over the summer, so we need judges who are also committed to work hard to evaluate them and who are willing to take part in the whole process of iGEM judging. If you can spend time learning about the judging process during the summer, evaluating team wikis the week before the Jamboree, and attending the Jamboree from October 31-November 4, 2019, we would love to have you on board!</p> | ||
+ | <p>We need judges — both experienced and new — who really understand iGEM. We are aiming to recruit a judging panel that reflects our teams’ experience, so if you have previous iGEM experience we want you to apply!</p> | ||
+ | <p>As we approach the Giant Jamboree, we will provide educational resources to help judges learn how to evaluate teams (or provide a refresher, for those who have judged before), and we will help you get up to speed if you are selected.</p> | ||
− | |||
− | |||
− | <p>We're looking for:</p> | + | |
+ | <div class="clear extra_space"></div> | ||
+ | |||
+ | <img src="https://static.igem.org/mediawiki/2019/f/f3/Judging_application_1.jpg"> | ||
+ | <p class="image_caption">Judges at a team's poster during the 2018 Giant Jamboree</p> | ||
+ | </div> | ||
+ | |||
+ | <div class="clear extra_space"></div> | ||
+ | <div class="line_divider"></div> | ||
+ | <div class="clear extra_space" id="who"></div> | ||
+ | |||
+ | <div class="column third_size"> | ||
+ | |||
+ | <img src="https://static.igem.org/mediawiki/2019/2/25/Judging_application_2.jpg"> | ||
+ | |||
+ | |||
+ | </div> | ||
+ | |||
+ | <div class="column two_thirds_size"> | ||
+ | <h3>Who Should Apply to be a Judge? </h3> | ||
+ | <p> | ||
+ | We're looking for:</p> | ||
<ul> | <ul> | ||
+ | <li>iGEM alumni who want to stay involved, including professionals, graduate students, and post-docs</li> | ||
+ | <li>iGEM PIs, instructors, and advisors, both current and past</li> | ||
<li>People who have judged iGEM in the past</li> | <li>People who have judged iGEM in the past</li> | ||
− | |||
− | |||
− | |||
<li>Professionals in the synthetic biology, biotechnology, and engineering industries</li> | <li>Professionals in the synthetic biology, biotechnology, and engineering industries</li> | ||
− | <li> | + | <li>People who have experience in complimentary areas, such as the humanities, art and design, and software</li> |
</ul> | </ul> | ||
+ | |||
+ | <p>If you have colleagues who you think should apply, please feel free to direct them to this form.</p> | ||
<p>If you are a student on a 2019 iGEM team, you can't apply to be a judge this year. But you can apply when you graduate and become an iGEM alum!</p> | <p>If you are a student on a 2019 iGEM team, you can't apply to be a judge this year. But you can apply when you graduate and become an iGEM alum!</p> | ||
+ | </div> | ||
− | </div> | + | <div class="clear extra_space" id="why"></div> |
− | <div class="column | + | <div class="column third_size"> |
− | < | + | |
+ | <img src="https://static.igem.org/mediawiki/2019/9/91/Judging_application_3.jpg"> | ||
+ | |||
+ | |||
+ | </div> | ||
+ | |||
+ | <div class="column two_thirds_size"> | ||
+ | |||
+ | <h3>Why Should You be an iGEM Judge?</h3> | ||
<p>Judging at the annual iGEM Giant Jamboree is an incredibly fulfilling and worthwhile experience for all judges, whether you're returning as a veteran judge or are a new judge this year. Some of the benefits include: | <p>Judging at the annual iGEM Giant Jamboree is an incredibly fulfilling and worthwhile experience for all judges, whether you're returning as a veteran judge or are a new judge this year. Some of the benefits include: | ||
<ul> | <ul> | ||
− | <li> | + | <li><b>Contribute to the iGEM Community:</b> By volunteering to judge at the Giant Jamboree, you will contribute to what will be the most meaningful opportunity that these students experience in synthetic biology. Providing feedback to these dedicated students can be life changing for them as they continue through their academic career and beyond.</li> |
− | + | <li><b>Networking:</b> Much like the iGEM teams, you'll have the chance to connect with people from around the globe, to expand your synthetic biology community, and to form new collaborations beyond the Giant Jamboree. You will meet fellow judges, students, and other professionals from around the world and different walks of life. </li> | |
− | <li> | + | <li><b>Learn About New Technology:</b> You will learn about the latest cutting edge work being done in synthetic biology from student teams who are driven to excel and who test the boundaries of synthetic biology through their projects.</li> |
− | <li> | + | |
</ul> | </ul> | ||
</div> | </div> | ||
+ | <div class="clear extra_space"></div> | ||
+ | <div class="line_divider"></div> | ||
+ | <div class="clear extra_space" id="process"></div> | ||
+ | |||
+ | |||
+ | <div class="column full_size"> | ||
+ | <h3>Application Process</h3> | ||
+ | <p> | ||
+ | This year we are accepting applications on a rolling basis. We will be evaluating applications at the end of each month starting in May and will contact applicants approximately two weeks after the evaluation period. Status notifications (1. invitation to judge, 2. invitation to serve as a reserve judge, 3. invitation to re-apply, or 4. decline for 2019 with an invitation to apply next year) will be sent in the middle of each month, beginning in June, until our quota is full (expected by August). <b>We encourage you to apply early to increase your chances of being selected!</b> | ||
+ | <br><br> | ||
+ | You can apply to be a judge before knowing if you can fully commit to attending the Giant Jamboree. Applicants who are invited to join the judging panel will be asked to confirm their acceptance. We can also provide an official invitation letter if you require that to secure funding and/or permission from your institute to participate as a judge. | ||
+ | <br><br> | ||
+ | Once we have reached our quota of judges, we will close the application and add a notice to this page. | ||
+ | </p> | ||
<div class="column full_size"> | <div class="column full_size"> | ||
− | < | + | <div class="highlight post_item"> |
− | < | + | <div class="details"> |
+ | <span class="icon note"></span> | ||
+ | <div class="title">Giant Jamboree Attendance</div> | ||
+ | </div> | ||
+ | |||
+ | <p>If you are selected as a judge, you <b>MUST</b> attend the iGEM 2019 <a href="https://2019.igem.org/Giant_Jamboree">Giant Jamboree</a> in Boston (October 31-November 4) <b>in person.</b> We are unable to support remote participation for judges due to the nature of the interactions you will have with the teams throughout the event. | ||
<br><br> | <br><br> | ||
− | + | If you can only attend a portion of the Jamboree, this may make judging your assigned teams a challenge. We will work with you to try to accommodate your schedule constraints as best as possible, but we may rescind your invitation to judge in favor of another applicant who can attend the entire event. This will be evaluated on a case by case basis. | |
+ | </div> | ||
+ | </div> | ||
+ | |||
+ | |||
+ | <div class="clear extra_space"></div> | ||
+ | <div class="line_divider"></div> | ||
+ | <div class="clear extra_space" id="benefits"></div> | ||
+ | |||
+ | |||
+ | |||
+ | <h3>Judge Benefits</h3> | ||
+ | <p> | ||
+ | Instructor judges (current team PIs, instructors, and advisors) will receive a 50% discount on their Jamboree attendance fee. | ||
<br><br> | <br><br> | ||
− | + | Judges who are not affiliated with a team will receive free Jamboree attendance. | |
− | </p> | + | <br><br> |
+ | We are also excited to offer free childcare for all of our judges throughout the Giant Jamboree! | ||
+ | <br><br> | ||
+ | iGEM currently cannot provide travel funding for judges to attend.</p></p> | ||
+ | |||
+ | <div class="clear extra_space"></div> | ||
+ | |||
+ | <div class="highlight post_item gray"> | ||
+ | <div class="details "> | ||
+ | <span class="icon why"></span> | ||
+ | <div class="title"> Questions? </div> | ||
</div> | </div> | ||
+ | <p> Please email <i> traci [AT] igem [DOT] org</i> and/or <i> vinoo [AT] igem [DOT] org</i> if you have questions!</p> | ||
+ | </div> | ||
+ | </div> | ||
+ | |||
+ | |||
<div class="clear extra_space"></div> | <div class="clear extra_space"></div> | ||
+ | <div class="column full_size" id="application"> | ||
+ | <br><br> | ||
+ | <!------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ||
+ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ||
− | <p><b>Judge | + | THIS IS WHERE THE FORM BEGINS |
+ | |||
+ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ||
+ | |||
+ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------> | ||
+ | |||
+ | |||
+ | <script type="text/javascript"> | ||
+ | var form_info = {}; | ||
+ | form_info.name="2019_judge_application"; | ||
+ | form_info.display_title="2019 Judging Application Form"; | ||
+ | form_info.default_mode = "edit"; | ||
+ | form_info.owner_type = "user"; | ||
+ | form_info.permissions = {view: ["author", "super_users"], | ||
+ | edit: ["author", "super_users"], | ||
+ | submit: ["author", "super_users"], | ||
+ | admin: ["super_users"]}; | ||
+ | form_info.validate_unspecified_fields = "required"; | ||
+ | form_info.ajax_URL = "https://2019.igem.org/cgi/forms/form.cgi"; | ||
+ | </script> | ||
+ | |||
+ | <link rel="stylesheet" type="text/css" href="https://igem.org/wiki/index.php?title=HQ:2019_Forms.css&action=raw&ctype=text/css" /> | ||
+ | <script src="https://igem.org/wiki/index.php?title=HQ:Judging_Form.js&action=raw&ctype=text/javascript"></script> | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | <div class="column full_size" style="text-align:center; margin:auto;"><h1> Judge Application Form </h1> </div> | ||
+ | <div class="clear"></div> | ||
+ | <div class="line_divider"></div> | ||
+ | <div class="clear extra_space"></div> | ||
+ | |||
+ | |||
+ | <div class="column full_size"> | ||
+ | |||
+ | <div id='aj_form_errors'> </div> | ||
+ | |||
+ | </div> | ||
+ | |||
+ | |||
+ | <div id="submitted_warning"> | ||
+ | <p>This form has been submitted.</p> | ||
+ | <p>You can <a href="#" id="popwin_unsubmit">unsubmit the form</a> if you wish to make further edits.</p> | ||
+ | <p><a href="#" id="popwin_dismiss">Click here to dismiss this message</a></p> | ||
+ | </div> | ||
+ | </div> | ||
+ | |||
+ | |||
+ | |||
+ | <div class="column full_size"> | ||
+ | |||
+ | <div id="formtitlemodewrapper"> | ||
+ | <h2 id="toptitle"> | ||
+ | <span id="form_title_display"></span> <span id="owner_name_display"></span> | ||
+ | </h2> | ||
+ | |||
+ | <h4 id="modes"></h4> | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | <div class="admins_only" id="admin_link"> | ||
+ | <p>Admin view (orange) is only visible to super users. (<a href="#" id="hide_admin">Hide admin view</a>)</p> | ||
+ | <p><b><a class="change_mode" data-mode="admin">Go to Admin Mode</a></b> / <a class="change_team" data-team="1874">Go to Team Example</a> / Go to Username: <input type="text" id="author_select" autocomplete="off"></p> | ||
+ | </div> | ||
+ | </div> | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | <!--Enclose the actual questions in a div id="formbody"--> | ||
+ | <div id="formbody"> | ||
+ | |||
+ | <!------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ||
+ | |||
+ | GENERAL INFORMATION | ||
+ | |||
+ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------> | ||
+ | |||
+ | |||
+ | <fieldset> | ||
+ | <h2> 1. General Information </h2> | ||
+ | |||
+ | |||
+ | <p class="question"> Full name: <span id="full_name_display">-</span> </p> | ||
+ | |||
+ | |||
+ | |||
+ | <p class="question"> Username: <span id="user_name_display">-</span></p> | ||
+ | |||
+ | |||
+ | |||
+ | <p class="question">1. Email | ||
+ | <input type="text" size="40" name="Email" id="email" class="validate-on-change" data-form-field="email" data-validate-as="email" placeholder="Email"> | ||
+ | </p> | ||
+ | |||
+ | <p class="question">2. Age | ||
+ | <input type="text" size="40" name="Age" id="age" class="validate-on-change" data-form-field="age" data-validate-as="age" placeholder="Age"> | ||
+ | </p> | ||
+ | |||
+ | <div class="highlight post_item"> | ||
+ | <div class="details"> | ||
+ | <span class="icon note"></span> | ||
+ | <div class="title">Note</div> | ||
+ | </div> | ||
+ | <p> | ||
+ | To be eligible to become an iGEM judge, you must be at least 23 years old as of March 31, 2019. We also expect judges to have completed their undergraduate degree before the Jamboree takes place. | ||
+ | </p> | ||
+ | </div> | ||
+ | |||
+ | |||
+ | <p class="question">3. Gender</p> | ||
+ | <ul> | ||
+ | <li><label><input type="radio" data-form-field="gender" name="Gender" id="female" value="female"> Female</label></li> | ||
+ | <li><label><input type="radio" data-form-field="gender" name="Gender" id="male" value="male"> Male</label></li> | ||
+ | <li><label><input type="radio" data-form-field="gender" name="Gender" id="freeform" value="freeform"></label> <input type="text" size="40" id="freeform-gender" name="Gender (freeform text box)" data-form-field="freeform-gender" data-validation="#freeform" placeholder="Please describe"></li> | ||
+ | </ul> | ||
+ | |||
+ | <p class="question">4. Institution | ||
+ | <input type="text" size="40" name="Institution" id="institution" data-form-field="institution" placeholder="Institution"> | ||
+ | </p> | ||
+ | |||
+ | |||
+ | |||
+ | <p class="question">5. Institution type</p> | ||
+ | <ul> | ||
+ | <li><label><input type="radio" data-form-field="institution-type" name="Institution type" id="academia" value="academia"> Academia</label></li> | ||
+ | <li><label><input type="radio" data-form-field="institution-type" name="Institution type" id="industry" value="industry"> Industry</label></li> | ||
+ | <li><label><input type="radio" data-form-field="institution-type" name="Institution type" id="government" value="government"> Government</label></li> | ||
+ | <li><label><input type="radio" data-form-field="institution-type" name="Institution type" id="ngo" value="ngo"> Non-governmental organization (NGO)</label></li> | ||
+ | <li><label><input type="radio" data-form-field="institution-type" name="Institution type" id="nonprofit" value="nonprofit"> Non-profit organization</label></li> | ||
+ | <li><label><input type="radio" data-form-field="institution-type" name="Institution type" id="other-institution" value="other-institution"> Other:</label> <input type="text" size="40" name="Other institution type" data-validation="#other-institution" id="other-institution-describe" data-form-field="other-institution-describe" placeholder="Please describe"></li> | ||
+ | </ul> | ||
+ | |||
+ | <p class="question">6. Position</p> | ||
+ | <ul> | ||
+ | <li><label><input type="radio" data-form-field="position" name="Position" id="dean" value="dean"> Dean, or equivalent</label></li> | ||
+ | <li><label><input type="radio" data-form-field="position" name="Position" id="professor" value="professor"> Professor, or equivalent</label></li> | ||
+ | <li><label><input type="radio" data-form-field="position" name="Position" id="pi" value="pi"> PI (primary investigator), or equivalent</label></li> | ||
+ | <li><label><input type="radio" data-form-field="position" name="Position" id="postdoc" value="postdoc"> Post-doctoral researcher, or equivalent</label></li> | ||
+ | <li><label><input type="radio" data-form-field="position" name="Position" id="grad" value="grad"> PhD student, or equivalent</label></li> | ||
+ | <li><label><input type="radio" data-form-field="position" name="Position" id="masters" value="masters"> Masters student, or equivalent</label></li> | ||
+ | <li><label><input type="radio" data-form-field="position" name="Position" id="other-position" value="other-position"> Other:</label> <input type="text" size="40" name="Other position" data-validation="#other-position" data-form-field="other-position-describe" placeholder="Please describe"></li> | ||
+ | </ul> | ||
+ | |||
+ | <p class="question">7. Region <span class="additional_question_text"> Where you currently live/work </span> : </p> | ||
+ | <ul> | ||
+ | <li><label><input type="radio" name="iGEM Region" data-form-field="region" id="Africa" value="Africa"> Africa</label></li> | ||
+ | <li><label><input type="radio" name="iGEM Region" data-form-field="region" id="Asia" value="Asia"> Asia</label> </li> | ||
+ | <li><label><input type="radio" name="iGEM Region" data-form-field="region" id="Europe" value="Europe"> Europe</label> </li> | ||
+ | <li><label><input type="radio" name="iGEM Region" data-form-field="region" id="Latin_America" value="Latin_America"> Latin America</label> </li> | ||
+ | <li><label><input type="radio" name="iGEM Region" data-form-field="region" id="North_America" value="North_America"> North America</label> </li> | ||
+ | </ul> | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | <p class="question">8. Number of years of iGEM experience as a:</p> | ||
+ | |||
+ | |||
+ | <p class="dropdown_question"> <span class="align_dropdowns">Judge: </span> | ||
+ | <select name="Years Experience as a Judge" data-form-field="years_judge"> | ||
+ | <option value="0">0</option> | ||
+ | <option value="1">1</option> | ||
+ | <option value="2">2</option> | ||
+ | <option value="3">3</option> | ||
+ | <option value="4">4</option> | ||
+ | <option value="5">5</option> | ||
+ | <option value="6+">6+</option> | ||
+ | </select> | ||
+ | </p> | ||
+ | |||
+ | <br> | ||
+ | |||
+ | <p class="dropdown_question"> <span class="align_dropdowns">PI/Instructor: </span> | ||
+ | <select name="Years Experience as an PI/Instructor" data-form-field="years_instructor" > | ||
+ | <option value="0">0</option> | ||
+ | <option value="1">1</option> | ||
+ | <option value="2">2</option> | ||
+ | <option value="3">3</option> | ||
+ | <option value="4">4</option> | ||
+ | <option value="5">5</option> | ||
+ | <option value="6+">6+</option> | ||
+ | </select> | ||
+ | </p> | ||
+ | |||
+ | <br> | ||
+ | |||
+ | <p class="dropdown_question"> <span class="align_dropdowns">Advisor: </span> | ||
+ | <select name="Years Experience as an Advisor" data-form-field="years_advisor"> | ||
+ | <option value="0">0</option> | ||
+ | <option value="1">1</option> | ||
+ | <option value="2">2</option> | ||
+ | <option value="3">3</option> | ||
+ | <option value="4">4</option> | ||
+ | <option value="5">5</option> | ||
+ | <option value="6+">6+</option> | ||
+ | </select> | ||
+ | </p> | ||
+ | |||
+ | <br> | ||
+ | <p class="dropdown_question"> <span class="align_dropdowns">Student: </span> | ||
+ | <select name="Years Experience as a Student" data-form-field="years_student" > | ||
+ | <option value="0">0</option> | ||
+ | <option value="1">1</option> | ||
+ | <option value="2">2</option> | ||
+ | <option value="3">3</option> | ||
+ | <option value="4">4</option> | ||
+ | <option value="5">5</option> | ||
+ | <option value="6+">6+</option> | ||
+ | </select> | ||
+ | </p> | ||
+ | |||
+ | <br> | ||
+ | |||
+ | <p class="dropdown_question"> <span class="align_dropdowns">Volunteer: </span> | ||
+ | <select name="Years Experience as a Volunteer" data-form-field="years_volunteer" > | ||
+ | <option value="0">0</option> | ||
+ | <option value="1">1</option> | ||
+ | <option value="2">2</option> | ||
+ | <option value="3">3</option> | ||
+ | <option value="4">4</option> | ||
+ | <option value="5">5</option> | ||
+ | <option value="6+">6+</option> | ||
+ | </select> | ||
+ | </p> | ||
+ | </fieldset> | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | <!------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ||
+ | |||
+ | JAMBOREE INFORMATION | ||
+ | |||
+ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------> | ||
+ | |||
+ | |||
+ | |||
+ | <fieldset> | ||
+ | <h2>2. Jamboree Information </h2> | ||
+ | <p><i>Please complete this section as well as you can. You will be asked to check or update this information prior to the Jamboree.</i></p> | ||
+ | |||
+ | <p class="question">1. Sweatshirt Size:</p> | ||
+ | <ul> | ||
+ | <li><label><input type="radio" name="Sweatshirt Size" data-form-field="size" id="XS" value="XS"> XS</label> </li> | ||
+ | <li><label><input type="radio" name="Sweatshirt Size" data-form-field="size" id="S" value="S"> S</label> </li> | ||
+ | <li><label><input type="radio" name="Sweatshirt Size" data-form-field="size" id="M" value="M"> M</label> </li> | ||
+ | <li><label><input type="radio" name="Sweatshirt Size" data-form-field="size" id="L" value="L"> L</label> </li> | ||
+ | <li><label><input type="radio" name="Sweatshirt Size" data-form-field="size" id="XL" value="XL"> XL</label> </li> | ||
+ | <li><label><input type="radio" name="Sweatshirt Size" data-form-field="size" id="XXL" value="XXL"> XXL</label> </li> | ||
+ | </ul> | ||
+ | |||
+ | |||
+ | <p class="question">2. Are you available to attend the <b>entire</b> <a href="https | ||
+ | ://2019.igem.org/Giant_Jamboree">Giant Jamboree</a> from October 31 - November 4, 2019, in Boston?</p> | ||
+ | <ul> | ||
+ | <li><label><input type="radio" name="Jamboree Attendance" data-form-field="jamboree" value="yes">Yes</label></li> | ||
+ | <li><label><input type="radio" name="Jamboree Attendance" data-form-field="jamboree" value="no"> No</label> </li> | ||
+ | </ul> | ||
+ | |||
+ | <p class="question">2.1 If not, please indicate which days/times you are available to attend.</p> | ||
+ | |||
+ | <div class="column half_size"> | ||
+ | <table> | ||
+ | <tr> <th> Day </th> <th>Morning </th> <th> Evening </th> </tr> | ||
+ | |||
+ | <tr> | ||
+ | <th>Thursday <br> October 31</th> | ||
+ | <td></td> | ||
+ | <td><label><input type="radio" name="Availability Thurs Oct 31, Evening" data-form-field="available_thu_eve" value="yes"> Yes</label><br /><br> | ||
+ | <label><input type="radio" name="Availability Thurs Oct 31, Evening" data-form-field="available_thu_eve" value="no"> No</label> | ||
+ | </td> | ||
+ | </tr> | ||
+ | |||
+ | |||
+ | <tr> | ||
+ | <th>Friday <br> November 1</th> | ||
+ | <td><label><input type="radio" name="Availability Fri Nov 1, Morning" data-form-field="available_fri_morn" value="yes"> Yes</label><br /><br> | ||
+ | <label><input type="radio" name="Availability Fri Nov 1, Morning" data-form-field="available_fri_morn" value="no"> No</label> | ||
+ | </td> | ||
+ | <td><label><input type="radio" name="Availability Fri Nov 1, Evening" data-form-field="available_fri_eve" value="yes"> Yes</label><br /><br> | ||
+ | <label><input type="radio" name="Availability Fri Nov 1, Evening" data-form-field="available_fri_eve" value="no"> No</label> | ||
+ | </td> | ||
+ | </tr> | ||
+ | |||
+ | <tr> | ||
+ | <th>Saturday <br> November 2</th> | ||
+ | <td><label><input type="radio" name="Availability Sat Nov 2, Morning" data-form-field="available_sat_morn" value="yes"> Yes</label><br /><br> | ||
+ | <label><input type="radio" name="Availability Sat Nov 2, Morning" data-form-field="available_sat_morn" value="no"> No</label> | ||
+ | </td> | ||
+ | <td><label><input type="radio" name="Availability Sat Nov 2, Evening" data-form-field="available_sat_eve" value="yes"> Yes</label><br /><br> | ||
+ | <label><input type="radio" name="Availability Sat Nov 2, Evening" data-form-field="available_sat_eve" value="no"> No</label> | ||
+ | </td> | ||
+ | |||
+ | </tr> | ||
+ | |||
+ | |||
+ | |||
+ | <tr> | ||
+ | |||
+ | <th>Sunday <br> November 3</th> | ||
+ | |||
+ | <td><label><input type="radio" name="Availability Sun Nov 3, Morning" data-form-field="available_sun_morn" value="yes"> Yes</label><br /><br> | ||
+ | <label><input type="radio" name="Availability Sun Nov 3, Morning" data-form-field="available_sun_morn" value="no"> No</label> | ||
+ | </td> | ||
+ | <td><label><input type="radio" name="Availability Sun Nov 3, Evening" data-form-field="available_sun_eve" value="yes"> Yes</label><br /><br> | ||
+ | <label><input type="radio" name="Availability Sun Nov 3, Evening" data-form-field="available_sun_eve" value="no"> No</label> | ||
+ | </td> | ||
+ | |||
+ | </tr> | ||
+ | |||
+ | <tr> | ||
+ | <th>Monday <br> November 4</th> | ||
+ | <td><label><input type="radio" name="Availability Mon Nov 4, Morning" data-form-field="available_mon_morn" value="yes"> Yes</label><br /><br> | ||
+ | <label><input type="radio" name="Availability Mon Nov 4, Morning" data-form-field="available_mon_morn" value="no"> No</label> | ||
+ | </td> | ||
+ | <td><label><input type="radio" name="Availability Mon Nov 4, Evening" data-form-field="available_mon_eve" value="yes"> Yes</label><br /><br> | ||
+ | <label><input type="radio" name="Availability Mon Nov 4, Evening" data-form-field="available_mon_eve" value="no"> No</label> | ||
+ | </td> | ||
+ | </tr> | ||
+ | |||
+ | </table> | ||
+ | |||
+ | |||
+ | </div> | ||
+ | |||
+ | |||
+ | |||
+ | </fieldset> | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | <!------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ||
+ | |||
+ | CONFLICTS OF INTEREST | ||
+ | |||
+ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------> | ||
+ | |||
+ | |||
+ | <fieldset> | ||
+ | <h2> 3. Conflicts of Interest </h2> | ||
+ | |||
+ | <p>There are many possible reasons why you might be unable to judge some teams impartially. For example if you are a PI or instructor for the team, if the team comes from a school that you attended, or a school where you work or if you mentored or advised the team informally. | ||
<br><br> | <br><br> | ||
− | + | These situations could lead to a conflict of interest and iGEM takes conflicts of interests very seriously. Judges are not permitted to evaluate teams for which they have a conflict of interest. If you are a PI or instructor, your first responsibility is to your team, and we will schedule your judging assignment so that you are able to attend your team's presentation.</p> | |
+ | |||
+ | |||
+ | <p>To select multiple teams, use <i><b> Ctrl-click or Cmd-click</i></b>. Don't recognize a team name? Look it up in the <a target="_blank" href="https://igem.org/Team_List">Team List</a>.</p> | ||
+ | |||
+ | |||
+ | <div class="column half_size"> | ||
+ | <p class="question">1. Team Affiliations:</p> | ||
+ | <p> Please select any teams you are officially affiliated with (i.e. you are listed on the team roster as a PI, Instructor, or Advisor).</p> | ||
<br><br> | <br><br> | ||
− | + | <select multiple class="teamselector-multiple" size="20" name="Team affiliations" id="team_affiliations" data-form-field="team_affiliations"> | |
+ | <option class='none_selected'>I have no 2019 team affiliations</option> | ||
+ | </select> | ||
+ | |||
</div> | </div> | ||
+ | |||
+ | |||
+ | |||
+ | <div class="column half_size"> | ||
+ | <p class="question">2. Conflicts of Interest:</p> | ||
+ | <p> Please select any teams for which you have a conflict of interest for another reason. (For example, a team that you mentored informally, or a team from the university where you were an undergrad student.)</p><br> | ||
+ | |||
+ | <select multiple class="teamselector-multiple" size="20" name="Team conflicts of interest" id="team_conflicts" data-form-field="team_conflicts"> | ||
+ | <option class='none_selected'>I have no 2019 team conflicts of interest</option> | ||
+ | </select> | ||
+ | |||
</div> | </div> | ||
+ | |||
+ | |||
+ | <div class="clear extra_space"></div> | ||
+ | |||
+ | <p class="question">3. If you have any other conflicts of interest that are not indicated above, please describe them:</p> | ||
+ | <textarea rows="3" data-validation="optional" name="Other conflicts of interest" id="other_conflicts" data-form-field="other_conflicts" maxlength="500"></textarea> | ||
+ | </fieldset> | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | <!------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ||
+ | |||
+ | MOTIVATION | ||
+ | |||
+ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------> | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | <fieldset> | ||
+ | |||
+ | <h2>4. Motivation</h2> | ||
+ | <p>Please answer these questions in detail.</p> | ||
+ | <p>Did you apply to judge last year? <a id="last_years_application_link" target="_blank">View your answers from last year.</a> Please note we have changed some of the questions for 2019.</p> | ||
+ | |||
+ | |||
+ | |||
+ | <p class="question">1. Why do you want to be a judge in iGEM?</p> | ||
+ | <textarea rows="5" name="Why do you want to be a judge" id="why_want_to_judge" data-form-field="why_want_to_judge" maxlength="2000"></textarea> | ||
+ | |||
+ | <p class="question">2. What professional experience do you have that you believe is relevant to iGEM (e.g., synthetic biology, hardware, software, human practices)?</p> | ||
+ | <textarea rows="5" name="What professional experience do you have" id="professional_experience" data-form-field="professional_experience" maxlength="2000"></textarea> | ||
+ | |||
+ | <p class="question">3. How important is scientific and/or engineering success to overall team success?</p> | ||
+ | <textarea rows="5" name="How important is scientific and/or engineering" id="scientific_engineering" data-form-field="success" maxlength="2000"></textarea> | ||
+ | |||
+ | <p class="question">4. What are the synthetic biology principles that iGEM participants should learn during their project?</p> | ||
+ | <textarea rows="5" name="What are the synthetic biology principles" id="synbio_principles" data-form-field="principles"></textarea maxlength="2000"></fieldset> | ||
+ | |||
+ | |||
+ | |||
+ | <!------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ||
+ | |||
+ | TRACK PREFERENCES | ||
+ | |||
+ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------> | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | <fieldset> | ||
+ | <h2>5. Track Preferences </h2> | ||
+ | |||
+ | <p>iGEM teams compete in several "tracks", based on the topics of their projects. Please see <a href="https://2019.igem.org/Competition/Tracks" target="_blank">the Track page</a> for more information on each track.</p> | ||
+ | |||
+ | <p>When we assign judges to teams, we will try to assign you your first preferences wherever possible. However, we can't anticipate how many teams will be in each track, so it may not always be possible to assign you your first choice. Therefore, you can indicate how you feel about each track. The more first choices you select, the more likely it is that you will be assigned teams in those tracks. If you are <b>unable</b> to evaluate teams in some track areas (software, for example), please put "Avoid" for those tracks.</p> | ||
+ | |||
+ | <p class="question">Please indicate how highly you prefer each track. You may select multiple first, second, and third preferences.</p> | ||
+ | |||
+ | <table id="track_prefs_table"> | ||
+ | <tr> | ||
+ | <th>Track</th> | ||
+ | <th>First</th> | ||
+ | <th>Second</th> | ||
+ | <th>Third</th> | ||
+ | <th>Neutral</th> | ||
+ | <th>Avoid</th> | ||
+ | </tr> | ||
+ | |||
+ | <tr> | ||
+ | <th>Diagnostics</th> | ||
+ | <td><input type="radio" name="Track Preference: Diagnostics" data-form-field="pref_diagnostics" value="first"></td> | ||
+ | <td><input type="radio" name="Track Preference: Diagnostics" data-form-field="pref_diagnostics" value="second"></td> | ||
+ | <td><input type="radio" name="Track Preference: Diagnostics" data-form-field="pref_diagnostics" value="third"></td> | ||
+ | <td><input type="radio" name="Track Preference: Diagnostics" data-form-field="pref_diagnostics" value="neutral"></td> | ||
+ | <td><input type="radio" name="Track Preference: Diagnostics" data-form-field="pref_diagnostics" value="avoid"></td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <th>Energy</th> | ||
+ | <td><input type="radio" name="Track Preference: Energy" data-form-field="pref_energy" value="first"></td> | ||
+ | <td><input type="radio" name="Track Preference: Energy" data-form-field="pref_energy" value="second"></td> | ||
+ | <td><input type="radio" name="Track Preference: Energy" data-form-field="pref_energy" value="third"></td> | ||
+ | <td><input type="radio" name="Track Preference: Energy" data-form-field="pref_energy" value="neutral"></td> | ||
+ | <td><input type="radio" name="Track Preference: Energy" data-form-field="pref_energy" value="avoid"></td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <th>Environment</th> | ||
+ | <td><input type="radio" name="Track Preference: Environment" data-form-field="pref_environment" value="first"></td> | ||
+ | <td><input type="radio" name="Track Preference: Environment" data-form-field="pref_environment" value="second"></td> | ||
+ | <td><input type="radio" name="Track Preference: Environment" data-form-field="pref_environment" value="third"></td> | ||
+ | <td><input type="radio" name="Track Preference: Environment" data-form-field="pref_environment" value="neutral"></td> | ||
+ | <td><input type="radio" name="Track Preference: Environment" data-form-field="pref_environment" value="avoid"></td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <th>Food and Nutrition</th> | ||
+ | <td><input type="radio" name="Track Preference: Food and Nutrition" data-form-field="pref_food" value="first"></td> | ||
+ | <td><input type="radio" name="Track Preference: Food and Nutrition" data-form-field="pref_food" value="second"></td> | ||
+ | <td><input type="radio" name="Track Preference: Food and Nutrition" data-form-field="pref_food" value="third"></td> | ||
+ | <td><input type="radio" name="Track Preference: Food and Nutrition" data-form-field="pref_food" value="neutral"></td> | ||
+ | <td><input type="radio" name="Track Preference: Food and Nutrition" data-form-field="pref_food" value="avoid"></td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <th>Foundational Advance</th> | ||
+ | <td><input type="radio" name="Track Preference: Foundational Advance" data-form-field="pref_foundational" value="first"></td> | ||
+ | <td><input type="radio" name="Track Preference: Foundational Advance" data-form-field="pref_foundational" value="second"></td> | ||
+ | <td><input type="radio" name="Track Preference: Foundational Advance" data-form-field="pref_foundational" value="third"></td> | ||
+ | <td><input type="radio" name="Track Preference: Foundational Advance" data-form-field="pref_foundational" value="neutral"></td> | ||
+ | <td><input type="radio" name="Track Preference: Foundational Advance" data-form-field="pref_foundational" value="avoid"></td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <th>High School</th> | ||
+ | <td><input type="radio" name="Track Preference: High School" data-form-field="pref_highschool" value="first"></td> | ||
+ | <td><input type="radio" name="Track Preference: High School" data-form-field="pref_highschool" value="second"></td> | ||
+ | <td><input type="radio" name="Track Preference: High School" data-form-field="pref_highschool" value="third"></td> | ||
+ | <td><input type="radio" name="Track Preference: High School" data-form-field="pref_highschool" value="neutral"></td> | ||
+ | <td><input type="radio" name="Track Preference: High School" data-form-field="pref_highschool" value="avoid"></td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <th>Information Processing</th> | ||
+ | <td><input type="radio" name="Track Preference: Information Processing" data-form-field="pref_info" value="first"></td> | ||
+ | <td><input type="radio" name="Track Preference: Information Processing" data-form-field="pref_info" value="second"></td> | ||
+ | <td><input type="radio" name="Track Preference: Information Processing" data-form-field="pref_info" value="third"></td> | ||
+ | <td><input type="radio" name="Track Preference: Information Processing" data-form-field="pref_info" value="neutral"></td> | ||
+ | <td><input type="radio" name="Track Preference: Information Processing" data-form-field="pref_info" value="avoid"></td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <th>Manufacturing</th> | ||
+ | <td><input type="radio" name="Track Preference: Manufacturing" data-form-field="pref_manufacturing" value="first"></td> | ||
+ | <td><input type="radio" name="Track Preference: Manufacturing" data-form-field="pref_manufacturing" value="second"></td> | ||
+ | <td><input type="radio" name="Track Preference: Manufacturing" data-form-field="pref_manufacturing" value="third"></td> | ||
+ | <td><input type="radio" name="Track Preference: Manufacturing" data-form-field="pref_manufacturing" value="neutral"></td> | ||
+ | <td><input type="radio" name="Track Preference: Manufacturing" data-form-field="pref_manufacturing" value="avoid"></td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <th>New Application</th> | ||
+ | <td><input type="radio" name="Track Preference: New Application" data-form-field="pref_newapplication" value="first"></td> | ||
+ | <td><input type="radio" name="Track Preference: New Application" data-form-field="pref_newapplication" value="second"></td> | ||
+ | <td><input type="radio" name="Track Preference: New Application" data-form-field="pref_newapplication" value="third"></td> | ||
+ | <td><input type="radio" name="Track Preference: New Application" data-form-field="pref_newapplication" value="neutral"></td> | ||
+ | <td><input type="radio" name="Track Preference: New Application" data-form-field="pref_newapplication" value="avoid"></td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <th>Open</th> | ||
+ | <td><input type="radio" name="Track Preference: Open" data-form-field="pref_open" value="first"></td> | ||
+ | <td><input type="radio" name="Track Preference: Open" data-form-field="pref_open" value="second"></td> | ||
+ | <td><input type="radio" name="Track Preference: Open" data-form-field="pref_open" value="third"></td> | ||
+ | <td><input type="radio" name="Track Preference: Open" data-form-field="pref_open" value="neutral"></td> | ||
+ | <td><input type="radio" name="Track Preference: Open" data-form-field="pref_open" value="avoid"></td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <th>Software</th> | ||
+ | <td><input type="radio" name="Track Preference: Software" data-form-field="pref_software" value="first"></td> | ||
+ | <td><input type="radio" name="Track Preference: Software" data-form-field="pref_software" value="second"></td> | ||
+ | <td><input type="radio" name="Track Preference: Software" data-form-field="pref_software" value="third"></td> | ||
+ | <td><input type="radio" name="Track Preference: Software" data-form-field="pref_software" value="neutral"></td> | ||
+ | <td><input type="radio" name="Track Preference: Software" data-form-field="pref_software" value="avoid"></td> | ||
+ | </tr> | ||
+ | <tr> | ||
+ | <th>Therapeutics</th> | ||
+ | <td><input type="radio" name="Track Preference: Therapeutics" data-form-field="pref_therapeutics" value="first"></td> | ||
+ | <td><input type="radio" name="Track Preference: Therapeutics" data-form-field="pref_therapeutics" value="second"></td> | ||
+ | <td><input type="radio" name="Track Preference: Therapeutics" data-form-field="pref_therapeutics" value="third"></td> | ||
+ | <td><input type="radio" name="Track Preference: Therapeutics" data-form-field="pref_therapeutics" value="neutral"></td> | ||
+ | <td><input type="radio" name="Track Preference: Therapeutics" data-form-field="pref_therapeutics" value="avoid"></td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | </fieldset> | ||
+ | </div> | ||
+ | |||
+ | |||
+ | <!--Here is where formbody ends.--> | ||
+ | |||
+ | |||
<div class="clear extra_space"></div> | <div class="clear extra_space"></div> | ||
<div class="column full_size"> | <div class="column full_size"> | ||
− | --> | + | <div class="highlight gray"> |
+ | <h3 style="margin:auto; text-align:center"> Thank you! </h3> | ||
+ | |||
+ | <p style="margin:auto; text-align:center">Thank you for filling out this form. We look forward to picking a strong judging team for 2019!</p> | ||
+ | |||
+ | |||
+ | |||
+ | <p class="question" style="text-align: center;">Finished? <input type="submit" data-form-field="submit" value="SUBMIT FORM"></p> | ||
+ | |||
+ | <p class="question" style="text-align: center;">Need to make changes? <input type="submit" data-form-field="return_form" value="UNSUBMIT FORM"></p> | ||
+ | |||
+ | |||
+ | |||
+ | </div> | ||
+ | </div> | ||
Line 106: | Line 759: | ||
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ||
− | THIS IS WHERE THE FORM | + | THIS IS WHERE THE FORM ENDS |
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ||
Line 113: | Line 766: | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | <script type="text/javascript"> | ||
+ | |||
+ | function custom_get_owner_info_response(data, textStatus, jqxhr) { | ||
+ | //This function will be called upon successful completion of get_user_info. | ||
+ | //You can do fun custom stuff here. | ||
+ | $("#full_name_display").text(data.full_name); | ||
+ | $("#user_name_display").text(data.user_name); | ||
+ | $("#last_years_application_link").attr("href", "https://2018.igem.org/Judging/Apply?author=" + data.user_name + "#formbody"); | ||
+ | } | ||
+ | |||
+ | //This is called only upon success of OIC. So if it happens from a submit button, | ||
+ | //we can assume validation has already been passed. | ||
+ | function custom_one_input_changed_response(input_element) { | ||
+ | if (input_element.attr("data-form-field") == "submit") { | ||
+ | alert("Thank you for applying to be a judge! iGEM HQ will review your application and contact you.\nYou may return and edit your answers if needed."); | ||
+ | } | ||
+ | } | ||
+ | |||
+ | //document.ready -- get team list to fill the conflict-of-interest selectors, | ||
+ | //and misc setup stuff | ||
+ | $(document).ready(function(event) { | ||
+ | $("#modes").addClass('admins_only'); | ||
+ | |||
+ | $("#team_select_select").hide(); | ||
+ | |||
+ | $("[data-form-field=jamboree]").change(function() { | ||
+ | if ($(this).val() == "yes") { | ||
+ | $("[data-form-field^=available_][value=yes]").prop("checked", true).trigger("change"); | ||
+ | } | ||
+ | }); | ||
+ | |||
+ | $("#track_prefs_table").on("click", "td", function() { | ||
+ | $(this).find("[type=radio]").prop("checked", true).trigger("change"); | ||
+ | }); | ||
+ | |||
+ | jQuery.ajax({ | ||
+ | url: "https://igem.org/aj/team_list.cgi", | ||
+ | type: "GET", | ||
+ | timeout: 30000, | ||
+ | dataType: "json", | ||
+ | data: {command: "get_team_list", year: "2019"}, //**Make this auto-update itself | ||
+ | error: function(jqxhr, textStatus, errorThrown) { | ||
+ | general_ajax_error( jqxhr, textStatus, errorThrown, | ||
+ | "Failed to get list of teams"); | ||
+ | aj_log("Failed to get list of teams"); | ||
+ | }, | ||
+ | success: function(data, textStatus, jqxhr) { | ||
+ | //Each element of data is an object like | ||
+ | //{ region: "Europe", name: "Aachen", id: "1585", some: "other properties" } | ||
+ | var optgroups = { "Africa": "<optgroup label='Africa'>", | ||
+ | "Asia": "<optgroup label='Asia'>", | ||
+ | "Europe": "<optgroup label='Europe'>", | ||
+ | "Latin America": "<optgroup label='Latin America'>", | ||
+ | "North America": "<optgroup label='North America'>" | ||
+ | }; | ||
+ | data.forEach(function(team) { | ||
+ | optgroups[team.region] += "<option value='" + team.id + "'>" + team.name + "</option>"; | ||
+ | }); | ||
+ | //I'm not using a for..in loop for this because order is important | ||
+ | $(".teamselector-multiple").append(optgroups["Africa"] + "</optgroup>"); | ||
+ | $(".teamselector-multiple").append(optgroups["Asia"] + "</optgroup>"); | ||
+ | $(".teamselector-multiple").append(optgroups["Europe"] + "</optgroup>"); | ||
+ | $(".teamselector-multiple").append(optgroups["Latin America"] + "</optgroup>"); | ||
+ | $(".teamselector-multiple").append(optgroups["North America"] + "</optgroup>"); | ||
+ | } | ||
+ | }); | ||
+ | $(".teamselector-multiple").change(function(event) { | ||
+ | //console.log("change"); | ||
+ | if ($(this).children(".none_selected").prop("selected")) { | ||
+ | $(this).find("option").not(".none_selected").prop("selected", false); | ||
+ | } | ||
+ | }); | ||
+ | }); | ||
+ | </script> | ||
+ | |||
+ | </div> | ||
+ | |||
+ | </div> | ||
</html> | </html> | ||
+ | {{Footer2019}} |
Latest revision as of 18:32, 31 July 2020
iGEM 2019 Judging Applications
On this page you will find information on: Judging at the Giant Jamboree, Who Should Apply to be a Judge?, Why Should You be an iGEM Judge?, Application Process Judge Benefits, and the Judge Application
Judge applications for the 2019 Giant Jamboree are now closed. Thank you to everyone who applied!
Judging at the Giant Jamboree
Judging in iGEM is a lot of fun, but it does require a strong commitment. iGEM teams work incredibly hard on their projects over the summer, so we need judges who are also committed to work hard to evaluate them and who are willing to take part in the whole process of iGEM judging. If you can spend time learning about the judging process during the summer, evaluating team wikis the week before the Jamboree, and attending the Jamboree from October 31-November 4, 2019, we would love to have you on board!
We need judges — both experienced and new — who really understand iGEM. We are aiming to recruit a judging panel that reflects our teams’ experience, so if you have previous iGEM experience we want you to apply!
As we approach the Giant Jamboree, we will provide educational resources to help judges learn how to evaluate teams (or provide a refresher, for those who have judged before), and we will help you get up to speed if you are selected.
Who Should Apply to be a Judge?
We're looking for:
- iGEM alumni who want to stay involved, including professionals, graduate students, and post-docs
- iGEM PIs, instructors, and advisors, both current and past
- People who have judged iGEM in the past
- Professionals in the synthetic biology, biotechnology, and engineering industries
- People who have experience in complimentary areas, such as the humanities, art and design, and software
If you have colleagues who you think should apply, please feel free to direct them to this form.
If you are a student on a 2019 iGEM team, you can't apply to be a judge this year. But you can apply when you graduate and become an iGEM alum!
Why Should You be an iGEM Judge?
Judging at the annual iGEM Giant Jamboree is an incredibly fulfilling and worthwhile experience for all judges, whether you're returning as a veteran judge or are a new judge this year. Some of the benefits include:
- Contribute to the iGEM Community: By volunteering to judge at the Giant Jamboree, you will contribute to what will be the most meaningful opportunity that these students experience in synthetic biology. Providing feedback to these dedicated students can be life changing for them as they continue through their academic career and beyond.
- Networking: Much like the iGEM teams, you'll have the chance to connect with people from around the globe, to expand your synthetic biology community, and to form new collaborations beyond the Giant Jamboree. You will meet fellow judges, students, and other professionals from around the world and different walks of life.
- Learn About New Technology: You will learn about the latest cutting edge work being done in synthetic biology from student teams who are driven to excel and who test the boundaries of synthetic biology through their projects.
Application Process
This year we are accepting applications on a rolling basis. We will be evaluating applications at the end of each month starting in May and will contact applicants approximately two weeks after the evaluation period. Status notifications (1. invitation to judge, 2. invitation to serve as a reserve judge, 3. invitation to re-apply, or 4. decline for 2019 with an invitation to apply next year) will be sent in the middle of each month, beginning in June, until our quota is full (expected by August). We encourage you to apply early to increase your chances of being selected!
You can apply to be a judge before knowing if you can fully commit to attending the Giant Jamboree. Applicants who are invited to join the judging panel will be asked to confirm their acceptance. We can also provide an official invitation letter if you require that to secure funding and/or permission from your institute to participate as a judge.
Once we have reached our quota of judges, we will close the application and add a notice to this page.
If you are selected as a judge, you MUST attend the iGEM 2019 Giant Jamboree in Boston (October 31-November 4) in person. We are unable to support remote participation for judges due to the nature of the interactions you will have with the teams throughout the event.
If you can only attend a portion of the Jamboree, this may make judging your assigned teams a challenge. We will work with you to try to accommodate your schedule constraints as best as possible, but we may rescind your invitation to judge in favor of another applicant who can attend the entire event. This will be evaluated on a case by case basis.
Judge Benefits
Instructor judges (current team PIs, instructors, and advisors) will receive a 50% discount on their Jamboree attendance fee.
Judges who are not affiliated with a team will receive free Jamboree attendance.
We are also excited to offer free childcare for all of our judges throughout the Giant Jamboree!
iGEM currently cannot provide travel funding for judges to attend.
Please email traci [AT] igem [DOT] org and/or vinoo [AT] igem [DOT] org if you have questions!
Judge Application Form
This form has been submitted.
You can unsubmit the form if you wish to make further edits.
Admin view (orange) is only visible to super users. (Hide admin view)
Go to Admin Mode / Go to Team Example / Go to Username:
Thank you!
Thank you for filling out this form. We look forward to picking a strong judging team for 2019!
Finished?
Need to make changes?