Team:Duke/Attributions

HOME
TEAM
Team Members
Team Advisors
Collaborations
PROJECT
Description
Design
Experiments
Notebook
Model
Results
Attributions
PARTS
Parts Overview
Basic Parts
SAFETY
Human Practices
AWARDS
Education & Engagement
Model
JUDGING FORM ⇗

Adam






Acknowledgements

General Support

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.


Design Support

Original designs and concepts were created by our team members, building off the original G-block designs 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 students.


Wiki Support

Text and images from the 2016 Duke iGEM Wiki's "Project Description" were integrated into the the 2018 Duke iGEM Wiki.

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.

Template:Duke/footer






Attributions

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.

Bronze Medal Criterion #3

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.

Please see the <a href="https://2018.igem.org/Judging/Medals">Medals requirements page</a> for more details.



What should this page contain?

  • Clearly state what the team accomplished
  • General Support
  • Project support and advice
  • Fundraising help and advice
  • Lab support
  • Difficult technique support
  • Project advisor support
  • Wiki support
  • Presentation coaching
  • Human Practices support
  • Thanks and acknowledgements for all other people involved in helping make a successful iGEM team

Tell us if your institution teaches an iGEM or synthetic biology class and when you started your project:

  • Does your institution teach an iGEM or synthetic biology course?
  • When did you start this course?
  • Are the syllabus and course materials freely available online?
  • When did you start your brainstorming?
  • When did you start in the lab?
  • When did you start working on your project?


Inspiration

Take a look at what other teams have done:


Why is this page needed?

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.

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.

Can we base our project on a previous one?

Yes! You can have a project based on a previous team, or based on someone else's idea, as long as you state this fact very clearly and give credit for the original project.


</html>