Line 3: | Line 3: | ||
<html> | <html> | ||
+ | <!--TO DO 2016: Fix the "team selector multiple" filling code--> | ||
<script type="text/javascript"> | <script type="text/javascript"> | ||
Line 167: | Line 168: | ||
<div class="highlightBoxB"> | <div class="highlightBoxB"> | ||
<h4> Note</h4> | <h4> Note</h4> | ||
− | <p>If you are selected as a judge, you need to attend the iGEM | + | <p>If you are selected as a judge, you need to attend the iGEM 2016 <a href="https://2016.igem.org/Giant_Jamboree">Giant Jamboree</a> in Boston (October 27-31). iGEM currently cannot provide travel funding for judges to attend.</p> |
− | <p>If you are registered as a Primary | + | <p>If you are registered as a Primary PI, Secondary PI, Instructor, or Advisor for a 2016 iGEM team, you will receive a 50% discount on your Giant Jamboree registration fee 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 | + | <p>If you are not on the roster of a 2016 iGEM team, your Jamboree attendance fee will be waived.</p> |
</div> | </div> | ||
Line 176: | Line 177: | ||
<fieldset> | <fieldset> | ||
<legend>Team Affiliations and Conflicts of Interest</legend> | <legend>Team Affiliations and Conflicts of Interest</legend> | ||
+ | <p>If you are on the roster of a 2016 iGEM team, or advising a 2016 iGEM team in any capacity, you must tell us here.</p> | ||
<table id="conflicts_holder"> | <table id="conflicts_holder"> | ||
Line 191: | Line 193: | ||
<td> | <td> | ||
<select multiple class="teamselector-multiple" size="15" name="Team affiliations" id="team_affiliations" data-form-field="team_affiliations"> | <select multiple class="teamselector-multiple" size="15" 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 2016 team affiliations</option> |
</select> | </select> | ||
</td> | </td> | ||
<td> | <td> | ||
<select multiple class="teamselector-multiple" size="15" name="Team conflicts of interest" id="team_conflicts" data-form-field="team_conflicts"> | <select multiple class="teamselector-multiple" size="15" 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 2016 team conflicts of interest</option> |
</select> | </select> | ||
</td> | </td> | ||
Line 213: | Line 215: | ||
<fieldset> <legend>Motivation</legend> | <fieldset> <legend>Motivation</legend> | ||
+ | |||
+ | <p>Please answer these questions in detail, especially if this is your first IGEM judging application.</p> | ||
<p class="question">Why do you want to be a judge in iGEM?</p> | <p class="question">Why do you want to be a judge in iGEM?</p> | ||
Line 220: | Line 224: | ||
<textarea rows="5" name="What professional experience do you have" id="professional_experience" data-form-field="professional_experience" maxlength="2000"></textarea> | <textarea rows="5" name="What professional experience do you have" id="professional_experience" data-form-field="professional_experience" maxlength="2000"></textarea> | ||
− | <p class="question">Have you judged student competitions other than iGEM before? If so, which ones? (e.g. FIRST, BIOMOD)</p> | + | <p class="question">Have you judged student competitions other than iGEM before? If so, which ones? (e.g. FIRST, BIOMOD, Science Olympiad)</p> |
<textarea rows="5" name="Have you judged other competitions" id="other_competitions" data-form-field="other_competitions" maxlength="2000"></textarea> | <textarea rows="5" name="Have you judged other competitions" id="other_competitions" data-form-field="other_competitions" maxlength="2000"></textarea> | ||
<p class="question">What features of an iGEM team and their project make them worthy of recognition?</p> | <p class="question">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/2015/d/d7/IGEM2015_Judging_Handbook.pdf" target="_blank">2015 Judging Handbook Part 1</a>. The 2016 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 230: | Line 234: | ||
<fieldset> <legend>Track Preferences</legend> | <fieldset> <legend>Track Preferences</legend> | ||
− | <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://2016.igem.org/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 254: | Line 258: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
− | <th> | + | <th>Diagnostics</th> |
− | <td><input type="radio" name=" | + | <td><input type="radio" name="pref_diagnostics" data-form-field="pref_diagnostics" value="first"></td> |
− | <td><input type="radio" name=" | + | <td><input type="radio" name="pref_diagnostics" data-form-field="pref_diagnostics" value="second"></td> |
− | <td><input type="radio" name=" | + | <td><input type="radio" name="pref_diagnostics" data-form-field="pref_diagnostics" value="third"></td> |
− | <td><input type="radio" name=" | + | <td><input type="radio" name="pref_diagnostics" data-form-field="pref_diagnostics" value="neutral"></td> |
− | <td><input type="radio" name=" | + | <td><input type="radio" name="pref_diagnostics" data-form-field="pref_diagnostics" value="avoid"></td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 300: | Line 304: | ||
<td><input type="radio" name="pref_hardware" data-form-field="pref_hardware" value="neutral"></td> | <td><input type="radio" name="pref_hardware" data-form-field="pref_hardware" value="neutral"></td> | ||
<td><input type="radio" name="pref_hardware" data-form-field="pref_hardware" value="avoid"></td> | <td><input type="radio" name="pref_hardware" data-form-field="pref_hardware" value="avoid"></td> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 348: | Line 344: | ||
<td><input type="radio" name="pref_newapplication" data-form-field="pref_newapplication" value="neutral"></td> | <td><input type="radio" name="pref_newapplication" data-form-field="pref_newapplication" value="neutral"></td> | ||
<td><input type="radio" name="pref_newapplication" data-form-field="pref_newapplication" value="avoid"></td> | <td><input type="radio" name="pref_newapplication" data-form-field="pref_newapplication" value="avoid"></td> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 365: | Line 353: | ||
<td><input type="radio" name="pref_software" data-form-field="pref_software" value="avoid"></td> | <td><input type="radio" name="pref_software" data-form-field="pref_software" value="avoid"></td> | ||
</tr> | </tr> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
<tr> | <tr> | ||
− | <th> | + | <th>Therapeutics</th> |
− | + | <td><input type="radio" name="pref_therapeutics" data-form-field="pref_therapeutics" value="first"></td> | |
− | + | <td><input type="radio" name="pref_therapeutics" data-form-field="pref_therapeutics" value="second"></td> | |
− | + | <td><input type="radio" name="pref_therapeutics" data-form-field="pref_therapeutics" value="third"></td> | |
− | + | <td><input type="radio" name="pref_therapeutics" data-form-field="pref_therapeutics" value="neutral"></td> | |
− | + | <td><input type="radio" name="pref_therapeutics" data-form-field="pref_therapeutics" value="avoid"></td> | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | <td><input type="radio" name=" | + | |
− | <td><input type="radio" name=" | + | |
− | <td><input type="radio" name=" | + | |
− | <td><input type="radio" name=" | + | |
− | <td><input type="radio" name=" | + | |
</tr> | </tr> | ||
</table> | </table> | ||
</fieldset> | </fieldset> | ||
+ | |||
<br /> | <br /> |
Revision as of 14:12, 25 April 2016
Template:JS/QueryStringUtilities
Welcome!
Hello, and welcome to the iGEM 2016 judging application form. We've created this form to simplify the process of applying to be a judge in iGEM. Judging is a great way to experience iGEM, see the Giant Jamboree, and interact with other senior members of the community behind the scenes.
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. 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 in September, we would love to have you on board!
Based on what we have learned over the past several years, we are making a few changes to simplify judging in 2016.
We are de-specializing judging, which will eliminate separate evaluation committees (e.g. poster, medal, practices). We will need judges who understand 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.
We're looking for:
- iGEM instructors and advisors
- People who have judged iGEM in the past
- People in the synthetic biology industry
- Synthetic biology researchers who are new to iGEM
- iGEM alumni who want to stay involved
If you have colleagues who you think should apply, please feel free to direct them to this form.
Lastly, I'm afraid that if you are a student on a 2016 iGEM team, you can't apply to be a judge this year. But you can apply when you graduate and become an iGEM alum!
Thank you for filling out this form. We look forward to picking a strong judging team for 2016!
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:
Finished?
Need to make changes?