|
|
| Line 4: |
Line 4: |
| | <html> | | <html> |
| | | | |
| − | Collaborations are an important essence of iGEM in particular and science in general. Teams in the past have shown excellent collaborations.... <br>
| + | <a href="http://igem.rhizi.net"> Rhizi </a> |
| − | We decided to further the <<collaboration essence of iGEM>> by setting up a graphical database of project <<features>> of all the <<# of teams>> iGEM Teams. We used the "Rhizi" which is a real-time collaboration tool whereby a team can share their project details under the following node types, and common nodes between teams are automatically connected. For instance, a team working on lactobacillus plantarum would automatically be connected to all the other teams working on the same organism, and then can share vectors, promoters, protocols, and in general any advice, with all these teams.
| + | |
| | | | |
| − | <<Screenshot from Rhizi showing the above>>
| |
| − |
| |
| − | With the developers of Rhizi, we developed the structure of a Rhizi document (node types, view modes, features) to suit the particular needs of iGEM. We then made a short video tutorial explaining the usage of the database, and requested <<2/3 teams in Paris>> iGEM teams for testing and feedback on both the tutorial and Rhizi. We re-made the video catering to the feedback and then asked all the iGEM teams to share their project details at <a href="http://igem.rhizi.net"> Rhizi </a>
| |
| − |
| |
| − | <<One/Two examples of other teams' actual collaboration from the Rhizi>>
| |
| − |
| |
| − | <<Screenshot from Rhizi and link to actual Rhizi>>
| |
| | | | |
| | | | |
