Difference between revisions of "Judging/Apply"

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 2015 <a href="https://2015.igem.org/Giant_Jamboree">Giant Jamboree</a> in Boston (September 24 – 28). iGEM currently cannot provide travel funding for judges to attend.</p>
+
<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 Contact, Instructor, or Advisor on the roster of a 2015 iGEM team, you will need to pay the Jamboree registration fee even if you are selected as a judge. (You should think of the Jamboree registration fee as the final part of the team registration fee and how we charge more for bigger teams.) 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 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 2015 iGEM team, your Jamboree attendance fee will be waived.</p>
+
<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 2015 team affiliations</option>
+
<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 2015 team conflicts of interest</option>
+
<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/2014/3/39/JUDGESHANDBOOK_2014_1.0.pdf" target="_blank">2014 Judging Handbook Part 1</a>. The 2015 Judging Handbook will be available later this year.)</p>
+
<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://2015.igem.org/Tracks" target="_blank">the Track page</a> for more information on each track.</p>
+
<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>Community Labs</th>
+
<th>Diagnostics</th>
<td><input type="radio" name="pref_communitylabs" data-form-field="pref_communitylabs" value="first"></td>
+
<td><input type="radio" name="pref_diagnostics" data-form-field="pref_diagnostics" value="first"></td>
<td><input type="radio" name="pref_communitylabs" data-form-field="pref_communitylabs" value="second"></td>
+
<td><input type="radio" name="pref_diagnostics" data-form-field="pref_diagnostics" value="second"></td>
<td><input type="radio" name="pref_communitylabs" data-form-field="pref_communitylabs" value="third"></td>
+
<td><input type="radio" name="pref_diagnostics" data-form-field="pref_diagnostics" value="third"></td>
<td><input type="radio" name="pref_communitylabs" data-form-field="pref_communitylabs" value="neutral"></td>
+
<td><input type="radio" name="pref_diagnostics" data-form-field="pref_diagnostics" value="neutral"></td>
<td><input type="radio" name="pref_communitylabs" data-form-field="pref_communitylabs" value="avoid"></td>
+
<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>
 
<th>Health and Medicine</th>
 
<td><input type="radio" name="pref_health" data-form-field="pref_health" value="first"></td>
 
<td><input type="radio" name="pref_health" data-form-field="pref_health" value="second"></td>
 
<td><input type="radio" name="pref_health" data-form-field="pref_health" value="third"></td>
 
<td><input type="radio" name="pref_health" data-form-field="pref_health" value="neutral"></td>
 
<td><input type="radio" name="pref_health" data-form-field="pref_health" 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>
 
<th>Policy and Practices</th>
 
<td><input type="radio" name="pref_practices" data-form-field="pref_practices" value="first"></td>
 
<td><input type="radio" name="pref_practices" data-form-field="pref_practices" value="second"></td>
 
<td><input type="radio" name="pref_practices" data-form-field="pref_practices" value="third"></td>
 
<td><input type="radio" name="pref_practices" data-form-field="pref_practices" value="neutral"></td>
 
<td><input type="radio" name="pref_practices" data-form-field="pref_practices" 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>
</table>
 
 
</fieldset>
 
 
<fieldset> <legend>Specialist Knowledge Areas</legend>
 
 
<p>Based on what we have learned about judging over the past several years, we are de-specializing judging this year and eliminating subject-specific judging committees. This will require all judges to have a general level of knowledge about many areas of iGEM. For example, we will not have dedicated Human Practices judges. If you're not familiar with Human Practices, you'll need to learn more about this area in order to evaluate teams.</p>
 
<p>You will have help! We are creating educational materials to help you learn to evaluate these areas. We have more than a thousand previous projects to draw on for the best examples. We also have the judging committees who can help you and answer questions on these topics.</p>
 
<p>(See <a href="https://2015.igem.org/Judging/Awards#SpecialPrizes" target="_blank">the Awards page</a> for details about what each area means in iGEM.)</p>
 
 
<p class="question">Please indicate your level of knowledge in each area:</p>
 
 
<table id="spec_knowledge_table">
 
 
<tr>
 
<tr>
<th>Area</th>
+
<th>Therapeutics</th>
<th>Expert</th>
+
<td><input type="radio" name="pref_therapeutics" data-form-field="pref_therapeutics" value="first"></td>
<th>Great</th>
+
<td><input type="radio" name="pref_therapeutics" data-form-field="pref_therapeutics" value="second"></td>
<th>Some knowledge</th>
+
<td><input type="radio" name="pref_therapeutics" data-form-field="pref_therapeutics" value="third"></td>
<th>I'm prepared to learn</th>
+
<td><input type="radio" name="pref_therapeutics" data-form-field="pref_therapeutics" value="neutral"></td>
<th>Not qualified</th>
+
<td><input type="radio" name="pref_therapeutics" data-form-field="pref_therapeutics" value="avoid"></td>
</tr>
+
<tr>
+
<th>Applied Design</th>
+
<td><input type="radio" name="spec_applieddesign" data-form-field="spec_applieddesign" value="expert"></td>
+
<td><input type="radio" name="spec_applieddesign" data-form-field="spec_applieddesign" value="great"></td>
+
<td><input type="radio" name="spec_applieddesign" data-form-field="spec_applieddesign" value="some"></td>
+
<td><input type="radio" name="spec_applieddesign" data-form-field="spec_applieddesign" value="learn"></td>
+
<td><input type="radio" name="spec_applieddesign" data-form-field="spec_applieddesign" value="none"></td>
+
</tr>
+
<tr>
+
<th>Entrepreneurship</th>
+
<td><input type="radio" name="spec_entrepreneurship" data-form-field="spec_entrepreneurship" value="expert"></td>
+
<td><input type="radio" name="spec_entrepreneurship" data-form-field="spec_entrepreneurship" value="great"></td>
+
<td><input type="radio" name="spec_entrepreneurship" data-form-field="spec_entrepreneurship" value="some"></td>
+
<td><input type="radio" name="spec_entrepreneurship" data-form-field="spec_entrepreneurship" value="learn"></td>
+
<td><input type="radio" name="spec_entrepreneurship" data-form-field="spec_entrepreneurship" value="none"></td>
+
</tr>
+
<tr>
+
<th>Hardware</th>
+
<td><input type="radio" name="spec_hardware" data-form-field="spec_hardware" value="expert"></td>
+
<td><input type="radio" name="spec_hardware" data-form-field="spec_hardware" value="great"></td>
+
<td><input type="radio" name="spec_hardware" data-form-field="spec_hardware" value="some"></td>
+
<td><input type="radio" name="spec_hardware" data-form-field="spec_hardware" value="learn"></td>
+
<td><input type="radio" name="spec_hardware" data-form-field="spec_hardware" value="none"></td>
+
</tr>
+
<tr>
+
<th>Measurement</th>
+
<td><input type="radio" name="spec_measurement" data-form-field="spec_measurement" value="expert"></td>
+
<td><input type="radio" name="spec_measurement" data-form-field="spec_measurement" value="great"></td>
+
<td><input type="radio" name="spec_measurement" data-form-field="spec_measurement" value="some"></td>
+
<td><input type="radio" name="spec_measurement" data-form-field="spec_measurement" value="learn"></td>
+
<td><input type="radio" name="spec_measurement" data-form-field="spec_measurement" value="none"></td>
+
</tr>
+
<tr>
+
<th>Modeling</th>
+
<td><input type="radio" name="spec_modeling" data-form-field="spec_modeling" value="expert"></td>
+
<td><input type="radio" name="spec_modeling" data-form-field="spec_modeling" value="great"></td>
+
<td><input type="radio" name="spec_modeling" data-form-field="spec_modeling" value="some"></td>
+
<td><input type="radio" name="spec_modeling" data-form-field="spec_modeling" value="learn"></td>
+
<td><input type="radio" name="spec_modeling" data-form-field="spec_modeling" value="none"></td>
+
</tr>
+
<tr>
+
<th>Parts</th>
+
<td><input type="radio" name="spec_parts" data-form-field="spec_parts" value="expert"></td>
+
<td><input type="radio" name="spec_parts" data-form-field="spec_parts" value="great"></td>
+
<td><input type="radio" name="spec_parts" data-form-field="spec_parts" value="some"></td>
+
<td><input type="radio" name="spec_parts" data-form-field="spec_parts" value="learn"></td>
+
<td><input type="radio" name="spec_parts" data-form-field="spec_parts" value="none"></td>
+
</tr>
+
<tr>
+
<th>Human Practices</th>
+
<td><input type="radio" name="spec_practices" data-form-field="spec_practices" value="expert"></td>
+
<td><input type="radio" name="spec_practices" data-form-field="spec_practices" value="great"></td>
+
<td><input type="radio" name="spec_practices" data-form-field="spec_practices" value="some"></td>
+
<td><input type="radio" name="spec_practices" data-form-field="spec_practices" value="learn"></td>
+
<td><input type="radio" name="spec_practices" data-form-field="spec_practices" value="none"></td>
+
</tr>
+
<tr>
+
<th>Poster</th>
+
<td><input type="radio" name="spec_poster" data-form-field="spec_poster" value="expert"></td>
+
<td><input type="radio" name="spec_poster" data-form-field="spec_poster" value="great"></td>
+
<td><input type="radio" name="spec_poster" data-form-field="spec_poster" value="some"></td>
+
<td><input type="radio" name="spec_poster" data-form-field="spec_poster" value="learn"></td>
+
<td><input type="radio" name="spec_poster" data-form-field="spec_poster" value="none"></td>
+
</tr>
+
<tr>
+
<th>Software</th>
+
<td><input type="radio" name="spec_software" data-form-field="spec_software" value="expert"></td>
+
<td><input type="radio" name="spec_software" data-form-field="spec_software" value="great"></td>
+
<td><input type="radio" name="spec_software" data-form-field="spec_software" value="some"></td>
+
<td><input type="radio" name="spec_software" data-form-field="spec_software" value="learn"></td>
+
<td><input type="radio" name="spec_software" data-form-field="spec_software" value="none"></td>
+
 
</tr>
 
</tr>
 
</table>
 
</table>
  
 
</fieldset>
 
</fieldset>
 +
  
 
<br />
 
<br />

Revision as of 14:12, 25 April 2016

Template:JS/QueryStringUtilities


You have JavaScript disabled.

This page requires JavaScript in order to function correctly. Please enable JavaScript in your browser, then try again.

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.

New in 2016: Instructor judges will receive a 50% discount to their Jamboree registration fee!

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.

Click here to dismiss this message

-- Please choose a team

General

Full name: - (Username: -)

Email:

Gender:

Institution:

Institution type:

Position:

Region (where you currently live/work):

Number of years of iGEM experience:

Sweatshirt Size:

Dietary restrictions:

  • (If you have other dietary restrictions, please contact iGEM HQ.)

Are you available to attend the entire Giant Jamboree (September 24th-28th, 2015, in Boston)?

If not, what are your schedule conflicts?

Note

If you are selected as a judge, you need to attend the iGEM 2016 Giant Jamboree in Boston (October 27-31). iGEM currently cannot provide travel funding for judges to attend.

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.

If you are not on the roster of a 2016 iGEM team, your Jamboree attendance fee will be waived.

Team Affiliations and Conflicts of Interest

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.

Team Affiliations:
We encourage team instructors to be judges, but you can't judge your own team. Please select any teams you are officially affiliated with (i.e. you are on their roster of team members).

Conflicts of Interest:
There might be other reasons you could not judge a team impartially -- for example, a team from your alma mater, or a team that you advised informally. Please select any teams for which you have a conflict of interest.

To select multiple teams, use Ctrl-click or Cmd-click. We recommend that you update your answers once team registration closes in May (this form will save your answers and you can return to edit them).

Don't recognize a team name? Look it up in the Team List.

If you have any other conflicts of interest that are not indicated above, please describe them:

Motivation

Please answer these questions in detail, especially if this is your first IGEM judging application.

Why do you want to be a judge in iGEM?

What professional experience do you have that's relevant to iGEM (e.g., synthetic biology, hardware, software, human practices)?

Have you judged student competitions other than iGEM before? If so, which ones? (e.g. FIRST, BIOMOD, Science Olympiad)

What features of an iGEM team and their project make them worthy of recognition?

(New judges may want to familiarize themselves with the 2015 Judging Handbook Part 1. The 2016 Judging Handbook will be available later this year.)

Track Preferences

iGEM teams compete in several "tracks", based on the topics of their projects. Please see the Track page for more information on each track.

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 unable to evaluate teams in some track areas (software or measurement, for example), please put "Avoid" for those tracks.

Please indicate how highly you prefer each track. You may select multiple first, second, and third preferences.

Track First Second Third Neutral Avoid
Art and Design
Diagnostics
Energy
Environment
Food and Nutrition
Foundational Advance
Hardware
High School
Information Processing
Manufacturing
Measurement
New Application
Software
Therapeutics

Finished?

Need to make changes?

Visible Only to iGEM HQ

How much do we like this judge?

How much do we want this person to judge?

Calculation of how much work they did before the Jamboree:

Relative score of judging performance:

Notes on this judge:

iGEM HQ Use Only

Form Status:     

Admin Comment: