Difference between revisions of "Team:UofGuelph/Collaborations"
| Line 82: | Line 82: | ||
</style> | </style> | ||
<body> | <body> | ||
| − | + | ||
<h1 class="colabHead">Collaborations</h1> | <h1 class="colabHead">Collaborations</h1> | ||
<img src="https://static.igem.org/mediawiki/2017/4/4a/T--U_of_Guelph--gryphon.jpg" class="guelphImages"> | <img src="https://static.igem.org/mediawiki/2017/4/4a/T--U_of_Guelph--gryphon.jpg" class="guelphImages"> | ||
| − | <h1 class="colabSub">Collaboration 1</h1> | + | <p class="colabP">This year iGEM Guelph continued its expansion to fostering relations with other established teams and had two main teams with whom we collaborated.</p> |
| + | |||
| + | <h1 class="colabSub">Collaboration 1: iGEM Waterloo</h1> | ||
<p class="colabP"> | <p class="colabP"> | ||
| − | + | iGEM Waterloo was a huge help this year. This team, being the closest team to iGEM Guelph geographically, ended up being one of our largest sources of expertise. iGEM Guelph is now in its second year, still trying to be established at our home university, while iGEM Waterloo has existed for nearly a decade! With their team and university connections so well established, iGEM Waterloo provided our team with knowledge during every encounter, such as at the Ontario iGEM Annual Meeting (oGEM) and at University of Western Ontario’s Synthetic Biology Conference. We’ve discussed topics that ranged from how to secure funding from our university, motivating team members throughout the year, what we should be looking for in a faculty supervisor and different angles from which we should explaining the iGEM Experience. | |
| + | <br><br> | ||
| + | The Waterloo iGEM also gifted us black, flat, clear-bottomed, 96 well plates so that we could complete the interlab study.<br><br> | ||
| + | Thanks for being awesome, iGEM Waterloo! | ||
</p> | </p> | ||
| − | <h1 class="colabSub">Collaboration 2</h1> | + | |
| + | |||
| + | |||
| + | <h1 class="colabSub">Collaboration 2: iGEM Dalhousie</h1> | ||
<p class="colabBot"> | <p class="colabBot"> | ||
| − | + | iGEM Dalhousie became very close with our team between the friendship of their Co-President Matt Curry and our own Jehoshua Sharma. With Dalhousie being a cool 13 hour drive away, a lot of our team communication has been over skype. iGEM Dalhousie and iGEM Guelph seemed to have similar issues arise this year and we had many Skype sessions discussing how to tackle lab interest and engagement within the team. We learned from their prior experience the help that Graduate Mentors can provide to an undergraduate team and a healthy way to retain members is by having an exciting incentive outside of lab work to keep the entire team contributing and on task! iGEM Guelph was able to also offer a few suggestions such as discussing potential University avenues to secure funding from (such as their President or Office of Research) as well as the concept of having weekly lab meetings with their faculty supervisor. | |
| + | <br><br> | ||
| + | iGEM Dalhousie introduced our team to the exciting world of scientific communication from an iGEM perspective with their PloSibilites blog and iGEM Guelph got a chance to write blog posts our “Can Fruit Flies Help Us Predict the Course of Evolution” and “To bee or not to bee? Can you tell if a beehive has CCD?” posts. The blog posts once a week and due to scheduling, our posts won’t be ready until early November. This collaboration was still completed and was very important for iGEM Guelph to start our work on communicating with the public through information dissemination, about the impact that science has on our society as well as the impact that society has on science. | ||
| + | <br><br> | ||
| + | High fives and firm handshakes all around, iGEM Dalhousie! | ||
</p> | </p> | ||
| + | |||
| + | |||
| + | |||
<div class="sponsor"> | <div class="sponsor"> | ||
<p class="footer-links" style="text-align:center!important;"> | <p class="footer-links" style="text-align:center!important;"> | ||
Revision as of 03:36, 18 October 2018
Collaborations
This year iGEM Guelph continued its expansion to fostering relations with other established teams and had two main teams with whom we collaborated.
Collaboration 1: iGEM Waterloo
iGEM Waterloo was a huge help this year. This team, being the closest team to iGEM Guelph geographically, ended up being one of our largest sources of expertise. iGEM Guelph is now in its second year, still trying to be established at our home university, while iGEM Waterloo has existed for nearly a decade! With their team and university connections so well established, iGEM Waterloo provided our team with knowledge during every encounter, such as at the Ontario iGEM Annual Meeting (oGEM) and at University of Western Ontario’s Synthetic Biology Conference. We’ve discussed topics that ranged from how to secure funding from our university, motivating team members throughout the year, what we should be looking for in a faculty supervisor and different angles from which we should explaining the iGEM Experience.
The Waterloo iGEM also gifted us black, flat, clear-bottomed, 96 well plates so that we could complete the interlab study.
Thanks for being awesome, iGEM Waterloo!
Collaboration 2: iGEM Dalhousie
iGEM Dalhousie became very close with our team between the friendship of their Co-President Matt Curry and our own Jehoshua Sharma. With Dalhousie being a cool 13 hour drive away, a lot of our team communication has been over skype. iGEM Dalhousie and iGEM Guelph seemed to have similar issues arise this year and we had many Skype sessions discussing how to tackle lab interest and engagement within the team. We learned from their prior experience the help that Graduate Mentors can provide to an undergraduate team and a healthy way to retain members is by having an exciting incentive outside of lab work to keep the entire team contributing and on task! iGEM Guelph was able to also offer a few suggestions such as discussing potential University avenues to secure funding from (such as their President or Office of Research) as well as the concept of having weekly lab meetings with their faculty supervisor.
iGEM Dalhousie introduced our team to the exciting world of scientific communication from an iGEM perspective with their PloSibilites blog and iGEM Guelph got a chance to write blog posts our “Can Fruit Flies Help Us Predict the Course of Evolution” and “To bee or not to bee? Can you tell if a beehive has CCD?” posts. The blog posts once a week and due to scheduling, our posts won’t be ready until early November. This collaboration was still completed and was very important for iGEM Guelph to start our work on communicating with the public through information dissemination, about the impact that science has on our society as well as the impact that society has on science.
High fives and firm handshakes all around, iGEM Dalhousie!
★ ALERT!
This page is used by the judges to evaluate your team for the medal criterion or award listed below.
Delete this box in order to be evaluated for this medal criterion and/or award. See more information at Instructions for Pages for awards.
Collaborations
Sharing and collaboration are core values of iGEM. We encourage you to reach out and work with other teams on difficult problems that you can more easily solve together.
Silver Medal Criterion #2
Complete this page if you intend to compete for the silver medal criterion #2 on collaboration. Please see the 2018 Medals Page for more information.
Which other teams can we work with?
You can work with any other team in the competition, including software, hardware, high school and other tracks. You can also work with non-iGEM research groups, but they do not count towards the iGEM team collaboration silver medal criterion.
In order to meet the silver medal criteria on helping another team, you must complete this page and detail the nature of your collaboration with another iGEM team.
Here are some suggestions for projects you could work on with other teams:
- Improve the function of another team's BioBrick Part or Device
- Characterize another team's part
- Debug a construct
- Model or simulate another team's system
- Test another team's software
- Help build and test another team's hardware project
- Mentor a high-school team