Difference between revisions of "Team:Duke/Attributions"

 
(9 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
{{Duke}}
 
{{Duke}}
 
<html>
 
<html>
 +
 +
 +
<br> <br> <br>
 +
  
  
Line 10: Line 14:
 
<h2> General Support </h2>
 
<h2> General Support </h2>
  
<p> We would like to thank all of the members of the Lynch Lab for their general assistance. All troubleshooting and experiments not mentioned below were done by team members. However, procedural and technical questions, corrections, and guidance were addressed by the Lynch Lab members. We also, would not have been able to do half as much without the full support of the Pratt School of Engineering, the Duke Bass Connections program, and Duke University. </p>
+
<p> We would like to thank all of the members of the Lynch Lab for letting us work in their lab space. Mike Lynch provided support as an advisor and Adim Moreb and John Decker provided support on difficult techniques. The full support of the Pratt School of Engineering, the Duke Bass Connections program, and Duke University in making iGEM a priority allowed us to get more done than we would have otherwise.
 +
 
 +
If not mentioned below, it was done independently by members of the team. For instance, we coached ourselves for our presentation. </p>
 
<br>
 
<br>
  
 
<h2> Design Support </h2>
 
<h2> Design Support </h2>
  
<p> Original design and concepts were created by our team members. Technical review and questions were answered with help from Adim Moreb, John Decker, and Mike Lynch from the Lynch Lab.</p>
+
<p> Experimental designs were done by our team members, building off the original G-block designs and progress of the 2016 Duke iGEM team. Technical review and questions were answered with help from Adim Moreb, John Decker, and Mike Lynch from the Lynch Lab.</p>
<p> All experiments were carried out by students. </p>
+
<p> All experiments were carried out by student members of the team. </p>
 
<br>
 
<br>
  
 +
<h2> Wiki Support </h2>
 +
 +
Text and images from the 2016 Duke iGEM Wiki's "Project Description" page were integrated into the the 2018 Duke iGEM Wiki, as our work is a continuation of that project. Components of the 2017 Duke iGEM Wiki's "Attribution" and "Advisors" pages were integrated into the 2018 Duke iGEM Wiki, as our advisors and funding sources have remained more or less unchanged. Text from the 2017 Duke iGEM Wiki's page on community outreach to the Marbles Kids Museum was used in the 2018 Duke iGEM Wiki because we visit them annually and the content of our outreach remained unchanged from the previous year. Code for slideshows used in the "Team Members" and "Team Advisors" pages utilized code from the tutorial <a href="https://www.w3schools.com/howto/howto_js_slideshow.asp"> howto_js_slideshow </a>.
 
<h2> Funding Support </h2>
 
<h2> Funding Support </h2>
  
Line 54: Line 63:
 
<p> We would like to extend our thanks to all of these people who helped us with our project. Without their help, our project would not have been possible. </p> </center>
 
<p> We would like to extend our thanks to all of these people who helped us with our project. Without their help, our project would not have been possible. </p> </center>
 
</div>
 
</div>
 
</div>
 
</html>
 
{{Duke/footer}}
 
 
 
 
 
<div class="clear"></div>
 
 
 
 
 
 
 
<div class="column full_size">
 
<h1>Attributions</h1>
 
<p>This page is your opportunity to explain what parts of your project you did and what was done by technicians, advisers, etc. This requirement is not about literature references - these can and should be displayed throughout your wiki.
 
</p>
 
 
<h3> Bronze Medal Criterion #3</h3>
 
<p> All of the work done in your project must be attributed correctly on this 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, including the host labs, advisors, instructors, and individuals not on the team roster.
 
<br><br>
 
Please see the <a href="https://2018.igem.org/Judging/Medals">Medals requirements page</a> for more details.</p>
 
</div>
 
 
 
<div class="clear extra_space"></div>
 
 
 
 
<div class="column third_size">
 
<h3> What should this page contain?</h3>
 
 
<ul>
 
<li>Clearly state what the team accomplished</li>
 
<li>General Support</li>
 
<li>Project support and advice</li>
 
<li>Fundraising help and advice</li>
 
<li>Lab support</li>
 
<li>Difficult technique support</li>
 
<li>Project advisor support</li>
 
<li>Wiki support</li>
 
<li>Presentation coaching</li>
 
<li>Human Practices support</li>
 
<li> Thanks and acknowledgements for all other people involved in helping make a successful iGEM team</li>
 
</ul>
 
</div>
 
 
<div class="column third_size">
 
<p>Tell us if your institution teaches an iGEM or synthetic biology class and when you started your project:</p>
 
<ul>
 
<li>Does your institution teach an iGEM or synthetic biology course?</li>
 
<li>When did you start this course?</li>
 
<li>Are the syllabus and course materials freely available online?</li>
 
<li>When did you start your brainstorming?</li>
 
<li>When did you start in the lab?</li>
 
<li>When did you start working on  your project?</li>
 
</ul>
 
</div>
 
 
 
<div class="column third_size">
 
<div class="highlight decoration_A_full">
 
 
<h3>Inspiration</h3>
 
<p>Take a look at what other teams have done:</p>
 
<ul>
 
<li><a href="https://2011.igem.org/Team:Imperial_College_London/Team">2011 Imperial College London</a> (scroll to the bottom)</li>
 
<li><a href="https://2014.igem.org/Team:Exeter/Attributions">2014 Exeter </a></li>
 
<li><a href="https://2014.igem.org/Team:Melbourne/Attributions">2014 Melbourne </a></li>
 
<li><a href="https://2014.igem.org/Team:Valencia_Biocampus/Attributions">2014 Valencia Biocampus</a></li>
 
</ul>
 
</div>
 
</div>
 
 
 
 
<div class="clear extra_space"></div>
 
 
<div class="column two_thirds_size">
 
<h3> Why is this page needed? </h3>
 
<p>The Attribution requirement helps the judges know what you did yourselves and what you had help with. We don't mind if you get help with difficult or complex techniques, but you must report what work your team did and what work was done by others.</p>
 
<p>
 
For example, you might choose to work with an animal model during your project. Working with animals requires getting a license and applying far in advance to conduct certain experiments in many countries. This is difficult to achieve during the course of a summer, but much easier if you can work with a postdoc or PI who has the right licenses.</p>
 
</div>
 
 
<div class="column third_size">
 
<div class="highlight decoration_B_full">
 
<h3> Can we base our project on a previous one? </h3>
 
<p>Yes! You can have a project based on a previous team, or based on someone else's idea, <b>as long as you state this fact very clearly and give credit for the original project.</b> </p>
 
</div>
 
</div>
 
 
 
 
</html>
 

Latest revision as of 03:54, 18 October 2018






Acknowledgements

General Support

We would like to thank all of the members of the Lynch Lab for letting us work in their lab space. Mike Lynch provided support as an advisor and Adim Moreb and John Decker provided support on difficult techniques. The full support of the Pratt School of Engineering, the Duke Bass Connections program, and Duke University in making iGEM a priority allowed us to get more done than we would have otherwise. If not mentioned below, it was done independently by members of the team. For instance, we coached ourselves for our presentation.


Design Support

Experimental designs were done by our team members, building off the original G-block designs and progress of the 2016 Duke iGEM team. Technical review and questions were answered with help from Adim Moreb, John Decker, and Mike Lynch from the Lynch Lab.

All experiments were carried out by student members of the team.


Wiki Support

Text and images from the 2016 Duke iGEM Wiki's "Project Description" page were integrated into the the 2018 Duke iGEM Wiki, as our work is a continuation of that project. Components of the 2017 Duke iGEM Wiki's "Attribution" and "Advisors" pages were integrated into the 2018 Duke iGEM Wiki, as our advisors and funding sources have remained more or less unchanged. Text from the 2017 Duke iGEM Wiki's page on community outreach to the Marbles Kids Museum was used in the 2018 Duke iGEM Wiki because we visit them annually and the content of our outreach remained unchanged from the previous year. Code for slideshows used in the "Team Members" and "Team Advisors" pages utilized code from the tutorial howto_js_slideshow .

Funding Support

None of our research would have been possible without the financial support of the Lord Foundation, the Duke Bass Connections Program, IDT (Integrated DNA Technologies), Duke Undergraduate Research Support Office


Lord Foundation
Bass Connections Logo
Duke University

We would like to extend our thanks to all of these people who helped us with our project. Without their help, our project would not have been possible.