Difference between revisions of "Judging/Apply"

m
 
(38 intermediate revisions by 4 users not shown)
Line 19: Line 19:
 
</script>
 
</script>
  
<link rel="stylesheet" type="text/css" href="https://igem.org/Template:CSS/General_Form_Styling?action=raw&ctype=text/css" />
+
<link rel="stylesheet" type="text/css" href="https://igem.org/wiki/index.php?title=HQ:Forms.css&action=raw&ctype=text/css" />
<script src="https://igem.org/Template:JS/Judging_Form?action=raw&ctype=text/javascript"></script>
+
<script src="https://igem.org/wiki/index.php?title=HQ:Judging_Form.js&action=raw&ctype=text/javascript"></script>
  
  
Line 35: Line 35:
 
</div>
 
</div>
 
</noscript>
 
</noscript>
 
  
  
 
<div class="column full_size">
 
<div class="column full_size">
<div class="highlight gray">
+
<h1>iGEM 2017 Judging Applications now closed </h1>
<H3> NOTE: This page is under development </h3>
+
</div>
+
 
</div>
 
</div>
  
 
+
<div class="column half_size">
<div class="column full_size">
+
<h1>Apply to be a Judge </h1>
+
 
+
 
<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>
  
<p>Lastly, I'm afraid that if you are a student on a 2017 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>
 
  
<h4> Please email kim [AT] igem [DOT] org if you have questions!</h4>
+
<h5> Please email kim [AT] igem [DOT] org if you have questions!</h5>
  
 
</div>
 
</div>
  
<div class="clear extra_space"></div>
 
  
 
<div class="column half_size">
 
<div class="column half_size">
 +
<p>If you have colleagues who you think should apply, please feel free to direct them to this form.</p>
 +
 +
 
<p>We're looking for:</p>
 
<p>We're looking for:</p>
 
<ul>
 
<ul>
Line 68: Line 63:
 
<li>iGEM alumni who want to stay involved</li>
 
<li>iGEM alumni who want to stay involved</li>
 
</ul>
 
</ul>
<p>If you have colleagues who you think should apply, please feel free to direct them to this form.</p>
 
</div>
 
  
 +
<p>If you are a student on a 2017 iGEM team, you can't apply to be a judge this year. But you can apply when you graduate and become an iGEM alum!</p>
  
<div class="column half_size">
 
<p> NEW: Instructor judges will receive a 50% discount on their Jamboree attendance fee!</p>
 
 
</div>
 
</div>
  
 +
 +
<div class="clear extra_space"></div>
 +
 +
 +
<div class="column full_size">
 +
<div class="highlight gray">
 +
<h3> <font color="red"> The iGEM 2017 Judging Roster has been finalized. The judging application form is now closed. This page will no longer be monitored for the rest of the 2017 season.</font>
 +
</h3>
 +
 +
<p>NEW: Instructor judges will receive a 50% discount on their Jamboree attendance fee!</p>
 +
</div>
 +
</div>
  
 
<div class="clear extra_space"></div>
 
<div class="clear extra_space"></div>
Line 98: Line 102:
 
<div class="line_divider"></div>
 
<div class="line_divider"></div>
 
<div class="clear extra_space"></div>
 
<div class="clear extra_space"></div>
 +
 +
 +
<div class="column full_size">
 +
 +
<div id='aj_form_errors'> </div>
 +
 +
</div>
  
  
Line 104: Line 115:
 
<p>You can <a href="#" id="popwin_unsubmit">unsubmit the form</a> if you wish to make further edits.</p>
 
<p>You can <a href="#" id="popwin_unsubmit">unsubmit the form</a> if you wish to make further edits.</p>
 
<p><a href="#" id="popwin_dismiss">Click here to dismiss this message</a></p>
 
<p><a href="#" id="popwin_dismiss">Click here to dismiss this message</a></p>
 +
</div>
 
</div>
 
</div>
  
 +
 +
 +
<div class="column full_size">
 +
<!---
 
<div id="formtitlemodewrapper">
 
<div id="formtitlemodewrapper">
 
<h2 id="toptitle">
 
<h2 id="toptitle">
Line 116: Line 132:
 
<option id="no_team_selected" value="">Choose team...</option>
 
<option id="no_team_selected" value="">Choose team...</option>
 
</select>
 
</select>
 +
 +
-->
 +
  
  
Line 141: Line 160:
  
 
<fieldset>  
 
<fieldset>  
<h2> <span class="section_numbers"> 1 </span> General Information </h2>
+
<h2> 1.- General Information </h2>
  
  
Line 148: Line 167:
  
  
<p class="question"> Username: <span id="user_name_display">-</span>)</p>
+
<p class="question"> Username: <span id="user_name_display">-</span></p>
  
  
Line 158: Line 177:
 
<p class="question">2. Age
 
<p class="question">2. Age
 
<input type="text" size="40" name="Age" id="age" class="validate-on-change" data-form-field="age" data-validate-as="age" placeholder="Age">
 
<input type="text" size="40" name="Age" id="age" class="validate-on-change" data-form-field="age" data-validate-as="age" placeholder="Age">
 +
</p>
 +
<p>
 +
Note: To be eligible to become an iGEM judge, you must be at least 23 on the 31st of March 2017. Any applicants who do no meet this criteria will be evaluated on a case by case basis.
 
</p>
 
</p>
  
Line 166: Line 188:
 
<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" placeholder="Please describe"></li>
 
</ul>
 
</ul>
  
Line 182: Line 204:
 
<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" placeholder="Please describe"></li>
 
</ul>
 
</ul>
  
Line 193: Line 215:
 
<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" placeholder="Please describe"></li>
 
</ul>
 
</ul>
  
Line 210: Line 232:
  
 
<p class="question">8. Number of years of iGEM experience as a:</p>
 
<p class="question">8. Number of years of iGEM experience as a:</p>
<p> <span class="align_dropdowns">Judge: </span>
+
 
 +
 
 +
<p class="dropdown_question"> <span class="align_dropdowns">Judge: </span>
 
<select name="Years Experience as a Judge" data-form-field="years_judge">
 
<select name="Years Experience as a Judge" data-form-field="years_judge">
 
<option value="0">0</option>
 
<option value="0">0</option>
Line 223: Line 247:
  
  
<p><span class="align_dropdowns">Instructor / PI: </span>
+
<p class="dropdown_question"> <span class="align_dropdowns">Instructor / PI: </span>
 
<select name="Years Experience as an Instructor/PI" data-form-field="years_instructor" >
 
<select name="Years Experience as an Instructor/PI" data-form-field="years_instructor" >
 
<option value="0">0</option>
 
<option value="0">0</option>
Line 235: Line 259:
 
</p>
 
</p>
  
<p><span class="align_dropdowns">Advisor: </span>
+
<p class="dropdown_question"> <span class="align_dropdowns">Advisor: </span>
 
<select name="Years Experience as an Advisor" data-form-field="years_advisor">
 
<select name="Years Experience as an Advisor" data-form-field="years_advisor">
 
<option value="0">0</option>
 
<option value="0">0</option>
Line 248: Line 272:
  
  
<p><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" >
 
<option value="0">0</option>
 
<option value="0">0</option>
Line 260: Line 284:
 
</p>
 
</p>
  
<p><span class="align_dropdowns">Volunteer: </span>
+
<p class="dropdown_question"> <span class="align_dropdowns">Volunteer: </span>
 
<select name="Years Experience as a Volunteer" data-form-field="years_volunteer" >
 
<select name="Years Experience as a Volunteer" data-form-field="years_volunteer" >
 
<option value="0">0</option>
 
<option value="0">0</option>
Line 284: Line 308:
  
 
<fieldset>
 
<fieldset>
<h2><span class="section_numbers">2</span> Jamboree Information </h2>
+
<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 300: Line 324:
  
  
<p class="question">2. Dietary restrictions <span class="additional_question_text"> If you have other dietary restrictions, please <a href="https://igem.org/Contact">contact iGEM HQ</a></span> </p>
+
<p class="question">2. Dietary restrictions. <span class="additional_question_text"> If you have other dietary restrictions, please <a href="https://igem.org/Contact">contact iGEM HQ</a></span> </p>
 
<ul>
 
<ul>
 
<li><label><input type="radio" data-validation="optional" name="Vegetarian" id="vegetarian" data-form-field="vegetarian"> Vegetarian</label></li>
 
<li><label><input type="radio" data-validation="optional" name="Vegetarian" id="vegetarian" data-form-field="vegetarian"> Vegetarian</label></li>
Line 325: Line 349:
 
<th>Thursday <br> November 09</th>
 
<th>Thursday <br> November 09</th>
 
<td></td>
 
<td></td>
<td><label><input type="radio" name="Availability Thu Oct 27, Evening" data-form-field="available_thu_eve" value="yes"> Yes</label><br />
+
<td>
 +
<label><input type="radio" name="Availability Thu Oct 27, Evening" data-form-field="available_thu_eve" value="yes"> Yes</label>   <br /><br>
 
<label><input type="radio" name="Availability Thu Oct 27, Evening" data-form-field="available_thu_eve" value="no"> No</label>
 
<label><input type="radio" name="Availability Thu Oct 27, Evening" data-form-field="available_thu_eve" value="no"> No</label>
 
</td>
 
</td>
Line 333: Line 358:
 
<tr>
 
<tr>
 
<th>Friday <br> November 10</th>
 
<th>Friday <br> November 10</th>
<td><label><input type="radio" name="Availability Fri Oct 28, Morning" data-form-field="available_fri_morn" value="yes"> Yes</label><br />
+
<td><label><input type="radio" name="Availability Fri Oct 28, Morning" data-form-field="available_fri_morn" value="yes"> Yes</label><br /><br>
 
<label><input type="radio" name="Availability Fri Oct 28, Morning" data-form-field="available_fri_morn" value="no"> No</label>
 
<label><input type="radio" name="Availability Fri Oct 28, Morning" data-form-field="available_fri_morn" value="no"> No</label>
 
</td>
 
</td>
<td><label><input type="radio" name="Availability Fri Oct 28, Evening" data-form-field="available_fri_eve" value="yes"> Yes</label><br />
+
<td><label><input type="radio" name="Availability Fri Oct 28, Evening" data-form-field="available_fri_eve" value="yes"> Yes</label><br /><br>
 
<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>
Line 348: Line 373:
 
<th>Saturday <br> November 11</th>
 
<th>Saturday <br> November 11</th>
  
<td><label><input type="radio" name="Availability 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 /><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="Availability 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 /><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>
Line 359: Line 384:
 
<tr>
 
<tr>
 
<th>Sunday <br> November 12</th>
 
<th>Sunday <br> November 12</th>
<td><label><input type="radio" name="Availability 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 /><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="Availability 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 /><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>
Line 369: Line 394:
 
<tr>
 
<tr>
 
<th>Monday <br> November 13</th>
 
<th>Monday <br> November 13</th>
<td><label><input type="radio" name="Availability 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 /><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 382: Line 407:
  
 
<div class="column half_size">
 
<div class="column half_size">
<div class="highlight">
+
<div class="highlight note">
 
<h3> Note</h3>
 
<h3> Note</h3>
<p>If you are selected as a judge, you <b>MUST</b> attend the iGEM 2017 <a href="https://2017.igem.org/Giant_Jamboree">Giant Jamboree</a> in Boston (October 27-31). <b>iGEM currently cannot provide travel funding</b> for judges to attend.</p>
+
<p>If you are selected as a judge, you <b>MUST</b> attend the iGEM 2017 <a href="https://2017.igem.org/Giant_Jamboree">Giant Jamboree</a> in Boston (November 9-13). <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 2017 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 registered as a Primary PI, Secondary PI, Instructor, or Advisor for a 2017 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 2017 iGEM team, <b>your Jamboree attendance fee will be waived</b>.</p>
 
<p>If you are not on the roster of a 2017 iGEM team, <b>your Jamboree attendance fee will be waived</b>.</p>
Line 403: Line 428:
  
 
<fieldset>
 
<fieldset>
<h2><span class="section_numbers">3</span> Conflicts of Interest </h2>
+
<h2> 3.- Conflicts of Interest </h2>
  
<p>There are many possible reasons why you might be unable to judge some teams impartially. For example:</p>
+
<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>
<ul style="list-style: disc outside none;">
+
These situations could lead to a conflict of interest and iGEM takes conflicts of interests very seriously. Judges are not permitted to evaluate teams for which they have a conflict of interest. If you are a PI or instructor, your first responsibility is to your team, and we will schedule your judging assignment so that you are able to attend your team's presentation.</p>
<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>
+
<br>
+
  
 +
<br><br>
  
<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>To select multiple teams, use <i><b> Ctrl-click or Cmd-click</i></b>. Don't recognize a team name? Look it up in the <a target="_blank" href="https://igem.org/Team_List">Team List</a>.</p>
<p>Please tell us about your conflicts of interest here.</p>
+
  
<table id="conflicts_holder">
+
 
<tr>
+
<div class="column half_size">
<td>
+
<p class="question">1. Team Affiliations:</p>
<p><span class="question">Team Affiliations:</span><br>
+
<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>
Please select any teams you are officially affiliated with (i.e. you are listed on the team roster as a PI, Instructor, or Advisor).</p>
+
<br><br>
</td>
+
<td>
+
<p><span class="question">Conflicts of Interest:</span> <br>
+
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>
+
</tr>
+
<tr>
+
<td>
+
 
<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 2017 team affiliations</option>
 
<option class='none_selected'>I have no 2017 team affiliations</option>
 
</select>
 
</select>
</td>
+
 
<td>
+
</div>
 +
 
 +
 
 +
 
 +
<div class="column half_size">
 +
<p class="question">2. Conflicts of Interest:</p>
 +
<p> Please select any teams for which you have a conflict of interest for another reason. (For example, a team that you mentored informally, or a team from the university where you were an undergrad student.)</p><br>
 +
 
 
<select multiple class="teamselector-multiple" size="20" name="Team conflicts of interest" id="team_conflicts" data-form-field="team_conflicts">
 
<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 2017 team conflicts of interest</option>
 
<option class='none_selected'>I have no 2017 team conflicts of interest</option>
 
</select>
 
</select>
</td>
 
</tr>
 
</table>
 
  
<div class="highlightBoxB">
 
<p>To select multiple teams, use <i><b> Ctrl-click or Cmd-click</i></b>.</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>
  
<p class="question">If you have any other conflicts of interest that are not indicated above, please describe them:</p>
+
 
 +
<div class="clear extra_space"></div>
 +
 
 +
<p class="question">3. If you have any other conflicts of interest that are not indicated above, please describe them:</p>
 
<textarea rows="3" data-validation="optional" name="Other conflicts of interest" id="other_conflicts" data-form-field="other_conflicts" maxlength="500"></textarea>
 
<textarea rows="3" data-validation="optional" name="Other conflicts of interest" id="other_conflicts" data-form-field="other_conflicts" maxlength="500"></textarea>
 
</fieldset>
 
</fieldset>
 +
 +
 +
 +
 +
<!-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 +
 +
MOTIVATION
 +
 +
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------->
 +
 +
  
  
 
<fieldset>  
 
<fieldset>  
  
<h2><span class="section_numbers">4</span>  Motivation</h2>
+
<h2>4.- Motivation</h2>
 
<p>Please answer these questions in detail, especially if this is your first IGEM judging application.</p>
 
<p>Please answer these questions in detail, especially if this is your first IGEM judging application.</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 460: Line 487:
  
  
<p class="question">Why do you want to be a judge in iGEM?</p>
+
<p class="question">1. Why do you want to be a judge in iGEM?</p>
 
<textarea rows="5" name="Why do you want to be a judge" id="why_want_to_judge" data-form-field="why_want_to_judge" maxlength="2000"></textarea>
 
<textarea rows="5" name="Why do you want to be a judge" id="why_want_to_judge" data-form-field="why_want_to_judge" maxlength="2000"></textarea>
  
<p class="question">What professional experience do you have that's relevant to iGEM (e.g., synthetic biology, hardware, software, human practices)?</p>
+
<p class="question">2. What professional experience do you have that's relevant to iGEM (e.g., synthetic biology, hardware, software, human practices)?</p>
 
<textarea rows="5" name="What professional experience do you have" id="professional_experience" data-form-field="professional_experience" maxlength="2000"></textarea>
 
<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, Science Olympiad)</p>
+
<p class="question">3. 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">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/2015/d/d7/IGEM2015_Judging_Handbook.pdf" target="_blank">2015 Judging Handbook Part 1</a>. The 2017 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 2017 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">
Line 486: Line 513:
  
 
<fieldset>  
 
<fieldset>  
<h2><span class="section_numbers">5</span> Track Preferences </h2>
+
<h2>5.- Track Preferences </h2>
  
 
<p>iGEM teams compete in several "tracks", based on the topics of their projects. Please see <a href="https://2017.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://2017.igem.org/Tracks" target="_blank">the Track page</a> for more information on each track.</p>
Line 632: Line 659:
  
  
<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>
  
  
Line 669: Line 696:
 
$("#full_name_display").text(data.full_name);
 
$("#full_name_display").text(data.full_name);
 
$("#user_name_display").text(data.user_name);
 
$("#user_name_display").text(data.user_name);
$("#last_years_application_link").attr("href", "https://2015.igem.org/Judging/Application_Form?author=" + data.user_name + "#formbody");
+
$("#last_years_application_link").attr("href", "https://2016.igem.org/Judging/Apply?author=" + data.user_name + "#formbody");
 
}
 
}
  

Latest revision as of 19:13, 3 August 2017

MENU


You have JavaScript disabled.

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

iGEM 2017 Judging Applications now closed

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.

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

If you have colleagues who you think should apply, please feel free to direct them to this form.

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 are a student on a 2017 iGEM team, you can't apply to be a judge this year. But you can apply when you graduate and become an iGEM alum!

The iGEM 2017 Judging Roster has been finalized. The judging application form is now closed. This page will no longer be monitored for the rest of the 2017 season.

NEW: Instructor judges will receive a 50% discount on their Jamboree attendance fee!

Judge Application Form

This form has been submitted.

You can unsubmit the form if you wish to make further edits.

Click here to dismiss this message

1.- General Information

Full name: -

Username: -

1. Email

2. Age

Note: To be eligible to become an iGEM judge, you must be at least 23 on the 31st of March 2017. Any applicants who do no meet this criteria will be evaluated on a case by case basis.

3. Gender

4. Institution

5. Institution type

6. Position

7. Region Where you currently live/work :

8. Number of years of iGEM experience as a:

2.- Jamboree Information

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

1. Sweatshirt Size:

2. Dietary restrictions. If you have other dietary restrictions, please contact iGEM HQ

3. Are you available to attend the entire Giant Jamboree (November 9 - 11 2017, in Boston)?

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

Day Morning Evening
Thursday
November 09


Friday
November 10




Saturday
November 11




Sunday
November 12




Monday
November 13


Note

If you are selected as a judge, you MUST attend the iGEM 2017 Giant Jamboree in Boston (November 9-13). 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 2017 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 2017 iGEM team, your Jamboree attendance fee will be waived.

3.- 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 or if you mentored or advised the team informally
These situations could lead to a conflict of interest and iGEM takes conflicts of interests very seriously. Judges are not permitted to evaluate teams for which they have a conflict of interest. If you are a PI or instructor, your first responsibility is to your team, and we will schedule your judging assignment so that you are able to attend your team's presentation.



To select multiple teams, use Ctrl-click or Cmd-click. Don't recognize a team name? Look it up in the Team List.

1. 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).



2. 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.)


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

4.- 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.

1. Why do you want to be a judge in iGEM?

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

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

4. 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 2017 Judging Handbook will be available later this year.)

5.- 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

Thank you!

Thank you for filling out this form. We look forward to picking a strong judging team for 2017!

Finished?

Need to make changes?