Difference between revisions of "Template:Heidelberg/collab/aachen"

Line 6: Line 6:
 
                 <div class="row">
 
                 <div class="row">
 
                     <div class="col-lg-12">
 
                     <div class="col-lg-12">
−
                         <div class="panel panel‐default" style="background: #f2f2eb url(http://www.matthamm.com/images/textured_background.jpg); -webkit-box-shadow: 0px 3px 10px 1px rgba(112,111,112,1);
+
                         <div class="panel panel‐default">
−
                            -moz-box-shadow: 0px 3px 10px 1px rgba(112,111,112,1);
+
−
                            box-shadow: 0px 3px 10px 1px rgba(112,111,112,1);">
+
 
                             <div class="panel‐heading">
 
                             <div class="panel‐heading">
 
                                 <h3 class="basicheader">Supporting iGEM Team Aachen</h3>
 
                                 <h3 class="basicheader">Supporting iGEM Team Aachen</h3>

Revision as of 05:52, 18 September 2015

Supporting iGEM Team Aachen

Back then when it was still summer, Michael Osterhege from iGEM Team Aachen visited us. As a verteran of iGEM 2014, he already knew that one of the most important parts of every successfull project is sample management. Talking with him we got to know of other teams struggling to locate their samples. Their plan was, to get further information about the impact of this problem. Michael has had already prepared a draft for the survey which we then discussed. Of course in the following weeks we participated in the final version of the survery.

Not only did he bring a beta-survey, but also an already functional beta-version of a very promising software: tubefront. It's a mobile-optimized webservice which keeps track of all your samples, assigns IDs which can be written on the tubes and tells you where you can find them.
As of now the software is fully functional and availiable for free for other teams. They also developed a MediaWiki plugin which can be confortably implemented into any wiki.

Though we really loved tubefront with heavy heart we decided not to use tubefront ourselves, as we had already established a sample management system. We recommend any team to check it out though, as it has proven to work for various teams and future generations of teams could really benefit from it.