Difference between revisions of "Team:Leicester/Attributions"
Line 1: | Line 1: | ||
{{Leicester}} | {{Leicester}} | ||
− | |||
− | <html | + | <html lang="en"> |
− | + | <body> | |
− | + | ||
− | + | <div class="container" style="padding-bottom: 50px; padding-top:2px;"> | |
− | + | <div class="row"> | |
− | + | <div class="col-sm-2" style="padding-left:0px; padding right:30px;"> | |
− | + | <ul class="nav nav-pills nav-stacked" style="margin-left:0px;"> | |
− | + | <li class="active"><a href="#">Interlab Study: Measurement</a></li> | |
− | + | <li><a href="#">Methodology</a></li> | |
− | + | <li><a href="#">Results</a></li> | |
− | + | </ul> | |
− | + | </div> | |
− | + | <div class="col-sm-8" style="color:#fff; background-color: #3498db; border-radius: 50px; border-top-right-radius: 0px; border-bottom-left-radius: 0px; padding-left:30px; padding-right:30px; padding-top:30px; padding-bottom:20px; box-shadow: 10px 10px 50px #000000;"> | |
− | + | <h2> Attributions</h2> | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | # | + | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | <h2> Attributions</h2> | + | |
<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> | <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> | ||
Line 78: | Line 48: | ||
</ul> | </ul> | ||
− | + | </div> | |
− | + | <div class="col-sm-2"> | |
− | < | + | <a class="twitter-timeline" |
− | + | data-widget-id="327381807010025474" | |
− | + | href="https://twitter.com/iGEMLeicester" | |
− | + | width="80" | |
− | < | + | height="300"> |
− | + | Tweets by @iGEMLeicester | |
− | </ | + | </a> |
− | + | <script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+"://platform.twitter.com/widgets.js";fjs.parentNode.insertBefore(js,fjs);}}(document,"script","twitter-wjs"); </script> | |
+ | </div> | ||
+ | |||
+ | </div> | ||
+ | |||
+ | |||
+ | </div> | ||
</div> | </div> | ||
+ | <p></p> | ||
+ | </body> | ||
</html> | </html> |
Revision as of 19:46, 27 August 2015
Attributions
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.
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.
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.
What should this page have?
- 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