"
Team:SDU-Denmark/Tour41
From 2013.igem.org
| Line 24: | Line 24: | ||
</div> | </div> | ||
| - | |||
| - | |||
| - | |||
| - | |||
<div class="accordionTitel">Biobricks</div> | <div class="accordionTitel">Biobricks</div> | ||
| Line 38: | Line 34: | ||
| - | |||
| - | |||
<div class="accordionTitel">Devices</div> | <div class="accordionTitel">Devices</div> | ||
| Line 49: | Line 43: | ||
</div> | </div> | ||
| - | |||
| - | |||
| - | |||
| - | |||
<div class="accordionTitel">Reporter systems</div> | <div class="accordionTitel">Reporter systems</div> | ||
| Line 63: | Line 53: | ||
| - | |||
| - | |||
<div class="accordionTitel">Characterization</div> | <div class="accordionTitel">Characterization</div> | ||
Revision as of 13:06, 2 October 2013
Complete Journal
"If it is not documented, it doesn’t exist." - Louis Fried
When working together in a large group, particularly on such a large project, it is simply impossible for anyone to maintain an overview over the entire project in real time. That is why it is important to keep protocols of every part of the project, to document every experiment that is performed. This allows each team member to backtrack and to resolve any issues with (or mistakes made in) previous experiments. Countless digestions and hundreds of PCR reaction were done, and the explicit protocols established which setups were effective, and which were not. Our iGEM-team has kept protocols since the dawn of the project, and has proved to be an invaluable resource, which saved us quite a bit of time.
Click on the project title below to expand the window and get an overview of the protocols for each experiment. Each protocol name is a link to a pdf file that will open in a new window.
