Hey iGEM Teams!
One of the things we're looking at this year is collaborating with as many schools as possible to create a definitive characterization standard for the parts registry. Because we all know how annoying it is when you go looking for parts and you can't find any characterization data, or characterization that was done poorly. We are trying to write a standard protocol that all teams need to follow before they submit a part to the registry. This will help future teams find high quality parts easier and faster.
Unfortunately, every year teams write protocols that they think everyone should follow, and nothing ever gets done. We think this is because it's written from one team's perspective, and not reviewed by multiple parties.
That's where you guys come in!
We're looking for teams that are willing to at least look at the protocol we write and make suggestions on how to improve it. And maybe if we do it well enough, we'd like to have teams actually use the protocol to characterize their parts for this year's competition.
This will not only help iGEM be better characterized, each team that collaborates with us will be able to use that for completing the requirements for a gold medal in the competition.
But we haven't written the protocol yet, we're just fielding interest and seeing who's willing to collaborate. We're hoping we get a large number of teams to help, because the more teams that help and approve it, the more likely an actual protocol will be put in place by iGEM HQ.
So if you and the rest of your team could each take this short, 10 question survey, it would help us immensely and be the first step to creating this standard!
Also, if you want to keep up with our team and our progress, you can find us on Facebook and Twitter and we'll follow or like you back!
Wednesday, May 29, 2013
Tuesday, May 28, 2013
Friday, May 24, 2013
Here's an update on what we've done this week and what we're doing with the project.
Our initial idea was to create a tool kit for the registry that allows iGEM teams to easily implement post translational modifications (PTMs) to complex proteins that they want to produce. Many eukaryotic cells have these PTMs to make the proteins they need, but prokaryotic organisms like E.coli have a much smaller selection of PTMs. So iGEM teams are limited in what proteins they can produce in E.coli. Our idea was to create a toolkit of devices and enzymes that other teams could put in their device to allow for the needed PTMs to work. So that's what we spent most of this week researching.
Unfortunately, after researching this idea we decided that PTMs weren't really a good project direction and that there isn't much we could do with it that would really be new or impressive. We can't create a toolkit like we originally planned because each type of PTM is radically different, even when it's two cases of the same modification. So since we can't create a useful toolkit, all we would be doing is putting coding regions in E.coli and seeing if it worked, which isn't really a good project.
So we started talking about quality control after Dr. Rickus mentioned it to us. We realized that there's no real standard for robustness of a part in the registry. People just put parts in one situation and test it in that specific set of variables, which doesn't help other teams if they want to use it in a different strain of microbe or under different conditions. So we read a paper that just came out that talked about creating a quality control number for genetic parts that shows how robust a part is to change. One of our focuses will be to adapt their method to iGEM parts and create a new system for measuring robustness of parts in the registry so teams can easily see how well a part can be used in different situations. It will add a level of characterization to the registry that is sorely needs. We are also talking about creating a number of devices or even a toolkit that teams can use to control robustness of a part. So let's say we create one device that keeps the output of a circuit steady in temperature changes, one that keeps steady in pH changes, and one that keeps it steady when the host species is changed. Then teams could use our quality control devices to better build and characterize their parts.
That's the direction we'll be focusing on for the last bit of this week and all of next week, and hopefully we'll have a working project outline by the end of next week.
Thanks for reading!