Difference between revisions of "Requirements"

m
 
(187 intermediate revisions by 7 users not shown)
Line 1: Line 1:
 +
{{Mobile}}
 
<html>
 
<html>
−
<div class="oneColumn alert_box">
+
 
−
<center>This page is under active development and is in draft form. Nothing posted here is finalized.
+
<div class="oneColumn ">
−
</center>
+
<div class="background_gray full_border">
 +
<p><b>NOTE:</b></p>
 +
 
 +
<p>All iGEM participants (including students, instructors, and advisors) are expected to read and understand the following iGEM requirements.  
 +
<br><br>Teams that do not comply with the requirements may not be eligible to win awards and prizes. See all details below and be sure to ask iGEM Headquarters if you have any questions.</p>
 +
</div>
 
</div>
 
</div>
−
<br><br><br><br><br>
 
  
−
<h3>Deliverables</h3>
 
−
<p>Every iGEM team is responsible for delivering the following 12 items (with 2 additional optional items). These items are used to evaluate your team, in addition to the other medal (link to: https://2015.igem.org/Judging/Medals) and award criteria (link to: https://2015.igem.org/Judging/Awards). Failure to complete these deliverables may impact your team’s chances at winning prizes during the Giant Jamboree.</p>
 
  
−
<ul><h5>Required Deliverables</h5></ul>
 
  
−
<ul>
+
<div class="clear_id" id="Team"></div>
−
<ol>
+
−
<li><a href="https://2015.igem.org/Wiki_Requirements">Team wiki</a>: Teams need to document their project on their Team Wiki page.</li> <ul>Wiki Freeze Date: <a href="https://2015.igem.org/Calendar_of_Events">October XX, 2016</a></ul>
+
−
<li><a href="https://2015.igem.org/Poster">Poster<a/>: Each team must present a poster of their project at the Giant Jamboree.</li><ul>Poster PDF Due: <a href="https://2015.igem.org/Calendar_of_Events">October XX, 2016</a></ul>
+
−
<li><a href="https://2015.igem.org/Presentation">Presentation</a>: Each team has 20 minutes to present their project at the Giant Jamboree.</li>
+
−
<li><a href="https://2015.igem.org/Team:Example2/Attributions">Project Attribution</a>: Teams must clearly state the work done by the team.</li>
+
−
<li>Registry Pages</li>
+
−
<li>Sample Submission</li>
+
−
<i>Safety Forms</i>
+
−
<ol>
+
−
<li value=7>Check-in Form</li>
+
−
<li>About Our Lab</li>
+
−
<li>About Our Project</li>
+
−
<li>Final Safety Form</li>
+
−
</ol>
+
−
<i>Judging Forms</i>
+
−
<ol>
+
−
<li value=11>Check-in Form</li>
+
−
<li>Final Judging Form</li>
+
−
</ol>
+
−
</ol></ul>
+
  
−
<ul><h5>Optional Deliverables</h5></ul>
+
<div class="oneColumn">
  
 +
<h2>1. Team</h2>
 +
 +
<h3>1.1 Composition</h3>
 +
<p>iGEM teams consist primarily of undergraduate students at an accredited college or university. Teams may also be composed of high school students or community lab members.</p>
 +
 +
 +
<h3>1.2 Roles <a href="https://2016.igem.org/Requirements/Team_roles">[details]</a></h3>
 +
<p>Similar to sports teams, team members have different roles and responsibilities on a team:</p>
 +
 +
<ul>
 +
<li> <b> Students = Team player </b> brainstorm, choose, and execute project idea; students are also responsible for documenting their work</li>
 +
 +
<li><b> Primary and Secondary PI = General manager  </b> individuals in a position of authority (ex: in a university setting, he/she is authorized to have lab space, grants, and hiring privileges) who are <a href="https://2016.igem.org/Requirements/Team_Roles">responsible</a> for team registration, team roster, safety forms, and team fees; at least one PI must be a professor, the other PI must be post-doc or above. See the <a href="https://2016.igem.org/Requirements/Team_Roles">Team Roles</a> page for additional details.</li>
 +
 +
<li><b> Instructor = Head coach </b> provides day-to-day support</li>
 +
 +
<li><b> Student team leader = Team captain</b> point of contact between team, PI, and iGEM HQ</li>
 +
 +
<li><b> Advisor = Assistant coach</b> provides supplementary support </li>
 +
</ul>
 +
 +
<h3>1.3 Sections</h3>
 +
<p>There are three team sections in iGEM 2016:</p>
 +
<ol>
 +
<li>Undergraduate: all student team members are age 23 or younger on March 31, 2016</li>
 +
<li>Overgraduate: one or more student team members are older than 23 on March 31, 2016</li>
 +
<li>High School: all student team members are high school students on March 31, 2016; includes students who graduate from high school spring 2016</li>
 +
</ol>
 +
<p>For details see the <a href="https://2016.igem.org/Requirements/Sections">sections page</a>.</p>
 +
 +
<h3>1.4 Recommendations</h3>
 +
<p>Based on previous competitions, we also strongly recommend the following:</p>
 +
<ul>
 +
<li>Teams should have between 8 and 15 student team members.<span class="pop_why" onclick="which_why='why_teamsize'">?</span></li>
 +
<li>Teams with more than 15 student team members should consider splitting into two teams and taking advantage of the multiple team discount. This also gives a larger team adequate wiki space and presentation time to cover the work generated by more team members.</li>
 +
<li>Teams should be a gender-balanced team, and having approximately as many women as men on a team. <span class="pop_why" onclick="which_why='why_gender'">?</span></li>
 +
</ul>
 +
 +
 +
</div>
 +
 +
<div class="clear_id" id="Registration"></div>
 +
 +
 +
<div class="oneColumn">
 +
<h2>2. Registration</h2>
 +
 +
<h3>2.1 Team Kind <a href="https://2016.igem.org/Requirements/Registration_requirements">[details]</a></h3>
 +
<p>In iGEM 2016, teams will register as one of three team "kinds", and each kind will have different <a href="https://2016.igem.org/Requirements/Registration_requirements">registration requirements</a>. The three team kinds are:</p>
 +
 +
<ol>
 +
<li>Collegiate</li>
 +
<li>High School</li>
 +
<li>Community Lab</li>
 +
</ol>
 +
 +
<h3>2.2 Team Affiliation</h3>
 +
<p>Several schools may combine to form a team, and one school may have several teams. For example, it is normal for a school to have both software and wetlab teams.</p>
 +
 +
<h3>2.3 Fees</h3>
 +
<p>Each team pays a team registration fee, which provides the team with a team wiki, associated materials and support, one presentation slot at the Giant Jamboree, and one poster location at the Giant Jamboree. Additionally, each individual who attends the Giant Jamboree must pay an attendance fee to gain entrance.</p>
 +
<p><a href="https://2016.igem.org/Team_Registration_Fee">Team registration fees</a> for iGEM 2016 are: </p>
 +
<ul>
 +
<li><b>Regular registration:</b> $4500 USD</li>
 +
<li><b>Late registration:</b> $5000 USD</li>
 +
<li><b>Multiple team discount:</b> $1000 USD discount</li>
 +
</ul>
 +
<p><a href="https://2016.igem.org/Jamboree_Attendance_Fee">Giant Jamboree attendance fees</a> for iGEM 2016 are:</p>
 +
<ul>
 +
<li><b>Giant Jamboree attendance:</b> $695 USD per person (PI, instructor, advisor, student)</li>
 +
</ul>
 +
 +
</div>
 +
 +
 +
 +
 +
 +
<div class="clear_id" id="Deliverables"></div>
 +
 +
<div class="oneColumn">
 +
 +
<h2>3. Deliverables</h2>
 +
<p>Every iGEM team is responsible for delivering the following items. These items are used to evaluate your team, in addition to the other <a href="https://2016.igem.org/Judging/Medals">medal</a> and <a href="https://2016.igem.org/Judging/Awards">award criteria</a>. Failure to complete these deliverables may impact your team’s chances at winning prizes during the Giant Jamboree.</p>
 +
 +
<h3>3.1 Required Deliverables</h3>
 +
 +
<ol>
 +
<li>Team Wiki: Teams need to document their project on their Team Wiki page.<span class="pop_why" onclick="which_why='why_teamwiki'">? </span>
 +
<ul>
 +
<li>Due Date: <a href="https://2016.igem.org/Calendar">Oct 19</a><span class="pop_why" onclick="which_why='why_wikifreeze'">? </span></li>
 +
<li><a href="https://2016.igem.org/Requirements/Wiki">[details]</a>
 +
</ul>
 +
</li>
 +
 +
<li>Poster: Each team must present a poster of their project at the Giant Jamboree.<span class="pop_why" onclick="which_why='why_teamposter'">?</span>
 +
<ul>
 +
<li>Due Date: <a href="https://2016.igem.org/Calendar">Giant Jamboree</a></li>
 +
<li><a href="https://2016.igem.org/Requirements/Poster">[details]</a></li>
 +
</ul>
 +
 +
<li>Presentation: Each team has 20 minutes to present their project at the Giant Jamboree. The presentation must be given by a student.<span class="pop_why" onclick="which_why='why_teampresentation'">?
 +
</span>
 +
<ul>
 +
<li>Due Date: <a href="https://2016.igem.org/Calendar">Giant Jamboree</a></li>
 +
<li><a href="https://2016.igem.org/Requirements/Presentation">[details]</a></li>
 +
</ul>
 +
</li>
 +
 +
 +
<li>Project Attribution: Teams need to attribute all of the work done for their project correctly.<span class="pop_why" onclick="which_why='why_projectattribution'">? </span>
 +
<ul>
 +
<li>Due Date: <a href="https://2016.igem.org/Calendar">Wiki Freeze - Oct 19</a></li>
 +
<li><a href="https://2016.igem.org/Team:Example2/Attributions">[details]</a></li>
 +
</ul>
 +
</li>
 +
 +
<li>Registry Part Pages: Teams must create and document Part pages on the Registry for the Parts they make.<span class="pop_why" onclick="which_why='why_newpartpages'">?
 +
</span>
 +
<ul>
 +
<li>Due Date: <a href="https://2016.igem.org/Calendar">Wiki Freeze - Oct 19</a></li>
 +
<li><a href="http://parts.igem.org/Add_a_Part_to_the_Registry">[details]</a></li>
 +
</ul>
 +
</li>
 +
 +
<li>Sample Submission: Submit DNA samples of your new Parts to the Registry.<span class="pop_why" onclick="which_why='why_samplesubmission'">?</span>
 +
<ul>
 +
<li> Due Date: <a href="https://2016.igem.org/Calendar">Oct 21 (send-by date)</a></li>
 +
<li><a href="http://parts.igem.org/DNA_Submission">[details]</a></li>
 +
</ul>
 +
</li>
 +
 +
<li>Safety Forms<span class="pop_why" onclick="which_why='why_safetyforms'">?</span>
 +
 +
<ol style="list-style-type: lower-roman;">
 +
<li>Safety Check-in <a href="https://2016.igem.org/Safety/Check_In">[link]</a>: Due on <a href="https://2016.igem.org/Calendar">Sep 16 (Submit throughout the season)</a></li>
 +
<li>About Our Lab <a href="https://2016.igem.org/Safety/About_Our_Lab">[link]</a>: : Due on <a href="https://2016.igem.org/Calendar">Jul 15</a></li>
 +
<li>About Our Project <a href="https://2016.igem.org/Safety/About_Our_Project">[link]</a>: : Due on <a href="https://2016.igem.org/Calendar">Jul 15</a></li>
 +
<li>Final Safety Form <a href="https://2016.igem.org/Safety/Final_Safety_Form">[link]</a>: Due on <a href="https://2016.igem.org/Calendar">Sep 16</a></li>
 +
</ol>
 +
</li>
 +
 +
<li >Judging Form <span class="pop_why" onclick="which_why='why_judgingforms'">?</span>
 +
<ul>
 +
<li>Due Date: <a href="https://2016.igem.org/Calendar">Oct 14</a></li>
 +
<li><a href="https://igem.org/Team_List.cgi">[link]</a> (go to your team information page and click on the Judging Form link at the top of the page)</li>
 +
</ul>
 +
</li>
 +
<ol>
 +
</div>
 +
 +
 +
<div class="clear_id" id="Rules_of_Conduct"></div>
 +
 +
<div class="oneColumn">
 +
<h2>4. Rules of Conduct</h2>
 +
<p>Conduct in the iGEM Competition is overseen by two committees of external experts: the <a href="https://2016.igem.org/Safety/Committee">Safety Committee</a> and the <a href="https://2016.igem.org/Requirements/Responsible_Conduct">Responsible Conduct Committee</a>. Failure to follow the rules may result in these committees choosing to take disciplinary action against your team, up to and including ineligibility for awards and disqualification from the competition. </p>
 +
 +
 +
<h3>4.1 Safety</h3>
 +
<p>Teams must agree to follow all of the <a href="https://2016.igem.org/Safety/What_is_Safety">Laboratory Safety Rules</a> throughout the competition.<span class="pop_why" onclick="which_why='why_labsafetyrules'">?</span></p>
 +
 +
<h3>4.2 Responsibility</h3>
 +
<p>Every iGEM participant must agree to adhere to the <a href="https://2016.igem.org/Requirements/Responsible_Conduct">Responsible Conduct Committee's Conduct Policy</a> at all times.<span class="pop_why" onclick="which_why='why_conductpolicy'">?</span></p>
 +
 +
<h3>4.3 Honesty</h3>
 +
<p>Be intellectually honest. Describe your accomplishments accurately, and do not take credit for the work of others.<span class="pop_why" onclick="which_why='why_honesty'">?</span></p>
 +
 +
<h3>4.4 Courtesy</h3>
 +
<p>Treat everyone with respect (including teammates, instructors, advisors, other teams, judges, and Headquarters staff).<span class="pop_why" onclick="which_why='why_respect'">?</span></p>
 +
 +
</div>
 +
 +
 +
 +
<div class="clear_id" id="Other"></div>
 +
 +
<div class="oneColumn">
 +
<h2>5. Other</h2>
 +
 +
<h3>5.1 Positive Contribution</h3>
 +
<p>All participants are required to work hard to build positive contributions to society and have lots of fun!</p>
 +
 +
 +
 +
</div>
 +
 +
<script>
 +
 +
$(document).ready(function(){
 +
$(".specific_page_menu").show();
 +
  });
 +
 +
 +
</script>
 
</html>
 
</html>
 +
 +
{{2016Bottom}}

Latest revision as of 14:39, 8 September 2016

NOTE:

All iGEM participants (including students, instructors, and advisors) are expected to read and understand the following iGEM requirements.

Teams that do not comply with the requirements may not be eligible to win awards and prizes. See all details below and be sure to ask iGEM Headquarters if you have any questions.

1. Team

1.1 Composition

iGEM teams consist primarily of undergraduate students at an accredited college or university. Teams may also be composed of high school students or community lab members.

1.2 Roles [details]

Similar to sports teams, team members have different roles and responsibilities on a team:

  • Students = Team player brainstorm, choose, and execute project idea; students are also responsible for documenting their work
  • Primary and Secondary PI = General manager individuals in a position of authority (ex: in a university setting, he/she is authorized to have lab space, grants, and hiring privileges) who are responsible for team registration, team roster, safety forms, and team fees; at least one PI must be a professor, the other PI must be post-doc or above. See the Team Roles page for additional details.
  • Instructor = Head coach provides day-to-day support
  • Student team leader = Team captain point of contact between team, PI, and iGEM HQ
  • Advisor = Assistant coach provides supplementary support

1.3 Sections

There are three team sections in iGEM 2016:

  1. Undergraduate: all student team members are age 23 or younger on March 31, 2016
  2. Overgraduate: one or more student team members are older than 23 on March 31, 2016
  3. High School: all student team members are high school students on March 31, 2016; includes students who graduate from high school spring 2016

For details see the sections page.

1.4 Recommendations

Based on previous competitions, we also strongly recommend the following:

  • Teams should have between 8 and 15 student team members.?
  • Teams with more than 15 student team members should consider splitting into two teams and taking advantage of the multiple team discount. This also gives a larger team adequate wiki space and presentation time to cover the work generated by more team members.
  • Teams should be a gender-balanced team, and having approximately as many women as men on a team. ?

2. Registration

2.1 Team Kind [details]

In iGEM 2016, teams will register as one of three team "kinds", and each kind will have different registration requirements. The three team kinds are:

  1. Collegiate
  2. High School
  3. Community Lab

2.2 Team Affiliation

Several schools may combine to form a team, and one school may have several teams. For example, it is normal for a school to have both software and wetlab teams.

2.3 Fees

Each team pays a team registration fee, which provides the team with a team wiki, associated materials and support, one presentation slot at the Giant Jamboree, and one poster location at the Giant Jamboree. Additionally, each individual who attends the Giant Jamboree must pay an attendance fee to gain entrance.

Team registration fees for iGEM 2016 are:

  • Regular registration: $4500 USD
  • Late registration: $5000 USD
  • Multiple team discount: $1000 USD discount

Giant Jamboree attendance fees for iGEM 2016 are:

  • Giant Jamboree attendance: $695 USD per person (PI, instructor, advisor, student)

3. Deliverables

Every iGEM team is responsible for delivering the following items. These items are used to evaluate your team, in addition to the other medal and award criteria. Failure to complete these deliverables may impact your team’s chances at winning prizes during the Giant Jamboree.

3.1 Required Deliverables

  1. Team Wiki: Teams need to document their project on their Team Wiki page.?
  2. Poster: Each team must present a poster of their project at the Giant Jamboree.?
  3. Presentation: Each team has 20 minutes to present their project at the Giant Jamboree. The presentation must be given by a student.?
  4. Project Attribution: Teams need to attribute all of the work done for their project correctly.?
  5. Registry Part Pages: Teams must create and document Part pages on the Registry for the Parts they make.?
  6. Sample Submission: Submit DNA samples of your new Parts to the Registry.?
  7. Safety Forms?
    1. Safety Check-in [link]: Due on Sep 16 (Submit throughout the season)
    2. About Our Lab [link]: : Due on Jul 15
    3. About Our Project [link]: : Due on Jul 15
    4. Final Safety Form [link]: Due on Sep 16
  8. Judging Form ?
    • Due Date: Oct 14
    • [link] (go to your team information page and click on the Judging Form link at the top of the page)

4. Rules of Conduct

Conduct in the iGEM Competition is overseen by two committees of external experts: the Safety Committee and the Responsible Conduct Committee. Failure to follow the rules may result in these committees choosing to take disciplinary action against your team, up to and including ineligibility for awards and disqualification from the competition.

4.1 Safety

Teams must agree to follow all of the Laboratory Safety Rules throughout the competition.?

4.2 Responsibility

Every iGEM participant must agree to adhere to the Responsible Conduct Committee's Conduct Policy at all times.?

4.3 Honesty

Be intellectually honest. Describe your accomplishments accurately, and do not take credit for the work of others.?

4.4 Courtesy

Treat everyone with respect (including teammates, instructors, advisors, other teams, judges, and Headquarters staff).?

5. Other

5.1 Positive Contribution

All participants are required to work hard to build positive contributions to society and have lots of fun!