m (Reverted edits by THaddock (talk) to last revision by Sifuentes anita) |
|||
Line 248: | Line 248: | ||
<fieldset> | <fieldset> | ||
− | <h2> 1. | + | <h2> 1. General Information </h2> |
Line 340: | Line 340: | ||
</p> | </p> | ||
+ | <br> | ||
− | <p class="dropdown_question"> <span class="align_dropdowns"> | + | <p class="dropdown_question"> <span class="align_dropdowns">PI/Instructor: </span> |
− | <select name="Years Experience as an | + | <select name="Years Experience as an PI/Instructor" data-form-field="years_instructor" > |
<option value="0">0</option> | <option value="0">0</option> | ||
<option value="1">1</option> | <option value="1">1</option> | ||
Line 352: | Line 353: | ||
</select> | </select> | ||
</p> | </p> | ||
+ | |||
+ | <br> | ||
<p class="dropdown_question"> <span class="align_dropdowns">Advisor: </span> | <p class="dropdown_question"> <span class="align_dropdowns">Advisor: </span> | ||
Line 365: | Line 368: | ||
</p> | </p> | ||
− | + | <br> | |
<p class="dropdown_question"> <span class="align_dropdowns">Student: </span> | <p class="dropdown_question"> <span class="align_dropdowns">Student: </span> | ||
<select name="Years Experience as a Student" data-form-field="years_student" > | <select name="Years Experience as a Student" data-form-field="years_student" > | ||
Line 377: | Line 380: | ||
</select> | </select> | ||
</p> | </p> | ||
+ | |||
+ | <br> | ||
<p class="dropdown_question"> <span class="align_dropdowns">Volunteer: </span> | <p class="dropdown_question"> <span class="align_dropdowns">Volunteer: </span> | ||
Line 403: | Line 408: | ||
<fieldset> | <fieldset> | ||
− | <h2>2. | + | <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><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> | ||
Line 414: | Line 419: | ||
<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="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> | <li><label><input type="radio" name="Sweatshirt Size" data-form-field="size" id="XXL" value="XXL"> XXL</label> </li> | ||
− | |||
</ul> | </ul> | ||
Line 431: | Line 435: | ||
− | <p class="question">3. Are you available to attend the <b>entire</b> <a href="https:// | + | <p class="question">3. Are you available to attend the <b>entire</b> <a href="https |
+ | ://2019.igem.org/Giant_Jamboree">Giant Jamboree</a> (October 31 - November 4 2019, in Boston)?</p> | ||
<ul> | <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="yes"> Yes</label></li> | ||
Line 444: | Line 449: | ||
<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_wed_eve" value="yes"> Yes</label><br /><br> | |
− | + | <label><input type="radio" name="Availability Thurs Oct 31, Evening" data-form-field="available_wed_eve" value="no"> No</label> | |
− | + | </td> | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
</tr> | </tr> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | ||
− | + | <tr> | |
− | + | <th>Thursday <br> November 1</th> | |
− | + | <td><label><input type="radio" name="Availability Fri Nov 1, Morning" data-form-field="available_thu_morn" value="yes"> Yes</label><br /><br> | |
− | + | <label><input type="radio" name="Availability Fri Nov 1, Morning" data-form-field="available_thu_morn" value="no"> No</label> | |
− | + | </td> | |
− | + | <td><label><input type="radio" name="Availability Fri Nov 1, Evening" data-form-field="available_thu_eve" value="yes"> Yes</label><br /><br> | |
+ | <label><input type="radio" name="Availability Fri Nov 1, Evening" data-form-field="available_thu_eve" value="no"> No</label> | ||
+ | </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <th> | + | <th>Friday <br> November 2</th> |
− | + | <td><label><input type="radio" name="Availability Sat Nov 2, Morning" data-form-field="available_fri_morn" value="yes"> Yes</label><br /><br> | |
− | + | <label><input type="radio" name="Availability Sat Nov 2, Morning" data-form-field="available_fri_morn" value="no"> No</label> | |
− | + | </td> | |
− | + | <td><label><input type="radio" name="Availability Sat Nov 2, Evening" data-form-field="available_fri_eve" value="yes"> Yes</label><br /><br> | |
− | + | <label><input type="radio" name="Availability Sat Nov 2, Evening" data-form-field="available_fri_eve" value="no"> No</label> | |
− | + | </td> | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
</tr> | </tr> | ||
Line 502: | Line 485: | ||
<tr> | <tr> | ||
− | <th> | + | <th>Saturday <br> November 3</th> |
− | + | <td><label><input type="radio" name="Availability Sun Nov 3, Morning" data-form-field="available_sat_morn" value="yes"> Yes</label><br /><br> | |
− | + | <label><input type="radio" name="Availability Sun Nov 3, Morning" data-form-field="available_sat_morn" value="no"> No</label> | |
− | + | </td> | |
− | + | <td><label><input type="radio" name="Availability Sun Nov 3, Evening" data-form-field="available_sat_eve" value="yes"> Yes</label><br /><br> | |
− | + | <label><input type="radio" name="Availability Sun Nov 3, Evening" data-form-field="available_sat_eve" value="no"> No</label> | |
− | + | </td> | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | + | <th>Sunday <br> November 4</th> | |
− | + | <td><label><input type="radio" name="Availability Mon Nov 4, Morning" data-form-field="available_sun_morn" value="yes"> Yes</label><br /><br> | |
− | + | <label><input type="radio" name="Availability Mon Nov 4, Morning" data-form-field="available_sun_morn" value="no"> No</label> | |
− | + | </td> | |
− | + | <td><label><input type="radio" name="Availability Mon Nov 4, Evening" data-form-field="available_sun_eve" value="yes"> Yes</label><br /><br> | |
− | + | <label><input type="radio" name="Availability Mon Nov 4, Evening" data-form-field="available_sun_eve" value="no"> No</label> | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
</td> | </td> | ||
− | |||
</tr> | </tr> | ||
− | + | ||
</table> | </table> | ||
Line 557: | Line 513: | ||
<div class="column half_size"> | <div class="column half_size"> | ||
− | <div class="highlight | + | <div class="highlight note"> |
− | + | <h3> Note</h3> | |
− | + | <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>iGEM currently cannot provide travel funding</b> for judges to attend.</p> | |
− | + | <p>If you are registered as a Primary PI, Secondary PI, Instructor, or Advisor for a 2019 iGEM team, <b>you will receive a 50% discount on your Giant Jamboree registration fee</b> if you are selected as a judge. As both an instructor and a judge, your primary role must be as an instructor. We ensure that your judging assignments do not conflict with your own team's presentation.</p> | |
− | + | <p>If you are not on the roster of a 2019 iGEM team, <b>your Jamboree attendance fee will be waived</b>.</p> | |
− | + | ||
− | <p>If you are selected as a judge, you <b>MUST</b> attend the iGEM | + | |
− | <p>If you are registered as a Primary PI, Secondary PI, Instructor, or Advisor for a | + | |
− | <p>If you are not on the roster of a | + | |
</div> | </div> | ||
</div> | </div> | ||
Line 583: | Line 535: | ||
<fieldset> | <fieldset> | ||
− | <h2> 3. | + | <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> | <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> | ||
Line 598: | Line 550: | ||
<br><br> | <br><br> | ||
<select multiple class="teamselector-multiple" size="20" name="Team affiliations" id="team_affiliations" data-form-field="team_affiliations"> | <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 | + | <option class='none_selected'>I have no 2019 team affiliations</option> |
</select> | </select> | ||
Line 610: | Line 562: | ||
<select multiple class="teamselector-multiple" size="20" name="Team conflicts of interest" id="team_conflicts" data-form-field="team_conflicts"> | <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 | + | <option class='none_selected'>I have no 2019 team conflicts of interest</option> |
</select> | </select> | ||
Line 636: | Line 588: | ||
<fieldset> | <fieldset> | ||
− | <h2>4. | + | <h2>4. Motivation</h2> |
<p>Please answer these questions in detail.</p> | <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></p> | <p>Did you apply to judge last year? <a id="last_years_application_link" target="_blank">View your answers from last year.</a></p> | ||
Line 652: | Line 604: | ||
<p class="question">4. What features of an iGEM team and their project make them worthy of recognition?</p> | <p class="question">4. What features of an iGEM team and their project make them worthy of recognition?</p> | ||
− | <p>(New judges may want to familiarize themselves with the <a href="https://static.igem.org/mediawiki/ | + | <p>(New judges may want to familiarize themselves with the <a href="https://static.igem.org/mediawiki/2018/2/2f/2018_judging_handbook.pdf" target="_blank">2018 Judging Handbook</a>. The 2019 Judging Handbook will be available later this year.)</p> |
<textarea rows="6" name="What makes an iGEM team worthy of recognition" id="worthy" data-form-field="worthy"></textarea maxlength="2500"> | <textarea rows="6" name="What makes an iGEM team worthy of recognition" id="worthy" data-form-field="worthy"></textarea maxlength="2500"> | ||
</fieldset> | </fieldset> | ||
Line 668: | Line 620: | ||
<fieldset> | <fieldset> | ||
− | <h2>5. | + | <h2>5. Track Preferences </h2> |
− | <p>iGEM teams compete in several "tracks", based on the topics of their projects. Please see <a href="https:// | + | <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 or measurement, for example), please put "Avoid" for those tracks.</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 or measurement, for example), please put "Avoid" for those tracks.</p> | ||
Line 685: | Line 637: | ||
<th>Avoid</th> | <th>Avoid</th> | ||
</tr> | </tr> | ||
+ | <!-- | ||
<tr> | <tr> | ||
<th>Art and Design</th> | <th>Art and Design</th> | ||
Line 693: | Line 646: | ||
<td><input type="radio" name="Track Preference: Art and Design" data-form-field="pref_artdesign" value="avoid"></td> | <td><input type="radio" name="Track Preference: Art and Design" data-form-field="pref_artdesign" value="avoid"></td> | ||
</tr> | </tr> | ||
+ | --> | ||
<tr> | <tr> | ||
<th>Diagnostics</th> | <th>Diagnostics</th> | ||
Line 733: | Line 687: | ||
<td><input type="radio" name="Track Preference: Foundational Advance" data-form-field="pref_foundational" value="avoid"></td> | <td><input type="radio" name="Track Preference: Foundational Advance" data-form-field="pref_foundational" value="avoid"></td> | ||
</tr> | </tr> | ||
+ | |||
+ | <!-- | ||
<tr> | <tr> | ||
<th>Hardware</th> | <th>Hardware</th> | ||
Line 741: | Line 697: | ||
<td><input type="radio" name="Track Preference: Hardware" data-form-field="pref_hardware" value="avoid"></td> | <td><input type="radio" name="Track Preference: Hardware" data-form-field="pref_hardware" value="avoid"></td> | ||
</tr> | </tr> | ||
+ | --> | ||
+ | |||
<tr> | <tr> | ||
<th>High School</th> | <th>High School</th> | ||
Line 765: | Line 723: | ||
<td><input type="radio" name="Track Preference: Manufacturing" data-form-field="pref_manufacturing" value="avoid"></td> | <td><input type="radio" name="Track Preference: Manufacturing" data-form-field="pref_manufacturing" value="avoid"></td> | ||
</tr> | </tr> | ||
+ | |||
+ | <!-- | ||
<tr> | <tr> | ||
<th>Measurement</th> | <th>Measurement</th> | ||
Line 773: | Line 733: | ||
<td><input type="radio" name="Track Preference: Measurement" data-form-field="pref_measurement" value="avoid"></td> | <td><input type="radio" name="Track Preference: Measurement" data-form-field="pref_measurement" value="avoid"></td> | ||
</tr> | </tr> | ||
+ | --> | ||
+ | |||
<tr> | <tr> | ||
<th>New Application</th> | <th>New Application</th> | ||
Line 780: | Line 742: | ||
<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="neutral"></td> | ||
<td><input type="radio" name="Track Preference: New Application" data-form-field="pref_newapplication" value="avoid"></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: Software" data-form-field="pref_open" value="first"></td> | ||
+ | <td><input type="radio" name="Track Preference: Software" data-form-field="pref_open" value="second"></td> | ||
+ | <td><input type="radio" name="Track Preference: Software" data-form-field="pref_open" value="third"></td> | ||
+ | <td><input type="radio" name="Track Preference: Software" data-form-field="pref_open" value="neutral"></td> | ||
+ | <td><input type="radio" name="Track Preference: Software" data-form-field="pref_open" value="avoid"></td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 812: | Line 782: | ||
<h3 style="margin:auto; text-align:center"> Thank you! </h3> | <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 | + | <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> |
Line 886: | Line 856: | ||
timeout: 30000, | timeout: 30000, | ||
dataType: "json", | dataType: "json", | ||
− | data: {command: "get_team_list", year: " | + | data: {command: "get_team_list", year: "2019"}, //**Make this auto-update itself |
error: function(jqxhr, textStatus, errorThrown) { | error: function(jqxhr, textStatus, errorThrown) { | ||
general_ajax_error( jqxhr, textStatus, errorThrown, | general_ajax_error( jqxhr, textStatus, errorThrown, |
Revision as of 22:50, 4 March 2019
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, and Judge Benefits,
We will send out notifications about the opening of the judging applications through our Newsletters, so please sign up for our newsletters to stay informed!
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 experienced judges who understand iGEM, and new judges who are willing to learn about iGEM. We will provide educational resources to help judges learn how to evaluate teams, 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 PIs, instructors, and advisors, both current and past
- iGEM alumni who want to stay involved
- People who have judged iGEM in the past
- Synthetic biology researchers who are new to iGEM, including graduate students and post-docs
- 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:
- Networking: You will meet fellow judges, students, and other professionals from around the world and different walks of life. Find your post-doc, network with industry leaders, and learn how others are doing synthetic biology worldwide!
- 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.
- Collaborate: 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.
- 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.
Application Process
This year we are accepting applications on a rolling basis so there was no deadline to apply earlier in the year. We will be evaluating applications at the end of each month starting in April and will contact applicants approximately two weeks after the evaluation period. This means 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 May, until our quota is full (expected by August). We encourage you to apply early to increase your chances of being selected!
Applicants who are invited to join the judging panel will be asked to confirm their acceptance, so you can apply to be a judge prior to knowing if you can fully commit to attending the Giant Jamboree. 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.
Judge Benefits
Instructor judges (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!
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?