Handbook

From 2014.igem.org

(Difference between revisions)
 
(4 intermediate revisions not shown)
Line 23: Line 23:
</td>
</td>
</tr>
</tr>
 +
 +
<tr><td height="25px"></td></tr>
 +
Line 31: Line 34:
</td></tr>
</td></tr>
 +
<tr><td height="25px"></td></tr>
<tr><td>
<tr><td>
-
<h4> Human Practice </h4>
+
<h4> Policy and Practices </h4>
-
<p> Teams are encouraged to help advance the social acceptance of synthetic biology amongst their peers and community. Teams can work on global issues or on local problems they can help solve through synthetic biology. You can conduct surveys, hold open synbio workshops, talk to your local government to promote science, or create informational material in your language, there is no limit!<br>
+
<p> Teams at iGEM are encouraged to pursue innovative approaches to exploring the policy, economic, social, legal, and philosophical landscape of their projects, and synthetic biology broadly. Teams aim to develop approaches that both prepare synthetic biologists for the world they’re working in, and help the world decide how it might best make use of synthetic biology. Teams have undertaken a wide variety of approaches. You can see some exemplary projects here in the <a href="https://2014.igem.org/Tracks/Policy_Practices#Exemplar Projects"> Exemplar projects</a> section of the track page.<br>
-
<i> Example </i> - <a href="https://2012.igem.org/Team:Colombia"> https://2012.igem.org/Team:Colombia</a> </p>
+
</td></tr>
</td></tr>
-
 
+
<tr><td height="25px"></td></tr>
<tr><td>
<tr><td>
Line 64: Line 67:
</td></tr>
</td></tr>
-
 
+
<tr><td height="25px"></td></tr>
<tr><td>
<tr><td>
<h3> Documentation and presentation</h3>
<h3> Documentation and presentation</h3>
<p> Document your project on your website and present your poster and work at the Giant Jamboree. Additional information will be provided as we get closer to the jamboree.<br>
<p> Document your project on your website and present your poster and work at the Giant Jamboree. Additional information will be provided as we get closer to the jamboree.<br>
-
See what other teams have done - https://igem.org/Team_Wikis?year=2013 See previous posters, presentations and awards here -
+
See what other teams have done - <a href="https://igem.org/Team_Wikis?year=2013"> https://igem.org/Team_Wikis?year=2013 </a>
-
https://igem.org/Results?year=2013&region=All&division=igem</p>
+
<br>
 +
See previous posters, presentations and awards here -
 +
<a href="https://igem.org/Results?year=2013&region=All&division=igem"> https://igem.org/Results?year=2013&region=All&division=igem </a> </p>
<ul>  
<ul>  
Line 83: Line 88:
<i> More information </i> -<a href="https://2014.igem.org/Wiki_How-To">  https://2014.igem.org/Wiki_How-To</a>  </li>  
<i> More information </i> -<a href="https://2014.igem.org/Wiki_How-To">  https://2014.igem.org/Wiki_How-To</a>  </li>  
</td></tr>
</td></tr>
 +
 +
 +
<tr><td height="25px"></td></tr>
 +
<tr><td>
<tr><td>
Line 99: Line 108:
</td></tr>
</td></tr>
 +
 +
<tr><td height="25px"></td></tr>
</table>
</table>

Latest revision as of 22:12, 6 August 2014

Project

iGEM projects are very diverse! Each team must strive to cooperate and collaborate with their local community and the global iGEM community.

  • Make a positive contribution
    Regardless of the focus or background, all teams must strive to make a positive contribution to the world or the community around them.
  • Select a track
    iGEM has 15 tracks from where to choose from. Choosing a track will help you focus your project towards one area. Some tracks have specific requirements, be sure to read the details for each one.
    More information - https://2014.igem.org/Tracks
  • Collaboration
    Teams should communicate with one another, help each other and overall strive for a community environment among participants.
  • Attributions
    Be clear about who did what in your project. If you received help or advice from someone outside the team, be sure to document it. If you are using another team’s biobrick, be sure to mention it as well.
    Example - https://2011.igem.org/Team:Imperial_College_London/Team

Safety

Teams are responsible for their own safety, in and outside the lab. Filling the Safety Form and the About Our Lab form are two of the requirements each team must fill. Also, make sure you document your lab conditions and the overall safety considerations regarding your project and its impact.
More information - https://2014.igem.org/Safety

Policy and Practices

Teams at iGEM are encouraged to pursue innovative approaches to exploring the policy, economic, social, legal, and philosophical landscape of their projects, and synthetic biology broadly. Teams aim to develop approaches that both prepare synthetic biologists for the world they’re working in, and help the world decide how it might best make use of synthetic biology. Teams have undertaken a wide variety of approaches. You can see some exemplary projects here in the Exemplar projects section of the track page.

Parts

iGEM maintains and operates the Registry of Standard parts with over 20,000 genetic parts. Teams are strongly encouraged to submit the parts they have developed to the iGEM Registry, and will need to do so to be considered for certain special awards.
Note: Some tracks, like Policy and Practices, are not required to submit parts.

Documentation and presentation

Document your project on your website and present your poster and work at the Giant Jamboree. Additional information will be provided as we get closer to the jamboree.
See what other teams have done - https://igem.org/Team_Wikis?year=2013
See previous posters, presentations and awards here - https://igem.org/Results?year=2013&region=All&division=igem

  • Poster
    Teams need to create a scientific poster that is clear and is self-explanatory. Be sure to include the highlights of your project and your achievements.
  • Presentation
    You will have 20 minutes to present your project in front of a live audience. You can use visual support to help explain your results.
  • Wiki
    Your team wiki will present your project and team to the world. Make sure information is clear, easy to find and well documented.
    More information - https://2014.igem.org/Wiki_How-To

Project evaluation