Team:SDU-Denmark/Tour41

From 2013.igem.org

(Difference between revisions)
Line 24: Line 24:
   <div class="pane current" style="height:150px;" >
   <div class="pane current" style="height:150px;" >
-
28.02.2013 - Assembly of the team:  <br>
+
<b>28.02.2013</b> - Assembly of the team:  <br>
-
08.03.2013 - 10.03.2013 - Teambuilding: iGEM crash course (DTU) <br>
+
<b>08.03.2013 - 10.03.2013</b> - Teambuilding: iGEM crash course (DTU) <br>
-
21.03.2013 - First meeting: get to know each other <br>
+
<b>21.03.2013</b> - First meeting: get to know each other <br>
-
26.03.2013 - Two new members of the team (Mattias and Sofie)<br>
+
<b>26.03.2013</b> - Two new members of the team (Mattias and Sofie)<br>
-
April + start of May - Brainstorming<br>
+
<b>April + start of May</b> - Brainstorming<br>
-
08.05.2013 - Determination of project<br>
+
<b>08.05.2013</b> - Determination of project<br>
-
11.07.2013 - One new member of the group (Nicky)<br>
+
<b>11.07.2013</b> - One new member of the group (Nicky)<br>

Revision as of 15:38, 2 October 2013

Complete Journal

Important dates & Protocols

"If it is not documented, it doesn’t exist." - Louis Fried

Obviously, Louis Fried was wrong - and luckily so, we might add! But it is true that if it is not documented, we don't know whether it exist. So please, click through the tabs below and catch a quick glimpse of our most treasured moments of the summer. We kept a calender of special events since the start of the project. And if you have the yearning (particularly after reading our Results), open up our thorough protocols below.


The very beginning
28.02.2013 - Assembly of the team:
08.03.2013 - 10.03.2013 - Teambuilding: iGEM crash course (DTU)
21.03.2013 - First meeting: get to know each other
26.03.2013 - Two new members of the team (Mattias and Sofie)
April + start of May - Brainstorming
08.05.2013 - Determination of project
11.07.2013 - One new member of the group (Nicky)
Social events
Lab successes
iGEM deadlines

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 project part. Each protocol name is a link to a pdf file that will open in a new window.


Primer design
Biobricks
Devices
Reporter systems
Characterization