Difference between revisions of "Judging/Apply"

Line 1: Line 1:
−
{{Main2019}}
+
{{Main2020}}
 
<html>
 
<html>
  
−
 
−
 
  
 
<noscript>
 
<noscript>
Line 11: Line 9:
 
</div>
 
</div>
 
</noscript>
 
</noscript>
 +
  
  
 
<div class="column full_size">
 
<div class="column full_size">
−
<h1>iGEM 2019 Judging Applications</h1>
+
<h1>iGEM 2020 Judging Applications</h1>
  
 
<p>
 
<p>
 
<span class="on_page"></span><b>On this page</b>  
 
<span class="on_page"></span><b>On this page</b>  
 
you will find information on:
 
you will find information on:
−
<a href="#jamboree"> Judging at the Giant Jamboree</a>,  
+
<a href="#jamboree"> Judging at the Giant Jamboree</a>, 
 +
<a href="#why"> Why Should You be an iGEM Judge?</a>,
 
<a href="#who"> Who Should Apply to be a Judge?</a>,  
 
<a href="#who"> Who Should Apply to be a Judge?</a>,  
−
<a href="#why"> Why Should You be an iGEM Judge?</a>,
+
<a href="#expectations">Expectations for Judges</a>,  
−
<a href="#process"> Application Process</a>
+
<a href="#process"> Application Process</a>,
−
<a href="#benefits"> Judge Benefits</a>, and
+
<a href="#goals"> Recruitment Goals</a>, and  
 
the <a href="#application">Judge Application</a>
 
the <a href="#application">Judge Application</a>
 
</p>
 
</p>
  
  
−
<br><br>
 
  
−
<div class="highlight post_item gray">
 
−
<div class="details ">
 
−
<span class="icon announcement"></span>
 
−
<div class="title"> The iGEM 2019 Judging Application is Closed </div>
 
−
</div>
 
−
<p>Judge applications for the 2019 Giant Jamboree are now closed. Thank you to everyone who applied!</p>
 
−
</div>
 
−
</div>
 
  
  
 +
<div class="clear extra_space" id="jamboree"></div>
  
−
<div class="clear extra_space" id="jamboree"></div>
+
<h3>Judging at the Giant Jamboree</h3>
 +
<p>
 +
Judging in iGEM is a fun, rewarding experience and requires commitment! Through the judging process, our judges will evaluate, celebrate, and help guide the next generation of synthetic biologists. Judges help the entire iGEM community celebrate the hard work and achievements of our iGEM teams.
 +
<br><br>
 +
We need judges — both experienced and new — who understand and value iGEM. Many of our judges come back year after year, and we gladly welcome new judges to apply as well.
 +
<br><br>
 +
Great news: no jet-lag this year! The Giant Jamboree is entirely virtual. Travel will not be a constraint for judges for the first time in iGEM’s history. We are hopeful that this will allow us to recruit an even more diverse panel of judges from our global iGEM community.
 +
<br><br>
 +
iGEM teams work incredibly hard on their projects, so we need judges who are also committed. Judges are expected to dedicate their time and effort to thoroughly evaluate the projects of their assigned teams. The judging process also includes attending virtual training sessions prior to the Jamboree, attending various sessions during the Giant Jamboree to interact with and evaluate your assigned teams, and providing written feedback to your assigned teams.
 +
</p>
  
−
<div class="column full_size">
+
<div class="clear extra_space"></div>
−
<h3>Judging at the Giant Jamboree</h3>
+
−
<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 and who are willing to take part in the whole process of iGEM judging. If you can spend time learning about the judging process during the summer, evaluating team wikis the week before the Jamboree, and attending the Jamboree from October 31-November 4, 2019, we would love to have you on board!</p>
+
  
−
<p>We need judges — both experienced and new — who really understand iGEM. We are aiming to recruit a judging panel that reflects our teams’ experience, so if you have previous iGEM experience we want you to apply!</p>
+
<img src="https://static.igem.org/mediawiki/2020/f/fa/Judging_judge_application.jpg">
−
<p>As we approach the Giant Jamboree, we will provide educational resources to help judges learn how to evaluate teams (or provide a refresher, for those who have judged before), and we will help you get up to speed if you are selected.</p>
+
−
 
+
<p class="image_caption">Judges at the 2019 Giant Jamboree</p>
−
 
+
−
 
+
−
 
+
−
<div class="clear extra_space"></div>
+
−
 
+
−
<img src="https://static.igem.org/mediawiki/2019/f/f3/Judging_application_1.jpg">
+
−
<p class="image_caption">Judges at a team's poster during the 2018 Giant Jamboree</p>
+
 
</div>
 
</div>
−
 
+
−
<div class="clear extra_space"></div>
+
<!--
 +
<div class="clear double_extra_space"></div>
 
<div class="line_divider"></div>
 
<div class="line_divider"></div>
−
<div class="clear extra_space" id="who"></div>
+
<div class="clear double_extra_space"id="experience"></div>
 +
 +
<div class="column full_size">
 +
<h3>The Judging Experience</h3>
 +
<p> Lorem ipsum</p>
 +
</div>
 +
-->
  
−
<div class="column third_size">
+
<div class="clear double_extra_space"></div>
 +
<div class="line_divider"></div>
 +
<div class="clear extra_space" id="why"></div>
  
−
<img src="https://static.igem.org/mediawiki/2019/2/25/Judging_application_2.jpg">
+
<div class="column third_size">
 +
<img src="https://static.igem.org/mediawiki/2020/b/b6/Judging_judge_poster.jpg">
 +
</div>
 
 
 +
<div class="column two_thirds_size">
  
−
</div>
+
<h3>Why Should You be an iGEM Judge?</h3>
 +
<p>Judging at the annual iGEM Giant Jamboree is an incredibly fulfilling and worthwhile experience for all judges, whether you're returning as a veteran judge or are a new judge this year. Some of the benefits include:</p>  
 
 
−
<div class="column two_thirds_size">
+
<ul>
−
<h3>Who Should Apply to be a Judge? </h3>
+
<li><b>Contributing to the iGEM Community</b> By volunteering to judge at the Giant Jamboree, you will contribute to one of the most meaningful opportunities that these students experience in synthetic biology. Providing constructive feedback to these dedicated students can be life changing for them as they continue through their academic career and beyond.</li>
−
<p>
+
−
We're looking for:</p>
+
<li><b>Networking:</b> Much like the iGEM teams, you'll have the chance to connect with people from around the globe, to expand your synthetic biology community, and to form new collaborations beyond the Giant Jamboree. You will meet fellow judges, students, and other professionals from around the world and different walks of life.</li>
−
<ul>
+
−
<li>iGEM alumni who want to stay involved, including professionals, graduate students, and post-docs</li>
+
<li><b>Learning About New Technology:</b> You will learn about the latest cutting edge work being done in synthetic biology from student teams who are driven to excel and who test the boundaries of synthetic biology through their projects.</li>
−
<li>iGEM PIs, instructors, and advisors, both current and past</li>
+
−
<li>People who have judged iGEM in the past</li>
+
−
<li>Professionals in the synthetic biology, biotechnology, and engineering industries</li>
+
−
<li>People who have experience in complimentary areas, such as the humanities, art and design, and software</li>
+
−
</ul>
+
  
−
<p>If you have colleagues who you think should apply, please feel free to direct them to this form.</p>
+
<li><b>Attending for Free:</b> Judges will not pay any registration fee for the Giant Jamboree!</li>
 +
</ul>
  
−
<p>If you are a student on a 2019 iGEM team, you can't apply to be a judge this year. But you can apply when you graduate and become an iGEM alum!</p>
 
 
</div>
 
</div>
−
 
−
<div class="clear extra_space" id="why"></div>
 
−
 
−
<div class="column third_size">
 
−
 
−
<img src="https://static.igem.org/mediawiki/2019/9/91/Judging_application_3.jpg">
 
 
 
−
 
+
<div class="clear extra_space" id="who"></div>
 +
 +
<div class="column third_size">
 +
<img src="https://static.igem.org/mediawiki/2020/4/47/Judging_judge_application2.jpg">
 
</div>
 
</div>
 
 
−
<div class="column two_thirds_size">
+
<div class="column two_thirds_size">
 +
<h3>Who Should Apply to be a Judge? </h3>
 +
<p>We're looking for:</p>
 +
<ul>
 +
<li>iGEM PIs, instructors, and advisors, from both current and past iGEM teams</li>
 +
<li>People who have judged iGEM previously</li>
 +
<li>iGEM alumni who want to stay involved, including professionals, graduate students, and post-docs</li>
 +
<li>Professionals in the synthetic biology, biotechnology, and engineering industries</li>
 +
<li>People who have experience in complementary areas, such as the humanities, art and design, and software</li>
 +
</ul>
  
−
<h3>Why Should You be an iGEM Judge?</h3>
+
<p>
−
<p>Judging at the annual iGEM Giant Jamboree is an incredibly fulfilling and worthwhile experience for all judges, whether you're returning as a veteran judge or are a new judge this year. Some of the benefits include:
+
If you have colleagues who you think should apply, please feel free to direct them to this form.
−
<ul>
+
While previous iGEM experience is preferred, we gladly welcome new applicants - particularly those that demonstrate a strong knowledge of and value for iGEM. <br><br>
−
<li><b>Contribute to the iGEM Community:</b> By volunteering to judge at the Giant Jamboree, you will contribute to what will be the most meaningful opportunity that these students experience in synthetic biology. Providing feedback to these dedicated students can be life changing for them as they continue through their academic career and beyond.</li>
+
Applicants must be at least 23 years old as of March 31, 2020, and have completed their undergraduate degree by June 30, 2020, to be considered for the judging panel.<br><br>
−
<li><b>Networking:</b> Much like the iGEM teams, you'll have the chance to connect with people from around the globe, to expand your synthetic biology community, and to form new collaborations beyond the Giant Jamboree. You will meet fellow judges, students, and other professionals from around the world and different walks of life. </li>
+
If you are a student on a 2020 iGEM team, then you can't apply to be a judge this year, but you can apply when you graduate and become an iGEM alum!
−
<li><b>Learn About New Technology:</b> You will learn about the latest cutting edge work being done in synthetic biology from student teams who are driven to excel and who test the boundaries of synthetic biology through their projects.</li>
+
</p>
 +
</div>
  
−
</ul>
+
<div class="clear extra_space"></div>
−
 
+
<div class="line_divider"></div>
−
</div>
+
<div class="clear extra_space" id="expectations"></div>
 +
 +
<div class="column full_size">
 +
<h3>Application Process</h3>
 +
<p>This year, the Giant Jamboree will have an expanded schedule [link once ready] to accommodate a global virtual audience. Most of the judging activities will take place from November 14-16 (Saturday-Monday) and will run across three time zones (EDT [UTC -4], CEST [UTC +2], and CST [UTC +8]). We are looking for judges who are available during one or more of these major time zones to ensure coverage for our teams. We plan to accommodate your personal schedule requirements when assigning you teams to evaluate.</p>
 +
 +
<p>Judges will be assigned 6-9 teams to evaluate. The evaluation process will include reviewing Team Wikis and watching Presentation Videos prior to the Giant Jamboree and attending sessions between November 14-16 during the Giant Jamboree to interact with and evaluate their assigned teams. Judges are also required to provide written feedback for each of their teams in the Judging Ballot provided to them.
 +
<br><br>
 +
Judges will also evaluate the iGEM Finalists (announced on Thursday, November 19) and vote for the winners on Saturday, November 21.
 +
<br><br>
 +
Judges are also invited to attend the Closing and Awards Ceremonies on Sunday, November 22, which will take place between 8am - 12pm EDT.
 +
</p>
 +
</div>
  
 
<div class="clear extra_space"></div>
 
<div class="clear extra_space"></div>
Line 114: Line 134:
 
 
 
 
−
<div class="column full_size">
+
<div class="column full_size">
−
<h3>Application Process</h3>
+
<h3>Application Process</h3>
−
<p>
+
<p>This year we are accepting applications on a rolling basis. We will be evaluating applications twice per month and will contact applicants approximately two weeks after the evaluation period with a status notification, such as 1. invitation to judge, 2. invitation to serve as a reserve judge, 3. invitation to re-apply, or 4. decline for 2020 with an invitation to apply next year. Notifications will be sent twice a month, beginning in July, until our quota is full (expected by the end of September). <b>We encourage you to apply early to increase your chances of being selected!</b></p>
−
This year we are accepting applications on a rolling basis. We will be evaluating applications at the end of each month starting in May and will contact applicants approximately two weeks after the evaluation period. Status notifications (1. invitation to judge, 2. invitation to serve as a reserve judge, 3. invitation to re-apply, or 4. decline for 2019 with an invitation to apply next year) will be sent in the middle of each month, beginning in June, until our quota is full (expected by August). <b>We encourage you to apply early to increase your chances of being selected!</b>  
+
−
<br><br>
+
<p> You can apply to be a judge before knowing if you can fully commit to attending the Giant Jamboree. Applicants who are invited to join the judging panel will be asked to confirm their acceptance and their availability. We can also provide an official invitation letter if you require that to secure permission from your institute to participate as a judge.<br><br>
−
You can apply to be a judge before knowing if you can fully commit to attending the Giant Jamboree. Applicants who are invited to join the judging panel will be asked to confirm their acceptance. We can also provide an official invitation letter if you require that to secure funding and/or permission from your institute to participate as a judge.  
+
Once we have reached our quota of judges, we will close the application and add a notice to this page.<br><br>
−
<br><br>
+
Applications will be anonymized and evaluated by experienced judges who belong to the Judging Corps Committee [link to committee page] and Executive Judging Committee [link to committee page]. If possible, please refrain from using identifying information in the answers to your application questions (Section 4).</p>
−
Once we have reached our quota of judges, we will close the application and add a notice to this page.
+
</div>
−
</p>
+
  
  
−
<div class="column full_size">
+
<div class="clear double_extra_space"></div>
−
<div class="highlight post_item">
+
−
<div class="details">
+
−
<span class="icon note"></span>
+
−
<div class="title">Giant Jamboree Attendance</div>
+
−
</div>
+
−
 
+
−
<p>If you are selected as a judge, you <b>MUST</b> attend the iGEM 2019 <a href="https://2019.igem.org/Giant_Jamboree">Giant Jamboree</a> in Boston (October 31-November 4) <b>in person.</b> We are unable to support remote participation for judges due to the nature of the interactions you will have with the teams throughout the event.
+
−
<br><br>
+
−
If you can only attend a portion of the Jamboree, this may make judging your assigned teams a challenge. We will work with you to try to accommodate your schedule constraints as best as possible, but we may rescind your invitation to judge in favor of another applicant who can attend the entire event. This will be evaluated on a case by case basis.
+
−
</div>
+
−
</div>
+
−
 
+
−
 
+
−
<div class="clear extra_space"></div>
+
 
<div class="line_divider"></div>
 
<div class="line_divider"></div>
−
<div class="clear extra_space" id="benefits"></div>
+
<div class="clear double_extra_space" id="goals"></div>
  
  
−
 
+
<div class="column full_size" >
−
<h3>Judge Benefits</h3>
+
−
<p>
+
−
Instructor judges (current team PIs, instructors, and advisors) will receive a 50% discount on their Jamboree attendance fee.
+
−
<br><br>
+
−
Judges who are not affiliated with a team will receive free Jamboree attendance.
+
−
<br><br>
+
−
We are also excited to offer free childcare for all of our judges throughout the Giant Jamboree!
+
−
<br><br>
+
−
iGEM currently cannot provide travel funding for judges to attend.</p></p>
+
−
 
+
−
<div class="clear extra_space"></div>
+
−
 
+
−
<div class="highlight post_item gray">
+
−
<div class="details ">
+
−
<span class="icon why"></span>
+
−
<div class="title"> Questions?  </div>
+
−
</div>
+
−
<p> Please email <i> traci [AT] igem [DOT] org</i> and/or <i> vinoo [AT] igem [DOT] org</i> if you have questions!</p>
+
−
 
+
−
</div>
+
−
</div>
+
 
 
 +
<h3>Recruitment Goals</h3>
 +
<p>We will be recruiting a diverse judging panel with the following characteristics in mind:</p>
 
 
−
<div class="clear extra_space"></div>
+
<ul>
 +
<li>Gender parity </li>
 +
<li>Regional diversity with time zone coverage</li>
 +
<li>iGEM experience (i.e., past and present team PIs, mentors, and advisors; previous team members; returning judges) </li>
 +
</ul>
 +
 +
<div class="clear extra_space"></div>
 +
 +
 +
<div class="highlight post_item gray">
 +
<div class="details ">
 +
<span class="icon why"></span>
 +
<div class="title"> Questions?  </div>
 +
</div>
 +
<p> Please email <i> traci [AT] igem [DOT] org</i> and/or <i> vinoo [AT] igem [DOT] org</i> if you have questions!</p>
 +
</div>
 +
 +
</div>
  
−
<div class="column full_size" id="application">
 
  
−
<br><br>
+
<div class="clear double_extra_space"></div>
 +
<div class="line_divider"></div>
 +
<div class="clear double_extra_space" id="application"></div>
 +
 
  
 
<!-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 
<!-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Line 187: Line 192:
 
<script type="text/javascript">
 
<script type="text/javascript">
 
var form_info = {};
 
var form_info = {};
−
form_info.name="2019_judge_application";
+
form_info.name="2020_judge_application";
−
form_info.display_title="2019 Judging Application Form";
+
form_info.display_title="2020 Judging Application Form";
 
form_info.default_mode = "edit";
 
form_info.default_mode = "edit";
 
form_info.owner_type = "user";
 
form_info.owner_type = "user";
Line 196: Line 201:
 
admin: ["super_users"]};
 
admin: ["super_users"]};
 
form_info.validate_unspecified_fields = "required";
 
form_info.validate_unspecified_fields = "required";
−
form_info.ajax_URL = "https://2019.igem.org/cgi/forms/form.cgi";
+
form_info.ajax_URL = "https://2020.igem.org/cgi/forms/form.cgi";
 
</script>
 
</script>
  
−
<link rel="stylesheet" type="text/css" href="https://igem.org/wiki/index.php?title=HQ:2019_Forms.css&action=raw&ctype=text/css" />
 
−
<script src="https://igem.org/wiki/index.php?title=HQ:Judging_Form.js&action=raw&ctype=text/javascript"></script>
 
  
 +
  
 +
<style>
 +
/* This wraps the section of questions */
 +
fieldset {
 +
background-color: #f9f9f9;
 +
border: 1px solid #d3d3d3;
 +
border-radius: 5px;
 +
margin: 40px auto;
 +
max-width: 1000px;
 +
padding: 40px;
 +
}
  
 +
/*This styles the title of a section */
 +
legend {
 +
color:#00A19D;
 +
font-size: 16px;
 +
font-weight: bold;
 +
}
  
  
−
<div class="column full_size" style="text-align:center; margin:auto;"><h1> Judge Application Form </h1> </div>
 
−
<div class="clear"></div>
 
−
<div class="line_divider"></div>
 
−
<div class="clear extra_space"></div>
 
  
 +
/*This styles the input text boxes  */
 +
input[type=text] {
 +
border: 1px solid #d3d3d3;
 +
border-radius: 5px;
 +
box-sizing: border-box;
 +
display: inline-block;
 +
margin: 0px;
 +
padding: 7px 20px;
 +
width:80%;
 +
}
  
−
<div class="column full_size">
+
.forty_percent {
 +
width:40% !important;
 +
}
  
−
<div id='aj_form_errors'> </div>
+
.hundred_percent {
 +
width:100% !important;
 +
}
  
−
</div>
 
  
 +
/* This styles the big paragraph text areas */
 +
#formbody textarea {
 +
border: 1px solid #d3d3d3;
 +
border-radius: 5px;
 +
box-sizing: border-box;
 +
display: inline-block;
 +
padding: 15px;
 +
width: 99%;
 +
}
  
−
<div id="submitted_warning">
 
−
<p>This form has been submitted.</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>
 
−
</div>
 
−
</div>
 
  
  
  
−
<div class="column full_size">
+
/* This styles the dropdown select  */
 +
#formbody select{
 +
background: #ffffff;
 +
border: 1px solid #d3d3d3;
 +
margin-bottom: 3px;
 +
width: 20%;
 +
}
  
−
<div id="formtitlemodewrapper">
 
−
<h2 id="toptitle">
 
−
<span id="form_title_display"></span> <span id="owner_name_display"></span>
 
−
</h2>
 
  
−
<h4 id="modes"></h4>
 
  
 +
#formbody .teamselector-multiple {
 +
border-radius: 5%;
 +
padding: 15px;
 +
margin: 0px 15px;
 +
width: 85%;
 +
}
  
  
  
 +
/* visible when selecting which dropdown option */
 +
#formbody input:focus {
 +
background: #ffffff;
 +
}
  
−
<div class="admins_only" id="admin_link">
+
 
−
<p>Admin view (orange)  is only visible to super users. (<a href="#" id="hide_admin">Hide admin view</a>)</p>
+
 
−
<p><b><a class="change_mode" data-mode="admin">Go to Admin Mode</a></b> / <a class="change_team" data-team="1874">Go to Team Example</a> / Go to Username: <input type="text" id="author_select" autocomplete="off"></p>
+
 
−
</div>
+
/*This styles the input text boxes and select dropdown when selected or brought "in focus"  */
 +
input[type=text]:focus, #formbody textarea:focus ,  #formbody select:focus{
 +
border: 1px solid #00bdcd;
 +
outline: none;
 +
}
 +
 
 +
 
 +
 
 +
 
 +
/*This styles the input submit button  */
 +
input[type=submit], input[type="button" i], input[type="submit" i], input[type="reset" i], input[type="file" i]::-webkit-file-upload-button, button  {
 +
background-color: #00a19c !important;
 +
border-radius: 4px;
 +
color: #ffffff !important;
 +
cursor: pointer;
 +
font-size:105%;
 +
font-weight: bold;
 +
margin: auto;
 +
min-width: 50%;
 +
text-decoration: none !important;
 +
padding: 15px !important;
 +
}
 +
 
 +
 
 +
 
 +
 
 +
/*This styles the input submit button  on hover */
 +
input[type=submit]:hover, input[type="button" i] :hover, input[type="submit" i]:hover, input[type="reset" i]:hover, input[type="file" i]::-webkit-file-upload-button:hover, button:hover {
 +
background-color: #0a5157 !important;
 +
}
 +
 
 +
 
 +
/*styling for p class used for questions */
 +
#formbody .question {
 +
color: #000000;
 +
font-weight: bold;
 +
margin-top: 1em;
 +
}
 +
 
 +
 
 +
 
 +
/* styling for ul in forms */
 +
#formbody fieldset ul {
 +
margin-left: 0px;
 +
list-style:none;
 +
padding-left: 25px;
 +
}
 +
 
 +
 
 +
/* styling for ul in forms */
 +
#formbody fieldset ul li {
 +
list-style:none;
 +
padding: 10px 0px;
 +
}
 +
 
 +
 
 +
/* styling for the wrapper class, this class surrounds an item that is being saved into the system. it gives visual feedback to the user that the form is working.  */
 +
#formbody .wrapper{
 +
background-color: transparent;
 +
padding: 10px;
 +
}
 +
 
 +
 
 +
 
 +
/* make span class align the text to the left of dropdowns so they all align */
 +
#formbody .align_dropdowns {
 +
float: left;
 +
padding: 5px 0px;
 +
width: 90px;
 +
}
 +
 
 +
 
 +
 
 +
#formbody .dropdown_question {
 +
padding: 0px 32px;
 +
margin-bottom: 10px;
 +
}
 +
 
 +
 
 +
/*style section numbers */
 +
.section_numbers {
 +
color: #00bdcd;
 +
border-radius: 50%;
 +
padding: 5px 7px 5px 9px;
 +
text-align: center;
 +
font-size: 15px;
 +
margin-right: 10px;
 +
border: 3px solid #00bdcd;
 +
}
 +
 
 +
 
 +
.admins_only {
 +
display: none;
 +
border: 2px solid #FF9900 !important;
 +
}
 +
 
 +
 
 +
 
 +
#formbody td {
 +
text-align: center;
 +
}
 +
 
 +
 
 +
.submitted_form_message{
 +
    background-color: #ffda00;
 +
    bottom: 0px;
 +
    left: 0px;
 +
padding: 1% 0;
 +
position: fixed;
 +
display:none;
 +
}
 +
 
 +
 
 +
.question_note{
 +
color: #6b6b6b;
 +
font-style: italic;
 +
font-weight: normal;
 +
}
 +
 
 +
 
 +
#aj_form_error_inner_div {
 +
background-color: rgba(255, 228, 232, 0.71);
 +
    border: 1px solid #fdb9b9;
 +
    border-radius: 5px;
 +
display: block;
 +
    margin: 30px auto 20px auto;
 +
    padding: 15px 0px;
 +
    text-align: center;
 +
    width: 40%;
 +
}
 +
 
 +
 
 +
 
 +
 
 +
#aj_form_error_inner_div img {
 +
    padding: 0px;
 +
width: 10%;
 +
}
 +
 
 +
 
 +
#formbody select#team_list_dropdown {
 +
    margin: auto 12px;
 +
    width: 80%;
 +
}
 +
 
 +
 
 +
#formbody fieldset .column.half_size.left_side{
 +
padding: 0px;
 +
margin-left: 0;
 +
width: 42%;
 +
}
 +
 
 +
#formbody fieldset .column.half_size.right_side{
 +
border-left:1px solid black;
 +
padding-left:5%;
 +
}
 +
 
 +
#formbody fieldset .column.third_size {
 +
padding: 0px;
 +
width:29.3%;
 +
}
 +
 
 +
 
 +
 
 +
 +
/* 1100px */
 +
/************************************************/
 +
@media only screen and (max-width: 1100px) {
 +
 +
#formbody fieldset .column.half_size.left_side,
 +
#formbody fieldset .column.half_size.right_side,
 +
#formbody fieldset .column.third_size {width:96%;}
 +
 +
#formbody fieldset .column.half_size.right_side{
 +
border-left:none;
 +
border-top:1px solid black;
 +
padding-left:0;
 +
padding-top:10%;
 +
}
 +
}
 +
</style>
 +
 
 +
 
 +
 +
 +
<script src="https://igem.org/wiki/index.php?title=HQ:Judging_Form.js&action=raw&ctype=text/javascript"></script>
 +
 +
 
 +
 
 +
<div class="column full_size" style="text-align:center; margin:auto;"><h1> Judge Application Form </h1> </div>
 +
<div class="clear"></div>
 +
<div class="line_divider"></div>
 +
<div class="clear extra_space"></div>
 +
 
 +
 
 +
<div class="column full_size">
 +
<div id='aj_form_errors'> </div>
 +
 +
<div id="submitted_warning">
 +
<p>This form has been submitted.</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>
 +
</div>
 
</div>
 
</div>
  
  
  
 +
<div class="column full_size">
  
 +
<div id="formtitlemodewrapper">
 +
<h2 id="toptitle">
 +
<span id="form_title_display"></span> <span id="owner_name_display"></span>
 +
</h2>
  
 +
<h4 id="modes"></h4>
  
 +
<div class="admins_only" id="admin_link">
 +
<p>Admin view (orange)  is only visible to super users. (<a href="#" id="hide_admin">Hide admin view</a>)</p>
 +
<p><b><a class="change_mode" data-mode="admin">Go to Admin Mode</a></b> / <a class="change_team" data-team="1874">Go to Team Example</a> / Go to Username: <input type="text" id="author_select" autocomplete="off"></p>
 +
</div>
 +
 +
</div>
 +
</div>
  
  
−
<!--Enclose the actual questions in a div id="formbody"-->
 
−
<div id="formbody">
 
  
 +
 +
 +
 +
 +
<!--Enclose the actual questions in a div id="formbody"-->
 +
<div class="column full_size" id="formbody">
 
<!-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 
<!-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
  
Line 290: Line 552:
 
</div>
 
</div>
 
<p>
 
<p>
−
To be eligible to become an iGEM judge, you must be at least 23 years old as of March 31, 2019. We also expect judges to have completed their undergraduate degree before the Jamboree takes place.  
+
Applicants must be at least 23 years old as of March 31, 2020, and have completed their undergraduate degree by June 30, 2020, to be considered for the judging panel.
 
</p>
 
</p>
 
</div>
 
</div>
Line 414: Line 676:
  
  
 +
 +
  
  
Line 428: Line 692:
 
<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>
  
−
<p class="question">1. Sweatshirt Size:</p>
 
−
<ul>
 
−
<li><label><input type="radio" name="Sweatshirt Size" data-form-field="size" id="XS" value="XS"> XS</label> </li>
 
−
<li><label><input type="radio" name="Sweatshirt Size" data-form-field="size" id="S" value="S"> S</label> </li>
 
−
<li><label><input type="radio" name="Sweatshirt Size" data-form-field="size" id="M" value="M"> M</label> </li>
 
−
<li><label><input type="radio" name="Sweatshirt Size" data-form-field="size" id="L" value="L"> L</label> </li>
 
−
<li><label><input type="radio" name="Sweatshirt Size" data-form-field="size" id="XL" value="XL"> XL</label> </li>
 
−
<li><label><input type="radio" name="Sweatshirt Size" data-form-field="size" id="XXL" value="XXL"> XXL</label> </li>
 
−
</ul>
 
  
  
−
<p class="question">2. Are you available to attend the <b>entire</b> <a href="https
+
<p class="question">1. Please indicate which days/times you are available to attend the Virtual Giant Jamboree November 14 - 16.</p>
−
://2019.igem.org/Giant_Jamboree">Giant Jamboree</a> from October 31 - November 4, 2019, in Boston?</p>
+
−
<ul>
+
−
<li><label><input type="radio" name="Jamboree Attendance" data-form-field="jamboree" value="yes">Yes</label></li>
+
−
<li><label><input type="radio" name="Jamboree Attendance" data-form-field="jamboree" value="no"> No</label> </li>
+
−
</ul>
+
  
−
<p class="question">2.1 If not, please indicate which days/times you are available to attend.</p>
 
  
−
<div class="column half_size">
 
 
<table>
 
<table>
−
<tr> <th> Day </th> <th>Morning </th> <th> Evening </th> </tr>
+
<tr>  
−
 
+
<th> Day </th>  
−
<tr>
+
<th> 1AM - 5AM (EDT) </th>  
−
<th>Thursday <br> October 31</th>
+
<th> 5AM - 9AM (EDT) </th>  
−
<td></td>
+
<th> 9AM - 1PM (EDT) </th>  
−
<td><label><input type="radio" name="Availability Thurs Oct 31, Evening" data-form-field="available_thu_eve" value="yes"> Yes</label><br /><br>
+
<th> 1PM - 5PM (EDT) </th>  
−
<label><input type="radio" name="Availability Thurs Oct 31, Evening" data-form-field="available_thu_eve" value="no"> No</label>
+
<th> 5PM - 9PM (EDT) </th>  
−
</td>
+
<th> 9PM - 1AM (EDT) </th>  
 
</tr>
 
</tr>
−
 
  
 
<tr>
 
<tr>
−
<th>Friday <br> November 1</th>
+
<th>November 14</th>
−
<td><label><input type="radio" name="Availability Fri Nov 1, Morning" data-form-field="available_fri_morn" value="yes"> Yes</label><br /><br>
+
 
−
<label><input type="radio" name="Availability Fri Nov 1, Morning" data-form-field="available_fri_morn" value="no"> No</label>
+
<td>
 +
<label>
 +
<input type="radio" name="Nov 14 1am-5am EDT " data-form-field="available_NOV14_1AM-5AM" value="yes"> Yes
 +
</label>
 +
<br><br>
 +
<label>
 +
<input type="radio" name="Nov 14 1am-5am EDT " data-form-field="available_NOV14_1AM-5AM" value="No"> No
 +
</label>
 
</td>
 
</td>
−
<td><label><input type="radio" name="Availability Fri Nov 1, Evening" data-form-field="available_fri_eve" value="yes"> Yes</label><br /><br>
+
−
<label><input type="radio" name="Availability Fri Nov 1, Evening" data-form-field="available_fri_eve" value="no"> No</label>
+
<td>
 +
<label>
 +
<input type="radio" name="Nov 14 5am-9am EDT " data-form-field="available_NOV14_5AM-9AM" value="yes"> Yes
 +
</label>
 +
<br><br>
 +
<label>
 +
<input type="radio" name="Nov 14 5am-9am EDT " data-form-field="available_NOV14_5AM-9AM" value="No"> No
 +
</label>
 
</td>
 
</td>
−
</tr>
+
 +
<td>
 +
<label>
 +
<input type="radio" name="Nov 14 9am-1pm EDT " data-form-field="available_NOV14_9AM-1PM" value="yes"> Yes
 +
</label>
 +
<br><br>
 +
<label>
 +
<input type="radio" name="Nov 14 9am-1pm EDT " data-form-field="available_NOV14_9AM-1PM" value="No"> No
 +
</label>
 +
</td>
  
−
<tr>
+
−
<th>Saturday <br> November 2</th>
+
<td>
−
<td><label><input type="radio" name="Availability Sat Nov 2, Morning" data-form-field="available_sat_morn" value="yes"> Yes</label><br /><br>
+
<label>
−
<label><input type="radio" name="Availability Sat Nov 2, Morning" data-form-field="available_sat_morn" value="no"> No</label>
+
<input type="radio" name="Nov 14 1pm-5pm EDT " data-form-field="available_NOV14_1PM-5PM" value="yes"> Yes
−
</td>
+
</label>
−
<td><label><input type="radio" name="Availability Sat Nov 2, Evening" data-form-field="available_sat_eve" value="yes"> Yes</label><br /><br>
+
<br><br>
−
<label><input type="radio" name="Availability Sat Nov 2, Evening" data-form-field="available_sat_eve" value="no"> No</label>
+
<label>
 +
<input type="radio" name="Nov 14 1pm-5pm EDT " data-form-field="available_NOV14_1PM-5PM" value="No"> No
 +
</label>
 +
</td>
 +
 +
 
 +
<td>
 +
<label>
 +
<input type="radio" name="Nov 14 5pm-9pm EDT " data-form-field="available_NOV14_5PM-9PM" value="yes"> Yes
 +
</label>
 +
<br><br>
 +
<label>
 +
<input type="radio" name="Nov 14 5pm-9pm EDT " data-form-field="available_NOV14_5PM-9PM" value="No"> No
 +
</label>
 
</td>
 
</td>
  
 +
 +
<td>
 +
<label>
 +
<input type="radio" name="Nov 14 9pm-1am EDT " data-form-field="available_NOV14_9PM-1AM" value="yes"> Yes
 +
</label>
 +
<br><br>
 +
<label>
 +
<input type="radio" name="Nov 14 9pm-1am EDT " data-form-field="available_NOV14_9PM-1AM" value="No"> No
 +
</label>
 +
</td>
 +
 
</tr>
 
</tr>
  
Line 485: Line 779:
  
 
<tr>
 
<tr>
 +
<th>November 15</th>
  
−
<th>Sunday <br> November 3</th>
+
<td>
−
 
+
<label>
−
<td><label><input type="radio" name="Availability Sun Nov 3, Morning" data-form-field="available_sun_morn" value="yes"> Yes</label><br /><br>
+
<input type="radio" name="Nov 15 1am-5am EDT " data-form-field="available_NOV15_1AM-5AM" value="yes"> Yes
−
<label><input type="radio" name="Availability Sun Nov 3, Morning" data-form-field="available_sun_morn" value="no"> No</label>
+
</label>
 +
<br><br>
 +
<label>
 +
<input type="radio" name="Nov 15 1am-5am EDT " data-form-field="available_NOV15_1AM-5AM" value="No"> No
 +
</label>
 
</td>
 
</td>
−
<td><label><input type="radio" name="Availability Sun Nov 3, Evening" data-form-field="available_sun_eve" value="yes"> Yes</label><br /><br>
+
−
<label><input type="radio" name="Availability Sun Nov 3, Evening" data-form-field="available_sun_eve" value="no"> No</label>
+
<td>
 +
<label>
 +
<input type="radio" name="Nov 15 5am-9am EDT " data-form-field="available_NOV15_5AM-9AM" value="yes"> Yes
 +
</label>
 +
<br><br>
 +
<label>
 +
<input type="radio" name="Nov 15 5am-9am EDT " data-form-field="available_NOV15_5AM-9AM" value="No"> No
 +
</label>
 
</td>
 
</td>
 +
 +
<td>
 +
<label>
 +
<input type="radio" name="Nov 15 9am-1pm EDT " data-form-field="available_NOV15_9AM-1PM" value="yes"> Yes
 +
</label>
 +
<br><br>
 +
<label>
 +
<input type="radio" name="Nov 15 9am-1pm EDT " data-form-field="available_NOV15_9AM-1PM" value="No"> No
 +
</label>
 +
</td>
  
 +
 +
<td>
 +
<label>
 +
<input type="radio" name="Nov 15 1pm-5pm EDT " data-form-field="available_NOV15_1PM-5PM" value="yes"> Yes
 +
</label>
 +
<br><br>
 +
<label>
 +
<input type="radio" name="Nov 15 1pm-5pm EDT " data-form-field="available_NOV15_1PM-5PM" value="No"> No
 +
</label>
 +
</td>
 +
 +
 +
<td>
 +
<label>
 +
<input type="radio" name="Nov 15 5pm-9pm EDT " data-form-field="available_NOV15_5PM-9PM" value="yes"> Yes
 +
</label>
 +
<br><br>
 +
<label>
 +
<input type="radio" name="Nov 15 5pm-9pm EDT " data-form-field="available_NOV15_5PM-9PM" value="No"> No
 +
</label>
 +
</td>
 +
 +
 +
<td>
 +
<label>
 +
<input type="radio" name="Nov 15 9pm-1am EDT " data-form-field="available_NOV15_9PM-1AM" value="yes"> Yes
 +
</label>
 +
<br><br>
 +
<label>
 +
<input type="radio" name="Nov 15 9pm-1am EDT " data-form-field="available_NOV15_9PM-1AM" value="No"> No
 +
</label>
 +
</td>
 +
 
</tr>
 
</tr>
 +
  
 
<tr>
 
<tr>
−
<th>Monday <br> November 4</th>
+
<th>November 16</th>
−
<td><label><input type="radio" name="Availability Mon Nov 4, Morning" data-form-field="available_mon_morn" value="yes"> Yes</label><br /><br>
+
 
−
<label><input type="radio" name="Availability Mon Nov 4, Morning" data-form-field="available_mon_morn" value="no"> No</label>
+
<td>
 +
<label>
 +
<input type="radio" name="Nov 16 1am-5am EDT " data-form-field="available_NOV16_1AM-5AM" value="yes"> Yes
 +
</label>
 +
<br><br>
 +
<label>
 +
<input type="radio" name="Nov 16 1am-5am EDT " data-form-field="available_NOV16_1AM-5AM" value="No"> No
 +
</label>
 
</td>
 
</td>
−
<td><label><input type="radio" name="Availability Mon Nov 4, Evening" data-form-field="available_mon_eve" value="yes"> Yes</label><br /><br>
+
−
<label><input type="radio" name="Availability Mon Nov 4, Evening" data-form-field="available_mon_eve" value="no"> No</label>
+
<td>
 +
<label>
 +
<input type="radio" name="Nov 16 5am-9am EDT " data-form-field="available_NOV16_5AM-9AM" value="yes"> Yes
 +
</label>
 +
<br><br>
 +
<label>
 +
<input type="radio" name="Nov 16 5am-9am EDT " data-form-field="available_NOV16_5AM-9AM" value="No"> No
 +
</label>
 
</td>
 
</td>
−
</tr>
+
 +
<td>
 +
<label>
 +
<input type="radio" name="Nov 16 9am-1pm EDT " data-form-field="available_NOV16_9AM-1PM" value="yes"> Yes
 +
</label>
 +
<br><br>
 +
<label>
 +
<input type="radio" name="Nov 16 9am-1pm EDT " data-form-field="available_NOV16_9AM-1PM" value="No"> No
 +
</label>
 +
</td>
  
−
</table>
+
 +
<td>
 +
<label>
 +
<input type="radio" name="Nov 16 1pm-5pm EDT " data-form-field="available_NOV16_1PM-5PM" value="yes"> Yes
 +
</label>
 +
<br><br>
 +
<label>
 +
<input type="radio" name="Nov 16 1pm-5pm EDT " data-form-field="available_NOV16_1PM-5PM" value="No"> No
 +
</label>
 +
</td>
 +
  
 +
<td>
 +
<label>
 +
<input type="radio" name="Nov 16 5pm-9pm EDT " data-form-field="available_NOV16_5PM-9PM" value="yes"> Yes
 +
</label>
 +
<br><br>
 +
<label>
 +
<input type="radio" name="Nov 16 5pm-9pm EDT " data-form-field="available_NOV16_5PM-9PM" value="No"> No
 +
</label>
 +
</td>
  
−
</div>
 
  
 +
<td>
 +
<label>
 +
<input type="radio" name="Nov 16 9pm-1am EDT " data-form-field="available_NOV16_9PM-1AM" value="yes"> Yes
 +
</label>
 +
<br><br>
 +
<label>
 +
<input type="radio" name="Nov 16 9pm-1am EDT " data-form-field="available_NOV16_9PM-1AM" value="No"> No
 +
</label>
 +
</td>
 +
 +
</tr>
  
  
−
</fieldset>
+
</table>
  
 +
 +
<div class="clear extra_space"></div>
 +
 +
  
 +
<p class="question">2. Please indicate your availability for Saturday November 21.</p>
  
 +
<div class="column half_size">
 +
<table>
 +
<tr>
 +
<th> Day </th>
 +
<th> 9AM - 11AM (EDT) </th>
 +
</tr>
 +
 +
<tr>
 +
<th>November 21</th>
  
 +
<td>
 +
<label>
 +
<input type="radio" name="Nov 21 9am-11am EDT " data-form-field="available_NOV21_9AM-11AM" value="yes"> Yes
 +
</label>
 +
<br><br>
 +
<label>
 +
<input type="radio" name="Nov 21 9am-11am EDT " data-form-field="available_NOV21_9AM-11AM" value="No"> No
 +
</label>
 +
</td>
 +
</tr>
 +
 +
 +
</table>
 +
</div>
  
 +
 +
 +
 +
 +
<div class="clear extra_space"></div>
 +
 +
 +
</fieldset>
 +
 +
 +
  
 
<!-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 
<!-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Line 544: Line 985:
 
<br><br>
 
<br><br>
 
<select multiple class="teamselector-multiple" size="20" name="Team affiliations" id="team_affiliations" data-form-field="team_affiliations">
 
<select multiple class="teamselector-multiple" size="20" name="Team affiliations" id="team_affiliations" data-form-field="team_affiliations">
−
<option class='none_selected'>I have no 2019 team affiliations</option>
+
<option class='none_selected'>I have no 2020 team affiliations</option>
 
</select>
 
</select>
  
Line 556: Line 997:
  
 
<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 2019 team conflicts of interest</option>
+
<option class='none_selected'>I have no 2020 team conflicts of interest</option>
 
</select>
 
</select>
  
Line 568: Line 1,009:
 
</fieldset>
 
</fieldset>
  
−
 
+
 +
 +
  
  
Line 582: Line 1,025:
 
<fieldset>  
 
<fieldset>  
  
−
<h2>4. Motivation</h2>
+
<h2>4.- Motivation</h2>
−
<p>Please answer these questions in detail.</p>
+
<p>Your application will be anonymized for evaluation, so please refrain from giving out any identifying information in the answer to these questions. </p>
−
<p>Did you apply to judge last year? <a id="last_years_application_link" target="_blank">View your answers from last year.</a> Please note we have changed some of the questions for 2019.</p>
+
  
  
  
−
<p class="question">1. 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">2. What professional experience do you have that you believe is relevant to iGEM (e.g., synthetic biology, hardware, software, human practices)?</p>
+
<p class="question">2. What professional experience do you have that you believe is 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">3. How important is scientific and/or engineering success to overall team success?</p>
+
<p class="question">3. What role do you believe judging serves in iGEM? </p>
−
<textarea rows="5" name="How important is scientific and/or engineering" id="scientific_engineering" data-form-field="success" maxlength="2000"></textarea>
+
<textarea rows="5" name="role judges serve in iGEM" id="jugde_role_iGEM" data-form-field="judge_role_iGEM" maxlength="2000"></textarea>
  
−
<p class="question">4. What are the synthetic biology principles that iGEM participants should learn during their project?</p>
+
<p class="question">4. What features of an iGEM team and their project do you think are most valuable? </p>
−
<textarea rows="5" name="What are the synthetic biology principles" id="synbio_principles" data-form-field="principles"></textarea maxlength="2000"></fieldset>
+
<textarea rows="6" name="What makes an iGEM team worthy of recognition" id="what_makes_project_worthy" data-form-field="what_makes_project_worthy" maxlength="2500"></textarea>
 +
 +
</fieldset>
  
 +
 +
  
  
Line 614: Line 1,062:
 
<h2>5. 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://2019.igem.org/Competition/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://2020.igem.org/Competition/Tracks" target="_blank">the Track page</a> for more information on each track.</p>
  
−
<p>When we assign judges to teams, we will try to assign you your first preferences wherever possible. However, we can't anticipate how many teams will be in each track, so it may not always be possible to assign you your first choice. Therefore, you can indicate how you feel about each track. The more first choices you select, the more likely it is that you will be assigned teams in those tracks. If you are <b>unable</b> to evaluate teams in some track areas (software, for example), please put "Avoid" for those tracks.</p>
+
 +
<p>This year the presentation scheduling for the Giant Jamboree will be dependent on timezones rather than tracks. It is possible that track preferences will not be taken into consideration, as teams and their judges will be grouped together based on timezone availability first, and track second. However, we will try to assign you to your track preferences wherever possible. If you are unable to evaluate teams in some track areas (software, for example), please put "Avoid" for those tracks. </p>
  
−
<p class="question">Please indicate how highly you prefer each track. You may select multiple first, second, and third preferences.</p>
+
<p>Please indicate how highly you prefer each track. You may select multiple first, second, and third preferences. </p>
  
 
<table id="track_prefs_table">
 
<table id="track_prefs_table">
Line 670: Line 1,119:
 
<td><input type="radio" name="Track Preference: Foundational Advance" data-form-field="pref_foundational" value="avoid"></td>
 
<td><input type="radio" name="Track Preference: Foundational Advance" data-form-field="pref_foundational" value="avoid"></td>
 
</tr>
 
</tr>
 +
<tr>
 +
<th>Hardware</th>
 +
<td><input type="radio"  name="Track Preference: Hardware" data-form-field="pref_hardware" value="first"></td>
 +
<td><input type="radio"  name="Track Preference: Hardware" data-form-field="pref_hardware" value="second"></td>
 +
<td><input type="radio"  name="Track Preference: Hardware" data-form-field="pref_hardware"  value="third"></td>
 +
<td><input type="radio"  name="Track Preference: Hardware" data-form-field="pref_hardware"  value="neutral"></td>
 +
<td><input type="radio"  name="Track Preference: Hardware" data-form-field="pref_hardware"  value="avoid"></td>
 +
</tr>
 +
 
<tr>
 
<tr>
 
<th>High School</th>
 
<th>High School</th>
Line 727: Line 1,185:
 
</tr>
 
</tr>
 
</table>
 
</table>
−
</fieldset>
+
</fieldset>
 +
 
</div>
 
</div>
 +
  
  
Line 741: Line 1,201:
 
<h3 style="margin:auto; text-align:center"> Thank you! </h3>  
 
<h3 style="margin:auto; text-align:center"> Thank you! </h3>  
  
−
<p style="margin:auto; text-align:center">Thank you for filling out this form. We look forward to picking a strong judging team for 2019!</p>
+
<p style="margin:auto; text-align:center">Thank you for filling out this form. We look forward to picking a strong judging team for 2020!</p>
  
  
Line 752: Line 1,212:
  
 
</div>
 
</div>
−
</div>
+
</div>
−
 
+
−
 
+
−
<!-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+
<!--form ends-->
−
 
+
−
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+
−
 
+
−
THIS IS WHERE THE FORM ENDS
+
−
 
+
−
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+
−
 
+
−
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------->
+
−
 
+
−
 
+
−
 
+
−
 
+
−
 
+
−
 
+
−
 
+
−
 
+
  
  
Line 782: Line 1,227:
 
$("#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://2018.igem.org/Judging/Apply?author=" + data.user_name + "#formbody");
+
$("#last_years_application_link").attr("href", "https://2019.igem.org/Judging/Apply?author=" + data.user_name + "#formbody");
 
}
 
}
  
Line 815: Line 1,260:
 
timeout: 30000,
 
timeout: 30000,
 
dataType: "json",
 
dataType: "json",
−
data: {command: "get_team_list", year: "2019"}, //**Make this auto-update itself
+
data: {command: "get_team_list", year: "2020"}, //**Make this auto-update itself
 
error: function(jqxhr, textStatus, errorThrown) {
 
error: function(jqxhr, textStatus, errorThrown) {
 
general_ajax_error( jqxhr, textStatus, errorThrown,
 
general_ajax_error( jqxhr, textStatus, errorThrown,
Line 849: Line 1,294:
 
});
 
});
 
</script>
 
</script>
−
 
+
 
</div>
 
</div>
−
 
 
</div>
 
</div>
 
</html>
 
</html>
−
{{Footer2019}}
+
{{Footer2020}}

Revision as of 18:31, 31 July 2020

Template:Main2020

You have JavaScript disabled.

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

iGEM 2020 Judging Applications

On this page you will find information on: Judging at the Giant Jamboree, Why Should You be an iGEM Judge?, Who Should Apply to be a Judge?, Expectations for Judges, Application Process, Recruitment Goals, and the Judge Application

Judging at the Giant Jamboree

Judging in iGEM is a fun, rewarding experience and requires commitment! Through the judging process, our judges will evaluate, celebrate, and help guide the next generation of synthetic biologists. Judges help the entire iGEM community celebrate the hard work and achievements of our iGEM teams.

We need judges — both experienced and new — who understand and value iGEM. Many of our judges come back year after year, and we gladly welcome new judges to apply as well.

Great news: no jet-lag this year! The Giant Jamboree is entirely virtual. Travel will not be a constraint for judges for the first time in iGEM’s history. We are hopeful that this will allow us to recruit an even more diverse panel of judges from our global iGEM community.

iGEM teams work incredibly hard on their projects, so we need judges who are also committed. Judges are expected to dedicate their time and effort to thoroughly evaluate the projects of their assigned teams. The judging process also includes attending virtual training sessions prior to the Jamboree, attending various sessions during the Giant Jamboree to interact with and evaluate your assigned teams, and providing written feedback to your assigned teams.

Judges at the 2019 Giant Jamboree

Why Should You be an iGEM Judge?

Judging at the annual iGEM Giant Jamboree is an incredibly fulfilling and worthwhile experience for all judges, whether you're returning as a veteran judge or are a new judge this year. Some of the benefits include:

  • Contributing to the iGEM Community By volunteering to judge at the Giant Jamboree, you will contribute to one of the most meaningful opportunities that these students experience in synthetic biology. Providing constructive feedback to these dedicated students can be life changing for them as they continue through their academic career and beyond.
  • Networking: Much like the iGEM teams, you'll have the chance to connect with people from around the globe, to expand your synthetic biology community, and to form new collaborations beyond the Giant Jamboree. You will meet fellow judges, students, and other professionals from around the world and different walks of life.
  • Learning About New Technology: You will learn about the latest cutting edge work being done in synthetic biology from student teams who are driven to excel and who test the boundaries of synthetic biology through their projects.
  • Attending for Free: Judges will not pay any registration fee for the Giant Jamboree!

Who Should Apply to be a Judge?

We're looking for:

  • iGEM PIs, instructors, and advisors, from both current and past iGEM teams
  • People who have judged iGEM previously
  • iGEM alumni who want to stay involved, including professionals, graduate students, and post-docs
  • Professionals in the synthetic biology, biotechnology, and engineering industries
  • People who have experience in complementary areas, such as the humanities, art and design, and software

If you have colleagues who you think should apply, please feel free to direct them to this form. While previous iGEM experience is preferred, we gladly welcome new applicants - particularly those that demonstrate a strong knowledge of and value for iGEM.

Applicants must be at least 23 years old as of March 31, 2020, and have completed their undergraduate degree by June 30, 2020, to be considered for the judging panel.

If you are a student on a 2020 iGEM team, then you can't apply to be a judge this year, but you can apply when you graduate and become an iGEM alum!

Application Process

This year, the Giant Jamboree will have an expanded schedule [link once ready] to accommodate a global virtual audience. Most of the judging activities will take place from November 14-16 (Saturday-Monday) and will run across three time zones (EDT [UTC -4], CEST [UTC +2], and CST [UTC +8]). We are looking for judges who are available during one or more of these major time zones to ensure coverage for our teams. We plan to accommodate your personal schedule requirements when assigning you teams to evaluate.

Judges will be assigned 6-9 teams to evaluate. The evaluation process will include reviewing Team Wikis and watching Presentation Videos prior to the Giant Jamboree and attending sessions between November 14-16 during the Giant Jamboree to interact with and evaluate their assigned teams. Judges are also required to provide written feedback for each of their teams in the Judging Ballot provided to them.

Judges will also evaluate the iGEM Finalists (announced on Thursday, November 19) and vote for the winners on Saturday, November 21.

Judges are also invited to attend the Closing and Awards Ceremonies on Sunday, November 22, which will take place between 8am - 12pm EDT.

Application Process

This year we are accepting applications on a rolling basis. We will be evaluating applications twice per month and will contact applicants approximately two weeks after the evaluation period with a status notification, such as 1. invitation to judge, 2. invitation to serve as a reserve judge, 3. invitation to re-apply, or 4. decline for 2020 with an invitation to apply next year. Notifications will be sent twice a month, beginning in July, until our quota is full (expected by the end of September). We encourage you to apply early to increase your chances of being selected!

You can apply to be a judge before knowing if you can fully commit to attending the Giant Jamboree. Applicants who are invited to join the judging panel will be asked to confirm their acceptance and their availability. We can also provide an official invitation letter if you require that to secure permission from your institute to participate as a judge.

Once we have reached our quota of judges, we will close the application and add a notice to this page.

Applications will be anonymized and evaluated by experienced judges who belong to the Judging Corps Committee [link to committee page] and Executive Judging Committee [link to committee page]. If possible, please refrain from using identifying information in the answers to your application questions (Section 4).

Recruitment Goals

We will be recruiting a diverse judging panel with the following characteristics in mind:

  • Gender parity
  • Regional diversity with time zone coverage
  • iGEM experience (i.e., past and present team PIs, mentors, and advisors; previous team members; returning judges)
Questions?

Please email traci [AT] igem [DOT] org and/or vinoo [AT] igem [DOT] org if you have questions!

Judge Application Form

This form has been submitted.

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

Click here to dismiss this message

1. General Information

Full name: -

Username: -

1. Email

2. Age

Note

Applicants must be at least 23 years old as of March 31, 2020, and have completed their undergraduate degree by June 30, 2020, to be considered for the judging panel.

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:

Judge:


PI/Instructor:


Advisor:


Student:


Volunteer:

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. Please indicate which days/times you are available to attend the Virtual Giant Jamboree November 14 - 16.

Day 1AM - 5AM (EDT) 5AM - 9AM (EDT) 9AM - 1PM (EDT) 1PM - 5PM (EDT) 5PM - 9PM (EDT) 9PM - 1AM (EDT)
November 14











November 15











November 16











2. Please indicate your availability for Saturday November 21.

Day 9AM - 11AM (EDT)
November 21

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

Your application will be anonymized for evaluation, so please refrain from giving out any identifying information in the answer to these questions.

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

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

3. What role do you believe judging serves in iGEM?

4. What features of an iGEM team and their project do you think are most valuable?

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.

This year the presentation scheduling for the Giant Jamboree will be dependent on timezones rather than tracks. It is possible that track preferences will not be taken into consideration, as teams and their judges will be grouped together based on timezone availability first, and track second. However, we will try to assign you to your track preferences wherever possible. If you are unable to evaluate teams in some track areas (software, 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
Diagnostics
Energy
Environment
Food and Nutrition
Foundational Advance
Hardware
High School
Information Processing
Manufacturing
New Application
Open
Software
Therapeutics

Thank you!

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

Finished?

Need to make changes?

Template:Footer2020