Team:SDU-Denmark/Tour41

From 2013.igem.org

(Difference between revisions)
Line 6: Line 6:
<p class='intro'>"If it is not documented, it doesn’t exist." - <b>Louis Fried</b></p>
<p class='intro'>"If it is not documented, it doesn’t exist." - <b>Louis Fried</b></p>
 +
 +
 +
 +
 +
 +
<p>
 +
We have kept an calender with special events, since the start of this project. We would very much like to share this list with you, our successes and events.
 +
 +
</p>
 +
 +
 +
 +
<div class="accordion" style="width:650px;">
 +
 +
  <div class="accordionTitel">The very beginning</div>
 +
  <div class="pane" style="height:150px;" >
 +
 +
 +
 +
  </div>
 +
 +
 +
  <div class="accordionTitel">Social events</div>
 +
  <div class="pane" style="height:150px;" >
 +
 +
 +
 +
 +
  </div>
 +
 +
 +
 +
  <div class="accordionTitel">Lab successes</div>
 +
  <div class="pane" style="height:150px;" >
 +
 +
 +
 +
 +
  </div>
 +
 +
 +
  <div class="accordionTitel">iGEM deadlines</div>
 +
  <div class="pane" style="height:150px;" >
 +
 +
 +
 +
 +
  </div>
 +
</div>
 +
 +
 +
 +
<p>
<p>
Line 11: Line 64:
<span class="intro">When working together in a large group</span>, 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.  
<span class="intro">When working together in a large group</span>, 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.  
<p></p>
<p></p>
-
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.   
+
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.   
-
 
+
</p>
</p>
 +
 +
 +
<br>
<div class="accordion" style="width:650px;">
<div class="accordion" style="width:650px;">
Line 20: Line 75:
   <div class="pane" style="height:150px;" >
   <div class="pane" style="height:150px;" >
-
XOXOXOXOXO
+
 
   </div>
   </div>
Line 28: Line 83:
   <div class="pane" style="height:150px;" >
   <div class="pane" style="height:150px;" >
-
XOXOXOXOXO
+
 
Line 38: Line 93:
   <div class="pane" style="height:150px;" >
   <div class="pane" style="height:150px;" >
-
XOXOXOXOXO
+
 
Line 47: Line 102:
   <div class="pane" style="height:150px;" >
   <div class="pane" style="height:150px;" >
-
XOXOXOXOXO
+
 
Line 57: Line 112:
   <div class="pane current" style="height:150px;" >
   <div class="pane current" style="height:150px;" >
-
XOXOXOXOXO
+
 

Revision as of 13:15, 2 October 2013

Complete Journal

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

We have kept an calender with special events, since the start of this project. We would very much like to share this list with you, our successes and events.

The very beginning
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