Difference between revisions of "Judging/Apply"

m
 
(27 intermediate revisions by 5 users not shown)
Line 1: Line 1:
 
{{HTML/JSDisabled}}
 
{{HTML/JSDisabled}}
−
 
 
<html>
 
<html>
−
<!--TO DO 2016: Fix the "team selector multiple" filling code-->
 
  
 
<script type="text/javascript">
 
<script type="text/javascript">
Line 19: Line 17:
  
 
<link rel="stylesheet" type="text/css" href="https://igem.org/Template:CSS/Forms?action=raw&ctype=text/css" />
 
<link rel="stylesheet" type="text/css" href="https://igem.org/Template:CSS/Forms?action=raw&ctype=text/css" />
−
<script src="https://igem.org/Template:JS/KForms_2.3?action=raw&ctype=text/javascript"></script>
+
<script src="https://igem.org/Template:JS/KForms_2pt4?action=raw&ctype=text/javascript"></script>
  
 
<style type="text/css">
 
<style type="text/css">
Line 27: Line 25:
 
color: black;
 
color: black;
 
}
 
}
−
 
+
#toptitle, #team_list_dropdown
−
#toptitle
+
 
{
 
{
 
display: none;
 
display: none;
 
}
 
}
−
 
 
#modes
 
#modes
 
{
 
{
 
text-align: right;
 
text-align: right;
 
}
 
}
−
 
 
.button
 
.button
 
{
 
{
Line 45: Line 40:
 
cursor: pointer;
 
cursor: pointer;
 
}
 
}
−
 
 
#conflicts_holder td
 
#conflicts_holder td
 
{
 
{
 
width: 45%;
 
width: 45%;
 
}
 
}
−
 
 
p#new-in-2016
 
p#new-in-2016
 
{
 
{
Line 61: Line 54:
 
padding: 10px;
 
padding: 10px;
 
}
 
}
−
 
 
.highlightBoxB {
 
.highlightBoxB {
 
     background-color: #f2f2f2;
 
     background-color: #f2f2f2;
Line 81: Line 73:
 
<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. 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!</p>
 
<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. 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!</p>
 
<p>We need judges who understand iGEM, and 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.</p>
 
<p>We need judges who understand iGEM, and 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.</p>
 +
 +
<h4>*** The judging applications have closed for 2016. Any applications received after July 15th 2016 may be considered for iGEM 2017.***</h4>
  
 
<div class="twoColumns" style="width: 430px;">
 
<div class="twoColumns" style="width: 430px;">
Line 94: Line 88:
 
</div>
 
</div>
 
<div class="twoColumns" style="width: 430px;">
 
<div class="twoColumns" style="width: 430px;">
−
<p id="new-in-2016">New in 2016: Instructor judges will receive a 50% discount to their Jamboree registration fee!</p>
+
<p id="new-in-2016">NEW: Instructor judges will receive a 50% discount on their Jamboree attendance fee!</p>
 
</div>
 
</div>
 
<div class="clear"></div>
 
<div class="clear"></div>
Line 101: Line 95:
 
<p>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!</p>
 
<p>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!</p>
 
<p>Thank you for filling out this form. We look forward to picking a strong judging team for 2016!</p>
 
<p>Thank you for filling out this form. We look forward to picking a strong judging team for 2016!</p>
 +
 +
<h4> Please email kim [AT] igem [DOT] org if you have questions!</h4>
  
 
</html>{{HTML/Temp/FormTitleAndMode}}<html>
 
</html>{{HTML/Temp/FormTitleAndMode}}<html>
Line 117: Line 113:
 
<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="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="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"></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"></li>
 
</ul>
 
</ul>
  
Line 129: Line 125:
 
<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="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="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"></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"></li>
 
</ul>
 
</ul>
  
Line 140: Line 136:
 
<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="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="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"></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"></li>
 
</ul>
 
</ul>
  
Line 151: Line 147:
 
</p>
 
</p>
  
−
<p class="question">Number of years of iGEM experience:
+
<p class="question">Number of years of iGEM experience as a...</p>
−
<label><input type="radio" name="Years of iGEM Experience" data-form-field="years" value="0"> 0</label>  
+
Judge:  
−
<label><input type="radio" name="Years of iGEM Experience" data-form-field="years" value="1"> 1</label>  
+
<select name="Years Experience as a Judge" data-form-field="years_judge">
−
<label><input type="radio" name="Years of iGEM Experience" data-form-field="years" value="2"> 2</label>  
+
<option value="0">0</option>
−
<label><input type="radio" name="Years of iGEM Experience" data-form-field="years" value="3"> 3</label>  
+
<option value="1">1</option>
−
<label><input type="radio" name="Years of iGEM Experience" data-form-field="years" value="4"> 4</label>  
+
<option value="2">2</option>
−
<label><input type="radio" name="Years of iGEM Experience" data-form-field="years" value="5"> 5</label>  
+
<option value="3">3</option>
−
<label><input type="radio" name="Years of iGEM Experience" data-form-field="years" value="6+"> 6+</label>  
+
<option value="4">4</option>
−
</p>
+
<option value="5">5</option>
 +
<option value="6+">6+</option>
 +
</select> &nbsp;&nbsp;&nbsp;&nbsp;
 +
Instructor / PI:
 +
<select name="Years Experience as an Instructor/PI" 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> &nbsp;&nbsp;&nbsp;&nbsp;
 +
Advisor:
 +
<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> &nbsp;&nbsp;&nbsp;&nbsp;
 +
Student:
 +
<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> &nbsp;&nbsp;&nbsp;&nbsp;
 +
Volunteer:
 +
<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>
  
 
</fieldset>
 
</fieldset>
Line 180: Line 218:
 
<ul>
 
<ul>
 
<li><label><input type="checkbox" data-validation="optional" name="Vegetarian" id="vegetarian" data-form-field="vegetarian"> Vegetarian</label></li>
 
<li><label><input type="checkbox" data-validation="optional" name="Vegetarian" id="vegetarian" data-form-field="vegetarian"> Vegetarian</label></li>
−
<li><label><input type="checkbox" data-validation="optional" name="Food allergy" id="allergy" data-form-field="allergy"> Food Allergy (describe):</label> <input type="text" size="60" data-validation="allergy" name="Food allergy" data-form-field="allergy-describe"></li>
+
<li><label><input type="checkbox" data-validation="optional" name="Food allergy" id="allergy" data-form-field="allergy"> Food Allergy (describe):</label> <input type="text" size="60" data-validation="#allergy" name="Food allergy" data-form-field="allergy-describe"></li>
 
<li>(If you have other dietary restrictions, please <a href="https://igem.org/Contact">contact iGEM HQ</a>.)</li>
 
<li>(If you have other dietary restrictions, please <a href="https://igem.org/Contact">contact iGEM HQ</a>.)</li>
 
</ul>
 
</ul>
Line 212: Line 250:
 
<label><input type="radio" name="Availability Fri Oct 28, Evening" data-form-field="available_fri_eve" value="no"> No</label>
 
<label><input type="radio" name="Availability Fri Oct 28, Evening" data-form-field="available_fri_eve" value="no"> No</label>
 
</td>
 
</td>
−
<td><label><input type="radio" name="Sat Oct 29, Morning" data-form-field="available_sat_morn" value="yes"> Yes</label><br />
+
<td><label><input type="radio" name="Availability Sat Oct 29, Morning" data-form-field="available_sat_morn" value="yes"> Yes</label><br />
 
<label><input type="radio" name="Availability Sat Oct 29, Morning" data-form-field="available_sat_morn" value="no"> No</label>
 
<label><input type="radio" name="Availability Sat Oct 29, Morning" data-form-field="available_sat_morn" value="no"> No</label>
 
</td>
 
</td>
−
<td><label><input type="radio" name="Sat Oct 29, Evening" data-form-field="available_sat_eve" value="yes"> Yes</label><br />
+
<td><label><input type="radio" name="Availability Sat Oct 29, Evening" data-form-field="available_sat_eve" value="yes"> Yes</label><br />
 
<label><input type="radio" name="Availability Sat Oct 29, Evening" data-form-field="available_sat_eve" value="no"> No</label>
 
<label><input type="radio" name="Availability Sat Oct 29, Evening" data-form-field="available_sat_eve" value="no"> No</label>
 
</td>
 
</td>
−
<td><label><input type="radio" name="Sun Oct 30, Morning" data-form-field="available_sun_morn" value="yes"> Yes</label><br />
+
<td><label><input type="radio" name="Availability Sun Oct 30, Morning" data-form-field="available_sun_morn" value="yes"> Yes</label><br />
 
<label><input type="radio" name="Availability Sun Oct 30, Morning" data-form-field="available_sun_morn" value="no"> No</label>
 
<label><input type="radio" name="Availability Sun Oct 30, Morning" data-form-field="available_sun_morn" value="no"> No</label>
 
</td>
 
</td>
−
<td><label><input type="radio" name="Sun Oct 30, Evening" data-form-field="available_sun_eve" value="yes"> Yes</label><br />
+
<td><label><input type="radio" name="Availability Sun Oct 30, Evening" data-form-field="available_sun_eve" value="yes"> Yes</label><br />
 
<label><input type="radio" name="Availability Sun Oct 30, Evening" data-form-field="available_sun_eve" value="no"> No</label>
 
<label><input type="radio" name="Availability Sun Oct 30, Evening" data-form-field="available_sun_eve" value="no"> No</label>
 
</td>
 
</td>
−
<td><label><input type="radio" name="Mon Oct 31, Morning" data-form-field="available_mon_morn" value="yes"> Yes</label><br />
+
<td><label><input type="radio" name="Availability Mon Oct 31, Morning" data-form-field="available_mon_morn" value="yes"> Yes</label><br />
 
<label><input type="radio" name="Availability Mon Oct 31, Morning" data-form-field="available_mon_morn" value="no"> No</label>
 
<label><input type="radio" name="Availability Mon Oct 31, Morning" data-form-field="available_mon_morn" value="no"> No</label>
 
</td>
 
</td>
Line 240: Line 278:
  
 
<fieldset>
 
<fieldset>
−
<legend>Team Affiliations and Conflicts of Interest</legend>
+
<legend>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>
+
<p>There are many possible reasons why you might be unable to judge some teams impartially. For example:</p>
 +
<ul style="list-style: disc outside none;">
 +
<li>If you are a PI or instructor for the team</li>
 +
<li>If the team comes from a school that you attended, or a school where you work</li>
 +
<li>If you mentored or advised the team informally</li>
 +
</ul>
 +
<p>These situations could lead to a conflict of interest. iGEM takes conflicts of interests very seriously. Judges are not permitted to judge 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>Please tell us about your conflicts of interest here.</p>
  
 
<table id="conflicts_holder">
 
<table id="conflicts_holder">
Line 247: Line 292:
 
<td>
 
<td>
 
<p><span class="question">Team Affiliations:</span><br>
 
<p><span class="question">Team Affiliations:</span><br>
−
  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).</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>
 
</td>
 
</td>
 
<td>
 
<td>
 
<p><span class="question">Conflicts of Interest:</span> <br>
 
<p><span class="question">Conflicts of Interest:</span> <br>
−
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.</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>
 
</td>
 
</td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
 
<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="20" name="Team affiliations" id="team_affiliations" data-form-field="team_affiliations">
 
<option class='none_selected'>I have no 2016 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="20" name="Team conflicts of interest" id="team_conflicts" data-form-field="team_conflicts">
 
<option class='none_selected'>I have no 2016 team conflicts of interest</option>
 
<option class='none_selected'>I have no 2016 team conflicts of interest</option>
 
</select>
 
</select>
Line 269: Line 314:
  
 
<div class="highlightBoxB">
 
<div class="highlightBoxB">
−
<p>To select multiple teams, use <i><b> Ctrl-click or Cmd-click</i></b>.
+
<p>To select multiple teams, use <i><b> Ctrl-click or Cmd-click</i></b>.</p>
−
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).</p>
+
 
<p>Don't recognize a team name? Look it up in the <a target="_blank" href="https://igem.org/Team_List">Team List</a>.</p>
 
<p>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>
 
</div>
Line 316: Line 360:
 
<tr>
 
<tr>
 
<th>Art and Design</th>
 
<th>Art and Design</th>
−
<td><input type="radio" name="pref_artdesign" data-form-field="pref_artdesign" value="first"></td>
+
<td><input type="radio" name="Track Preference: Art and Design" data-form-field="pref_artdesign" value="first"></td>
−
<td><input type="radio" name="pref_artdesign" data-form-field="pref_artdesign" value="second"></td>
+
<td><input type="radio" name="Track Preference: Art and Design" data-form-field="pref_artdesign" value="second"></td>
−
<td><input type="radio" name="pref_artdesign" data-form-field="pref_artdesign" value="third"></td>
+
<td><input type="radio" name="Track Preference: Art and Design" data-form-field="pref_artdesign" value="third"></td>
−
<td><input type="radio" name="pref_artdesign" data-form-field="pref_artdesign" value="neutral"></td>
+
<td><input type="radio" name="Track Preference: Art and Design" data-form-field="pref_artdesign" value="neutral"></td>
−
<td><input type="radio" name="pref_artdesign" 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>
−
<td><input type="radio" name="pref_diagnostics" data-form-field="pref_diagnostics" value="first"></td>
+
<td><input type="radio" name="Track Preference: Diagnostics" data-form-field="pref_diagnostics" value="first"></td>
−
<td><input type="radio" name="pref_diagnostics" data-form-field="pref_diagnostics" value="second"></td>
+
<td><input type="radio" name="Track Preference: Diagnostics" data-form-field="pref_diagnostics" value="second"></td>
−
<td><input type="radio" name="pref_diagnostics" data-form-field="pref_diagnostics" value="third"></td>
+
<td><input type="radio" name="Track Preference: Diagnostics" data-form-field="pref_diagnostics" value="third"></td>
−
<td><input type="radio" name="pref_diagnostics" data-form-field="pref_diagnostics" value="neutral"></td>
+
<td><input type="radio" name="Track Preference: Diagnostics" data-form-field="pref_diagnostics" value="neutral"></td>
−
<td><input type="radio" name="pref_diagnostics" data-form-field="pref_diagnostics" value="avoid"></td>
+
<td><input type="radio" name="Track Preference: Diagnostics" data-form-field="pref_diagnostics" value="avoid"></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
 
<th>Energy</th>
 
<th>Energy</th>
−
<td><input type="radio" name="pref_energy" data-form-field="pref_energy" value="first"></td>
+
<td><input type="radio" name="Track Preference: Energy" data-form-field="pref_energy" value="first"></td>
−
<td><input type="radio" name="pref_energy" data-form-field="pref_energy" value="second"></td>
+
<td><input type="radio" name="Track Preference: Energy" data-form-field="pref_energy" value="second"></td>
−
<td><input type="radio" name="pref_energy" data-form-field="pref_energy" value="third"></td>
+
<td><input type="radio" name="Track Preference: Energy" data-form-field="pref_energy" value="third"></td>
−
<td><input type="radio" name="pref_energy" data-form-field="pref_energy" value="neutral"></td>
+
<td><input type="radio" name="Track Preference: Energy" data-form-field="pref_energy" value="neutral"></td>
−
<td><input type="radio" name="pref_energy" data-form-field="pref_energy" value="avoid"></td>
+
<td><input type="radio" name="Track Preference: Energy" data-form-field="pref_energy" value="avoid"></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
 
<th>Environment</th>
 
<th>Environment</th>
−
<td><input type="radio" name="pref_environment" data-form-field="pref_environment" value="first"></td>
+
<td><input type="radio" name="Track Preference: Environment" data-form-field="pref_environment" value="first"></td>
−
<td><input type="radio" name="pref_environment" data-form-field="pref_environment" value="second"></td>
+
<td><input type="radio" name="Track Preference: Environment" data-form-field="pref_environment" value="second"></td>
−
<td><input type="radio" name="pref_environment" data-form-field="pref_environment" value="third"></td>
+
<td><input type="radio" name="Track Preference: Environment" data-form-field="pref_environment" value="third"></td>
−
<td><input type="radio" name="pref_environment" data-form-field="pref_environment" value="neutral"></td>
+
<td><input type="radio" name="Track Preference: Environment" data-form-field="pref_environment" value="neutral"></td>
−
<td><input type="radio" name="pref_environment" data-form-field="pref_environment" value="avoid"></td>
+
<td><input type="radio" name="Track Preference: Environment" data-form-field="pref_environment" value="avoid"></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
 
<th>Food and Nutrition</th>
 
<th>Food and Nutrition</th>
−
<td><input type="radio" name="pref_food" data-form-field="pref_food" value="first"></td>
+
<td><input type="radio" name="Track Preference: Food and Nutrition" data-form-field="pref_food" value="first"></td>
−
<td><input type="radio" name="pref_food" data-form-field="pref_food" value="second"></td>
+
<td><input type="radio" name="Track Preference: Food and Nutrition" data-form-field="pref_food" value="second"></td>
−
<td><input type="radio" name="pref_food" data-form-field="pref_food" value="third"></td>
+
<td><input type="radio" name="Track Preference: Food and Nutrition" data-form-field="pref_food" value="third"></td>
−
<td><input type="radio" name="pref_food" data-form-field="pref_food" value="neutral"></td>
+
<td><input type="radio" name="Track Preference: Food and Nutrition" data-form-field="pref_food" value="neutral"></td>
−
<td><input type="radio" name="pref_food" data-form-field="pref_food" value="avoid"></td>
+
<td><input type="radio" name="Track Preference: Food and Nutrition" data-form-field="pref_food" value="avoid"></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
 
<th>Foundational Advance</th>
 
<th>Foundational Advance</th>
−
<td><input type="radio" name="pref_foundational" data-form-field="pref_foundational" value="first"></td>
+
<td><input type="radio" name="Track Preference: Foundational Advance" data-form-field="pref_foundational" value="first"></td>
−
<td><input type="radio" name="pref_foundational" data-form-field="pref_foundational" value="second"></td>
+
<td><input type="radio" name="Track Preference: Foundational Advance" data-form-field="pref_foundational" value="second"></td>
−
<td><input type="radio" name="pref_foundational" data-form-field="pref_foundational" value="third"></td>
+
<td><input type="radio" name="Track Preference: Foundational Advance" data-form-field="pref_foundational" value="third"></td>
−
<td><input type="radio" name="pref_foundational" data-form-field="pref_foundational" value="neutral"></td>
+
<td><input type="radio" name="Track Preference: Foundational Advance" data-form-field="pref_foundational" value="neutral"></td>
−
<td><input type="radio" name="pref_foundational" 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>
−
<td><input type="radio" name="pref_hardware" data-form-field="pref_hardware" value="first"></td>
+
<td><input type="radio" name="Track Preference: Hardware" data-form-field="pref_hardware" value="first"></td>
−
<td><input type="radio" name="pref_hardware" data-form-field="pref_hardware" value="second"></td>
+
<td><input type="radio" name="Track Preference: Hardware" data-form-field="pref_hardware" value="second"></td>
−
<td><input type="radio" name="pref_hardware" data-form-field="pref_hardware" value="third"></td>
+
<td><input type="radio" name="Track Preference: Hardware" data-form-field="pref_hardware" value="third"></td>
−
<td><input type="radio" name="pref_hardware" data-form-field="pref_hardware" value="neutral"></td>
+
<td><input type="radio" name="Track Preference: 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="Track Preference: Hardware" data-form-field="pref_hardware" value="avoid"></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
 
<th>High School</th>
 
<th>High School</th>
−
<td><input type="radio" name="pref_highschool" data-form-field="pref_highschool" value="first"></td>
+
<td><input type="radio" name="Track Preference: High School" data-form-field="pref_highschool" value="first"></td>
−
<td><input type="radio" name="pref_highschool" data-form-field="pref_highschool" value="second"></td>
+
<td><input type="radio" name="Track Preference: High School" data-form-field="pref_highschool" value="second"></td>
−
<td><input type="radio" name="pref_highschool" data-form-field="pref_highschool" value="third"></td>
+
<td><input type="radio" name="Track Preference: High School" data-form-field="pref_highschool" value="third"></td>
−
<td><input type="radio" name="pref_highschool" data-form-field="pref_highschool" value="neutral"></td>
+
<td><input type="radio" name="Track Preference: High School" data-form-field="pref_highschool" value="neutral"></td>
−
<td><input type="radio" name="pref_highschool" data-form-field="pref_highschool" value="avoid"></td>
+
<td><input type="radio" name="Track Preference: High School" data-form-field="pref_highschool" value="avoid"></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
 
<th>Information Processing</th>
 
<th>Information Processing</th>
−
<td><input type="radio" name="pref_info" data-form-field="pref_info" value="first"></td>
+
<td><input type="radio" name="Track Preference: Information Processing" data-form-field="pref_info" value="first"></td>
−
<td><input type="radio" name="pref_info" data-form-field="pref_info" value="second"></td>
+
<td><input type="radio" name="Track Preference: Information Processing" data-form-field="pref_info" value="second"></td>
−
<td><input type="radio" name="pref_info" data-form-field="pref_info" value="third"></td>
+
<td><input type="radio" name="Track Preference: Information Processing" data-form-field="pref_info" value="third"></td>
−
<td><input type="radio" name="pref_info" data-form-field="pref_info" value="neutral"></td>
+
<td><input type="radio" name="Track Preference: Information Processing" data-form-field="pref_info" value="neutral"></td>
−
<td><input type="radio" name="pref_info" data-form-field="pref_info" value="avoid"></td>
+
<td><input type="radio" name="Track Preference: Information Processing" data-form-field="pref_info" value="avoid"></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
 
<th>Manufacturing</th>
 
<th>Manufacturing</th>
−
<td><input type="radio" name="pref_manufacturing" data-form-field="pref_manufacturing" value="first"></td>
+
<td><input type="radio" name="Track Preference: Manufacturing" data-form-field="pref_manufacturing" value="first"></td>
−
<td><input type="radio" name="pref_manufacturing" data-form-field="pref_manufacturing" value="second"></td>
+
<td><input type="radio" name="Track Preference: Manufacturing" data-form-field="pref_manufacturing" value="second"></td>
−
<td><input type="radio" name="pref_manufacturing" data-form-field="pref_manufacturing" value="third"></td>
+
<td><input type="radio" name="Track Preference: Manufacturing" data-form-field="pref_manufacturing" value="third"></td>
−
<td><input type="radio" name="pref_manufacturing" data-form-field="pref_manufacturing" value="neutral"></td>
+
<td><input type="radio" name="Track Preference: Manufacturing" data-form-field="pref_manufacturing" value="neutral"></td>
−
<td><input type="radio" name="pref_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>
−
<td><input type="radio" name="pref_measurement" data-form-field="pref_measurement" value="first"></td>
+
<td><input type="radio" name="Track Preference: Measurement" data-form-field="pref_measurement" value="first"></td>
−
<td><input type="radio" name="pref_measurement" data-form-field="pref_measurement" value="second"></td>
+
<td><input type="radio" name="Track Preference: Measurement" data-form-field="pref_measurement" value="second"></td>
−
<td><input type="radio" name="pref_measurement" data-form-field="pref_measurement" value="third"></td>
+
<td><input type="radio" name="Track Preference: Measurement" data-form-field="pref_measurement" value="third"></td>
−
<td><input type="radio" name="pref_measurement" data-form-field="pref_measurement" value="neutral"></td>
+
<td><input type="radio" name="Track Preference: Measurement" data-form-field="pref_measurement" value="neutral"></td>
−
<td><input type="radio" name="pref_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>
−
<td><input type="radio" name="pref_newapplication" data-form-field="pref_newapplication" value="first"></td>
+
<td><input type="radio" name="Track Preference: New Application" data-form-field="pref_newapplication" value="first"></td>
−
<td><input type="radio" name="pref_newapplication" data-form-field="pref_newapplication" value="second"></td>
+
<td><input type="radio" name="Track Preference: New Application" data-form-field="pref_newapplication" value="second"></td>
−
<td><input type="radio" name="pref_newapplication" data-form-field="pref_newapplication" value="third"></td>
+
<td><input type="radio" name="Track Preference: New Application" data-form-field="pref_newapplication" value="third"></td>
−
<td><input type="radio" name="pref_newapplication" 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="pref_newapplication" 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>
 
<tr>
 
<tr>
 
<th>Software</th>
 
<th>Software</th>
−
<td><input type="radio" name="pref_software" data-form-field="pref_software" value="first"></td>
+
<td><input type="radio" name="Track Preference: Software" data-form-field="pref_software" value="first"></td>
−
<td><input type="radio" name="pref_software" data-form-field="pref_software" value="second"></td>
+
<td><input type="radio" name="Track Preference: Software" data-form-field="pref_software" value="second"></td>
−
<td><input type="radio" name="pref_software" data-form-field="pref_software" value="third"></td>
+
<td><input type="radio" name="Track Preference: Software" data-form-field="pref_software" value="third"></td>
−
<td><input type="radio" name="pref_software" data-form-field="pref_software" value="neutral"></td>
+
<td><input type="radio" name="Track Preference: Software" data-form-field="pref_software" value="neutral"></td>
−
<td><input type="radio" name="pref_software" data-form-field="pref_software" value="avoid"></td>
+
<td><input type="radio" name="Track Preference: Software" data-form-field="pref_software" value="avoid"></td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
 
<th>Therapeutics</th>
 
<th>Therapeutics</th>
−
<td><input type="radio" name="pref_therapeutics" data-form-field="pref_therapeutics" value="first"></td>
+
<td><input type="radio" name="Track Preference: 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="Track Preference: 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="Track Preference: 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="Track Preference: 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="Track Preference: Therapeutics" data-form-field="pref_therapeutics" value="avoid"></td>
 
</tr>
 
</tr>
 
</table>
 
</table>
−
 
 
</fieldset>
 
</fieldset>
  
  
 
<br />
 
<br />
−
<!--<fieldset style="text-align: center; width: 50%; margin-left: auto; margin-right: auto;">-->
 
 
<div class="highlightBoxB" style="border: 2px solid green; width: 40%; float: none; margin-left: auto; margin-right: auto;">
 
<div class="highlightBoxB" style="border: 2px solid green; width: 40%; float: none; margin-left: auto; margin-right: auto;">
 
<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;">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>
 
<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>
−
<!--</fieldset>-->
 
−
 
−
<fieldset class="admins_only">
 
−
<legend>Visible Only to iGEM HQ</legend>
 
−
 
−
<p>How much do we like this judge?
 
−
<select name="admin_like" id="admin_like" data-form-field="admin_like">
 
−
<option value="5">5</option>
 
−
<option value="4">4</option>
 
−
<option value="3">3</option>
 
−
<option value="2">2</option>
 
−
<option value="1">1</option>
 
−
</select>
 
−
</p>
 
−
 
−
<p>How much do we want this person to judge?
 
−
<select name="admin_want" id="admin_want" data-form-field="admin_want">
 
−
<option value="5">5</option>
 
−
<option value="4">4</option>
 
−
<option value="3">3</option>
 
−
<option value="2">2</option>
 
−
<option value="1">1</option>
 
−
</select>
 
−
</p>
 
−
 
−
<p>Calculation of how much work they did before the Jamboree: <input type="text" size="40" name="admin_work" id="admin_work" data-form-field="admin_work"></p>
 
−
 
−
<p>Relative score of judging performance: <input type="text" size="40" name="admin_score" id="admin_score" data-form-field="admin_score"></p>
 
−
 
−
<p>Notes on this judge:</p>
 
−
<textarea rows="3" name="admin_notes" id="admin_notes" data-form-field="admin_notes"></textarea>
 
−
 
−
</fieldset>
 
−
 
−
</html>{{HTML/Temp/FormsAdmin}}<html>
 
  
 
</DIV>
 
</DIV>
Line 496: Line 503:
 
}
 
}
  
 +
//document.ready -- get team list to fill the conflict-of-interest selectors,
 +
//and misc setup stuff
 
$(document).ready(function(event) {
 
$(document).ready(function(event) {
 
$("#modes").addClass('admins_only');
 
$("#modes").addClass('admins_only');
Line 501: Line 510:
 
$("#team_select_select").hide();
 
$("#team_select_select").hide();
  
−
$("[data-form-field=jamboree]").change(function() {
+
$("[data-form-field=jamboree]").change(function() {
−
if ($(this).val() == "yes") {
+
if ($(this).val() == "yes") {
−
$("[data-form-field^=available_]").val("yes").trigger("change");
+
$("[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({
 
jQuery.ajax({
 
url: "https://igem.org/aj/team_list.cgi",
 
url: "https://igem.org/aj/team_list.cgi",

Latest revision as of 17:50, 9 August 2016


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!

We need judges who understand iGEM, and 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.

*** The judging applications have closed for 2016. Any applications received after July 15th 2016 may be considered for iGEM 2017.***

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: Instructor judges will receive a 50% discount on their Jamboree attendance 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!

Please email kim [AT] igem [DOT] org if you have questions!

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 as a...

Judge:      Instructor / PI:      Advisor:      Student:      Volunteer:
Information for Jamboree

Please complete this section as well as you can. You will be asked to check or update this information prior to the Jamboree.

Sweatshirt Size:

Dietary restrictions:

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

Are you available to attend the entire Giant Jamboree (October 27-31, 2016, in Boston)?

If not, please indicate which days/times you are available to attend.

Thu Oct 27, Evening Fri Oct 28, Morning Fri Oct 28, Evening Sat Oct 29, Morning Sat Oct 29, Evening Sun Oct 30, Morning Sun Oct 30, Evening Mon Oct 31, Morning








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.

Conflicts of Interest

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
  • If you mentored or advised the team informally

These situations could lead to a conflict of interest. iGEM takes conflicts of interests very seriously. Judges are not permitted to judge 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.

Please tell us about your conflicts of interest here.

Team Affiliations:
Please select any teams you are officially affiliated with (i.e. you are listed on the team roster as a PI, Instructor, or Advisor).

Conflicts of Interest:
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.)

To select multiple teams, use Ctrl-click or Cmd-click.

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.

Did you apply to judge last year? View your answers from last year.

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?