Difference between revisions of "Competition/Deliverables"

 
(56 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
{{Main2017}}
 
{{Main2017}}
−
 
 
<html>
 
<html>
 +
 +
  
  
 
<div class="column full_size">
 
<div class="column full_size">
  
−
<h2>4. Deliverables</h2>
+
<h1>4. Deliverables</h1>
−
<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>
+
</div>
 +
 
 +
 
 +
<div class="column full_size  navigation_support">
 +
 
 +
<a href="https://2017.igem.org/Competition">  
 +
<div class="title_extra main_item" >
 +
COMPETITION HUB /
 +
</div>  
 +
</a>  
  
−
<h3>4.1 Required Deliverables</h3>
+
<div class="title_extra support_item">  
 +
REQUIREMENTS:
 
</div>
 
</div>
 +
 +
</div>
 +
 +
<div class="column full_size navigation_support">
 +
 +
<a href="https://2017.igem.org/Competition/Rules_of_Conduct">
 +
<div class="navigation_button arrow_navigation previous_item"></div>
 +
<div class="title_extra" > Previous: Rules of Conduct </div>
 +
</a>
 +
 +
<a href="https://2017.igem.org/Competition/Team_Requirements">
 +
<div class="navigation_button"  id="Team_Requirements_button">
 +
1
 +
</div>
 +
<div class="title_extra" > Team Requirements </div>
 +
</a>
 +
 +
<a href="https://2017.igem.org/Competition/Registration">
 +
<div class="navigation_button " >
 +
2 
 +
</div>
 +
<div class="title_extra"> Registration </div>
 +
</a>
 +
 +
<a href="https://2017.igem.org/Competition/Rules_of_Conduct">
 +
<div class="navigation_button " >
 +
3
 +
</div>
 +
<div class="title_extra"> Rules of Conduct </div>
 +
</a>
 +
 +
 +
<a href="https://2017.igem.org/Competition/Deliverables">
 +
<div class="navigation_button active_navigation_button" >
 +
4
 +
</div>
 +
<div class="title_extra"> Deliverables </div>
 +
</a>
 +
 +
 +
<a href="https://2017.igem.org/Competition/Tracks">
 +
<div class="navigation_button" >
 +
5
 +
</div>
 +
<div class="title_extra">Tracks </div>
 +
</a>
 +
 +
 +
<a href="https://2017.igem.org/Competition#PosContribution">
 +
<div class="navigation_button" >
 +
6
 +
</div>
 +
<div class="title_extra">Positive Contribution </div>
 +
</a>
 +
 +
<a href="https://2017.igem.org/Competition/Tracks">
 +
<div class="navigation_button arrow_navigation next_item"> </div>
 +
<div class="title_extra" > Next: Tracks</div>
 +
</a>
 +
 +
</div>
 +
 +
 +
 +
 +
<div class="column full_size">
 +
<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://2017.igem.org/Judging/Medals">medal</a> and <a href="https://2017.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>
 +
 +
</div>
 +
 +
<div class="clear extra_space"></div>
 +
 +
<div class="column full_size">
 +
<h2>4.1 Required Deliverables</h2>
 +
</div>
 +
  
 
<div class="column fourth_size">
 
<div class="column fourth_size">
−
<p>Team Wiki: Teams need to document their project on their Team Wiki page. Your Team Wiki page is the public face of your project and serves as a public record of your hard work. Since it is hosted on the iGEM servers, no content will ever get lost and you will be able to share the website with people after the competition has ended.<br>
+
<div class="highlight gray turquoise_top">
−
Due Date: Nov 1</p>
+
 
−
</div>
+
<h3>1. Team Wiki</h3>
−
+
<h5> Due Date: November 1 </h5>
 +
<p> Teams need to document their project on their Wiki page. This page is the public face of your project. Since it is hosted on the iGEM servers, no content will ever get lost and you will still be able to share the website after the competition.
 +
</p>
 +
<div class="button">
 +
<a href="https://2017.igem.org/Competition/Deliverables/Wiki">
 +
TEAM WIKI
 +
</a>
 +
</div>
 +
</div>
 +
</div>
 +
 
 +
 
 +
 
 
<div class="column fourth_size">
 
<div class="column fourth_size">
−
<p>Team Poster: Each team is given one poster slot and the poster cannot exceed these dimensions: 4 ft. X 4 ft. (1.22 m X 1.22 m). Students must present the poster during the scheduled Poster Sessions at the Giant Jamboree.<br>
+
<div class="highlight gray turquoise_top ">
−
Due Date: Nov 1</p>
+
<h3> 2. Project Attribution</h3>
 +
<h5>Due Date: November 1 </h5>
 +
<p>All of the work done in your project must be attributed correctly on your team's Attributions page. You must clearly state the work that was done by the students on your team and note any work that was done by people outside of your team.
 +
</p>
 +
 
 +
<div class="button">
 +
<a href="https://2017.igem.org/Competition/Deliverables/Project_Attributions">
 +
ATTRIBUTION
 +
</a>
 +
</div>
 +
</div>
 
</div>
 
</div>
  
  
−
<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>
 
  
 +
 +
<div class="column fourth_size">
 +
<div class="highlight gray turquoise_top ">
 +
<h3>3. Team Poster</h3>
 +
<h5>Due Date: Giant Jamboree</h5>
 +
<p> Each team is given one poster slot and the poster cannot exceed these dimensions: 4 ft. X 4 ft. (1.22 m X 1.22 m). Students must present the poster during the scheduled Poster Sessions at the Giant Jamboree.</p>
  
−
<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>
+
<div class="button">
−
<ul>
+
<a href="https://2017.igem.org/Competition/Deliverables/Poster">
−
<li>Due Date: <a href="https://2016.igem.org/Calendar">Wiki Freeze - Oct 19</a></li>
+
POSTER
−
<li><a href="https://2016.igem.org/Team:Example2/Attributions">[details]</a></li>
+
</a>
−
</ul>
+
</div>
−
</li>
+
</div>
 +
</div>
  
−
<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>
+
<div class="column fourth_size">
 +
<div class="highlight gray turquoise_top ">
 +
<h3>4. Team Presentation</h3>
 +
<h5> Due Date: Giant Jamboree</h5>
 +
<p>Each team is given one 20-minute presentation slot. Each team will be randomly assigned a presentation time during the Giant Jamboree. The presentation must be given by a student on the team roster. </p>
 +
 +
<div class="button">
 +
<a href="https://2017.igem.org/Competition/Deliverables/Presentation">
 +
PRESENTATION
 +
</a>
 +
</div>
 +
</div>
 +
</div>
  
−
<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>
+
<div class="clear"></div>
−
<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>
+
<div class="column fourth_size">
−
</ul>
+
<div class="highlight gray turquoise_top ">
−
</li>
+
<h3>5. Safety Forms </h3>
−
<ol>
+
<h5>Due Dates: June 30, Oct 2</h5>
 +
<p>All teams are expected to follow a high standard of safe and responsible biological engineering. Teams must submit various safety forms over the course of the competition (Safety Check-In</a>, About Our Lab, About Our Project, New Parts and Final Safety Form). Safety Check-In opens June 2; Safety Form Parts 1-3 are to be complete by Friday, June 30, 2017; Safety Form Part 4-5 are to be complete by Monday, October 2, 2017</p>
 +
<div class="button">
 +
<a href="https://2017.igem.org/Safety/Check_In"> CHECK IN FORM
 +
</a>
 
</div>
 
</div>
 +
 +
<div class="button">
 +
<a href="https://2017.igem.org/Safety/Final_Safety_Form"> SAFETY FORM
 +
</a>
 +
</div>
 +
</div>
 +
</div>
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
<div class="column fourth_size">
 +
<div class="highlight gray turquoise_top ">
 +
<h3>6. Judging Form </h3>
 +
<h5>Due Date: October 27</h5>
 +
 +
<p>Since iGEM is a competition, teams will be judged on their projects during the Giant Jamboree. Teams fill out their own Judging Form. The Judging Form will be sent to the judges so they can evaluate your team for prizes and awards.</p>
 +
 +
<div class="button">
 +
<a href="https://2017.igem.org/Competition/Deliverables/Judging_Form">
 +
JUDGING FORM
 +
</a>
 +
</div>
 +
</div>
 +
</div>
 +
 +
 +
 +
<div class="column fourth_size">
 +
<div class="highlight gray turquoise_top ">
 +
<h3>7. Registry Part Pages</h3>
 +
<h5>Due Date: November 1</h5>
 +
<p>Teams must create and document Part pages on the Registry for the Parts they make. While your Team Wiki exists to document your entire project, the Registry Part Page(s) exist to specifically document your new part(s). These pages should be very detailed.  </p>
 +
 +
<div class="button">
 +
<a href="https://2017.igem.org/Competition/Deliverables/Part_Pages">
 +
PART PAGES
 +
</a>
 +
</div>
 +
</div>
 +
</div>
 +
 +
 +
 +
<div class="column fourth_size">
 +
<div class="highlight gray turquoise_top ">
 +
<h3>8. Sample Submission</h3>
 +
<h5>Mail By Date: October 27</h5>
 +
<p>Submit DNA samples of your new Parts to the Registry. Teams are asked to submit samples of their new Parts to the Registry to help make the Registry better each year. Teams must follow our DNA Submission Guidelines to qualify for medals. </p>
 +
 +
<div class="button">
 +
<a href="https://2017.igem.org/Competition/Deliverables/Sample_Submission">
 +
DNA SUBMISSION
 +
</a>
 +
</div>
 +
</div>
 +
</div>
 +
 +
 +
  
 
</html>
 
</html>

Latest revision as of 18:01, 28 June 2017

MENU
Loading...

4. Deliverables

COMPETITION HUB /
REQUIREMENTS:
Previous: Rules of Conduct
Team Requirements
2
Registration
3
Rules of Conduct
4
Deliverables
5
Tracks
6
Positive Contribution
Next: Tracks

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.

4.1 Required Deliverables

1. Team Wiki

Due Date: November 1

Teams need to document their project on their Wiki page. This page is the public face of your project. Since it is hosted on the iGEM servers, no content will ever get lost and you will still be able to share the website after the competition.

TEAM WIKI

2. Project Attribution

Due Date: November 1

All of the work done in your project must be attributed correctly on your team's Attributions page. You must clearly state the work that was done by the students on your team and note any work that was done by people outside of your team.

ATTRIBUTION

3. Team Poster

Due Date: Giant Jamboree

Each team is given one poster slot and the poster cannot exceed these dimensions: 4 ft. X 4 ft. (1.22 m X 1.22 m). Students must present the poster during the scheduled Poster Sessions at the Giant Jamboree.

POSTER

4. Team Presentation

Due Date: Giant Jamboree

Each team is given one 20-minute presentation slot. Each team will be randomly assigned a presentation time during the Giant Jamboree. The presentation must be given by a student on the team roster.

PRESENTATION

5. Safety Forms

Due Dates: June 30, Oct 2

All teams are expected to follow a high standard of safe and responsible biological engineering. Teams must submit various safety forms over the course of the competition (Safety Check-In, About Our Lab, About Our Project, New Parts and Final Safety Form). Safety Check-In opens June 2; Safety Form Parts 1-3 are to be complete by Friday, June 30, 2017; Safety Form Part 4-5 are to be complete by Monday, October 2, 2017

CHECK IN FORM
SAFETY FORM

6. Judging Form

Due Date: October 27

Since iGEM is a competition, teams will be judged on their projects during the Giant Jamboree. Teams fill out their own Judging Form. The Judging Form will be sent to the judges so they can evaluate your team for prizes and awards.

JUDGING FORM

7. Registry Part Pages

Due Date: November 1

Teams must create and document Part pages on the Registry for the Parts they make. While your Team Wiki exists to document your entire project, the Registry Part Page(s) exist to specifically document your new part(s). These pages should be very detailed.

PART PAGES

8. Sample Submission

Mail By Date: October 27

Submit DNA samples of your new Parts to the Registry. Teams are asked to submit samples of their new Parts to the Registry to help make the Registry better each year. Teams must follow our DNA Submission Guidelines to qualify for medals.

DNA SUBMISSION