|
|
| Line 4: |
Line 4: |
| | | | |
| | <!--Attributions content --> | | <!--Attributions content --> |
| - | <tr><td > <h3> iGEM Team attributions page</h3></td> | + | <tr><td > <h3>Attributions</h3></td> |
| | <td ></td > | | <td ></td > |
| | <td > <h3> </h3></td> | | <td > <h3> </h3></td> |
| Line 10: |
Line 10: |
| | | | |
| | <tr> | | <tr> |
| - | <td width="45%" valign="top" colspan="3"> | + | <td valign="top" colspan="3"> |
| - | | + | <p><b><a href="https://www.dna20.com/" target="_blank">DNA2.0 </a></b><br> |
| - | <p> | + | DNA2.0 provided us with invaluable support, both through reagents and expertise. They supplied us with numerous fluorescent and chromogenic proteins from their ProteinPaintbox for our early prototyping and performed the complete assembly of our final tri-color plasmid pools. Additionally, they also quantified individual promoter-RBS strengths.</p> |
| - | Each team must clearly attribute work done by the student team members on this page. The team must distinguish work done by the students from work done by others, including the host labs, advisors, instructors, and individuals not on the team roster.
| + | |
| - | </p> | + | |
| | | | |
| | </td> | | </td> |
| - |
| |
| - |
| |
| - |
| |
| - | <tr>
| |
| - | <td > <h3> Why do we have this requirement?</h3></td>
| |
| - | <td></td>
| |
| - | <td > <h3>Attribution Template </h3></td>
| |
| - | </tr>
| |
| - |
| |
| - | <tr>
| |
| - |
| |
| - | <td width="45%" valign="top">
| |
| - |
| |
| - | <p>
| |
| - | We have this requirement to help 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, just be sure to report the work your team did and the work that 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 something that 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>
| |
| - |
| |
| - | <p>
| |
| - | A great example of complete attribution comes from the <a href="https://2011.igem.org/Team:Imperial_College_London/Team">Imperial College London 2011 team</a> (scroll down to the bottom of their team page to see attributions).
| |
| - | </p>
| |
| - |
| |
| - | </td>
| |
| - | <td></td>
| |
| - | <td width="45%" valign="top">
| |
| - | <p>
| |
| - | Here are some of the fields we recommend you have on this page. If there are other areas not listed below, but applicable to your team/project, please feel free to also list them on your attributions page. Please feel free to remove any areas not applicable to your project.
| |
| - | </p>
| |
| - |
| |
| - | <ol>
| |
| - | <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>Policy & Practices support</li>
| |
| - |
| |
| - | <li> Thanks and acknowledgements for all other people involved in helping make a successful iGEM team.</li>
| |
| - |
| |
| - | </ol>
| |
| - | </td>
| |
| - |
| |
| - |
| |
| | </tr> | | </tr> |
| | </table> | | </table> |
| | </html> | | </html> |
"
