Difference between revisions of "Requirements"

Line 70: Line 70:
  
 
<h3>3. Deliverables</h3>
 
<h3>3. Deliverables</h3>
<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://2015.igem.org/Judging/Medals">medal</a> and <a href="https://2015.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>
+
<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>
  
 
<ul><h5>3.1 Required Deliverables</h5></ul>
 
<ul><h5>3.1 Required Deliverables</h5></ul>
Line 76: Line 76:
 
<ol>
 
<ol>
 
<li>Team Wiki <a href="https://2015.igem.org/Wiki_Requirements">[details]</a>: Teams need to document their project on their Team Wiki page.<span class="pop_why" onclick="which_why='why_teamwiki'">?
 
<li>Team Wiki <a href="https://2015.igem.org/Wiki_Requirements">[details]</a>: Teams need to document their project on their Team Wiki page.<span class="pop_why" onclick="which_why='why_teamwiki'">?
</span></li> <ul>Wiki Freeze Date: <a href="https://2015.igem.org/Calendar_of_Events">October XX, 2016</a><span class="pop_why" onclick="which_why='why_wikifreeze'">?
+
</span></li> <ul>Wiki Freeze Date: <a href="https://2016.igem.org/Timeline">October XX, 2016</a><span class="pop_why" onclick="which_why='why_wikifreeze'">?
 
</span></ul>
 
</span></ul>
  
 
<li>Poster <a href="https://2016.igem.org/Poster_and_Presentation">[details]</a>: Each team must present a poster of their project at the Giant Jamboree.<span class="pop_why" onclick="which_why='why_teamposter'">?
 
<li>Poster <a href="https://2016.igem.org/Poster_and_Presentation">[details]</a>: Each team must present a poster of their project at the Giant Jamboree.<span class="pop_why" onclick="which_why='why_teamposter'">?
</span></li> <ul>Poster PDF Due: <a href="https://2015.igem.org/Calendar_of_Events">October XX, 2016</a></ul>
+
</span></li> <ul>Poster PDF Due: <a href="https://2016.igem.org/Timeline">October XX, 2016</a></ul>
  
 
<li>Presentation <a href="https://2016.igem.org/Poster_and_Presentation">[details]</a>: 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'">?
 
<li>Presentation <a href="https://2016.igem.org/Poster_and_Presentation">[details]</a>: 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'">?
Line 91: Line 91:
 
</span></li>
 
</span></li>
  
<ul>Sample Submission Mailing Deadline: <a href="https://2015.igem.org/Calendar_of_Events">October XX, 2016</a></ul>
+
<ul>Sample Submission Mailing Deadline: <a href="https://2016.igem.org/Timeline">October XX, 2016</a></ul>
  
 
<li>Registry Part Pages <a href="http://parts.igem.org/Add_a_Part_to_the_Registry">[details]</a>: Teams must create and document Part pages on the Registry for the Parts they make.<span class="pop_why" onclick="which_why='why_newpartpages'">?
 
<li>Registry Part Pages <a href="http://parts.igem.org/Add_a_Part_to_the_Registry">[details]</a>: Teams must create and document Part pages on the Registry for the Parts they make.<span class="pop_why" onclick="which_why='why_newpartpages'">?
Line 100: Line 100:
  
 
<ol style="list-style-type: lower-roman;">
 
<ol style="list-style-type: lower-roman;">
<li>Safety Check-in <a href="https://2015.igem.org/Safety/Check_In">[link]</a>: Due on <a href="https://2015.igem.org/Calendar_of_Events">June XX, 2016</a></li>
+
<li>Safety Check-in <a href="https://2016.igem.org/Safety/Check_In">[link]</a>: Due on <a href="https://2016.igem.org/Timeline">June XX, 2016</a></li>
<li>About Our Lab <a href="https://2015.igem.org/Safety/About_Our_Lab">[link]</a>: : Due on <a href="https://2015.igem.org/Calendar_of_Events">July XX, 2016</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/Timeline">July XX, 2016</a></li>
<li>About Our Project <a href="https://2015.igem.org/Safety/About_Our_Project">[link]</a>: : Due on <a href="https://2015.igem.org/Calendar_of_Events">July XX, 2016</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/Timeline">July XX, 2016</a></li>
<li>Final Safety Form <a href="https://2015.igem.org/Safety/Final_Safety_Form">[link]</a>: Due on <a href="https://2015.igem.org/Calendar_of_Events">August XX, 2016</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/Timeline">August XX, 2016</a></li>
 
</ol>
 
</ol>
  
 
<li value=8>Judging Form <a href="https://igem.org/Team_Judging?year=2015">[link]</a><span class="pop_why" onclick="which_why='why_judgingforms'">?
 
<li value=8>Judging Form <a href="https://igem.org/Team_Judging?year=2015">[link]</a><span class="pop_why" onclick="which_why='why_judgingforms'">?
 
</span></li>
 
</span></li>
<ul>Judging Form Due: <a href="https://2015.igem.org/Calendar_of_Events">September XX, 2016</a><ul>
+
<ul>Judging Form Due: <a href="https://2016.igem.org/Timeline">September XX, 2016</a><ul>
 
</ol>
 
</ol>
 
</ol></ul>
 
</ol></ul>

Revision as of 20:05, 15 December 2015

This page is under active development and is in draft form. Nothing posted here is finalized.





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.

    • Primary and Secondary PI = General manager
    • Instructor = Head coach
    • Student team leader = Team captain
    • Advisor = Assistant coach
    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

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

    Giant Jamboree attendance fees for iGEM 2016 are:

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

    2.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 consider being a gender-balanced team, and having approximately as many women as men on a team. ?


    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

    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 iGEM’s Laboratory Safety Rules (link to: page doesn’t exist yet) throughout the competition.?

      4.2 Responsibility

      Every iGEM participant must agree to adhere to the Responsible Conduct Committee's Conduct Policy (link to: page doesn’t exist yet) 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!