Difference between revisions of "Team:Northeastern Boston/notebook"
| Line 163: | Line 163: | ||
</div> | </div> | ||
| + | <h2>Protocols.io</h2> | ||
| + | <p>Northeastern has decided to use Protocols.io to host all of its iGEM protocols. Protocols.io is an online open source wet lab repository. Researchers can upload their experimental protocol, share it others, build in functionality (like timers), and "fork" other researchers' protocols (adapting them for their particular situation).</p> | ||
| + | |||
| + | <p>We think this is worth breaking the <a href="https://2015.igem.org/Wiki_Requirements" target="_blank">"No iFrames"</a> rule. The benefit of teams being able to create a sharable protocol, with easy reference and modifiability, outweigh the fear of "cheating" from iGEM teams altering the externally hosted content (in part because altering lab protocols is relatively benign). Other teams could, with the Protocols.io app, exactly replicate the protocol that we followed, for example, when we transformed <a href="https://www.protocols.io/view/Glass-Bead-Transformation-of-Chlamydomonas-dtn6md" target="_blank"><i>C. reinhardtii</i></a>.</p> | ||
| + | |||
| + | <p>Reproducibility is the existential crisis that plagues science; when results in one lab are completely unrepeatable elsewhere, the value of science plummets. Protocols.io could be one potential solution. We enjoyed using it, forking protocols, and making our own. We encourage other teams to try it as well. Protocols don't need to be maintained in trans-generational, witchcraft-ready tomes, or lab-protected Dropboxes. Instead, these methods should be as easy to access as possible.</p> | ||
</div> | </div> | ||
Revision as of 22:16, 18 September 2015
PROTOCOLS
DNA
Escherichia coli
Chlamydomonas reinhardtii
Protocols.io
Northeastern has decided to use Protocols.io to host all of its iGEM protocols. Protocols.io is an online open source wet lab repository. Researchers can upload their experimental protocol, share it others, build in functionality (like timers), and "fork" other researchers' protocols (adapting them for their particular situation).
We think this is worth breaking the "No iFrames" rule. The benefit of teams being able to create a sharable protocol, with easy reference and modifiability, outweigh the fear of "cheating" from iGEM teams altering the externally hosted content (in part because altering lab protocols is relatively benign). Other teams could, with the Protocols.io app, exactly replicate the protocol that we followed, for example, when we transformed C. reinhardtii.
Reproducibility is the existential crisis that plagues science; when results in one lab are completely unrepeatable elsewhere, the value of science plummets. Protocols.io could be one potential solution. We enjoyed using it, forking protocols, and making our own. We encourage other teams to try it as well. Protocols don't need to be maintained in trans-generational, witchcraft-ready tomes, or lab-protected Dropboxes. Instead, these methods should be as easy to access as possible.