Difference between revisions of "Team:UNOTT/Collaborations"
| Line 37: | Line 37: | ||
<center><img src="https://static.igem.org/mediawiki/2017/9/99/T--UNOTT--skypebristoljakevik.jpeg" style="height: auto; width: 800px;"></center> | <center><img src="https://static.igem.org/mediawiki/2017/9/99/T--UNOTT--skypebristoljakevik.jpeg" style="height: auto; width: 800px;"></center> | ||
</div> | </div> | ||
| + | <p> </p> | ||
<p> The IDE is a local testing environment created by the Bristol iGEM team. The environment would allow users to deisgn and upload their entire wiki pages after fine tuning to the users desired end product. The IDE also has an in-built feature that avoids unwanted interactions between the users navigation bar and the igem's own navigation bar. This environment was brilliant for our purposes! </p> | <p> The IDE is a local testing environment created by the Bristol iGEM team. The environment would allow users to deisgn and upload their entire wiki pages after fine tuning to the users desired end product. The IDE also has an in-built feature that avoids unwanted interactions between the users navigation bar and the igem's own navigation bar. This environment was brilliant for our purposes! </p> | ||
| − | + | <p> </p> | |
<p> The IDE was very useful to our team since our team members are proficient in many coding languages... except HTML coding! This was just our luck, however, once the Bristol team had contacted us via Skype (see image above) we quickly realised this is just what we needed for our main wiki editor (Jake) to get going with our wiki design. </p> | <p> The IDE was very useful to our team since our team members are proficient in many coding languages... except HTML coding! This was just our luck, however, once the Bristol team had contacted us via Skype (see image above) we quickly realised this is just what we needed for our main wiki editor (Jake) to get going with our wiki design. </p> | ||
| − | + | <p> </p> | |
<p> We were not able to use the IDE to upload our entire wiki to the iGEM website as intended since we had already started when the Bristol team had contacted us. Nevertheless, we were able to use it to design each page of the wiki. You can click this link to see our entire wiki in the development environment. </p> | <p> We were not able to use the IDE to upload our entire wiki to the iGEM website as intended since we had already started when the Bristol team had contacted us. Nevertheless, we were able to use it to design each page of the wiki. You can click this link to see our entire wiki in the development environment. </p> | ||
Revision as of 15:45, 29 September 2017
COLLABORATIONS
#1 - Bristol IDE Collaboration
We have collaborated with the 2017 UK Bristol iGEM team this summer in order to use and test their new tool called the 'iGEM Development Environment' also known as 'IDE'.
The IDE is a local testing environment created by the Bristol iGEM team. The environment would allow users to deisgn and upload their entire wiki pages after fine tuning to the users desired end product. The IDE also has an in-built feature that avoids unwanted interactions between the users navigation bar and the igem's own navigation bar. This environment was brilliant for our purposes!
The IDE was very useful to our team since our team members are proficient in many coding languages... except HTML coding! This was just our luck, however, once the Bristol team had contacted us via Skype (see image above) we quickly realised this is just what we needed for our main wiki editor (Jake) to get going with our wiki design.
We were not able to use the IDE to upload our entire wiki to the iGEM website as intended since we had already started when the Bristol team had contacted us. Nevertheless, we were able to use it to design each page of the wiki. You can click this link to see our entire wiki in the development environment.
#2 - Revival collaboration
In September, we sent our freeze-dried cells out to Groningen, Sheffield and Edinburgh in order to see how reliable the fluorescence from our keys can be read after revival using a set method.
