Difference between revisions of "Team:Kyoto/Collaborations"
| Line 148: | Line 148: | ||
<h2 id="igem japan kansai forum">iGEM Japan Kansai Forum</h2> | <h2 id="igem japan kansai forum">iGEM Japan Kansai Forum</h2> | ||
| − | <p>Hosted by our team, we invited Japanese iGEM teams to Kansai Forum .We were able to exchange ideas and | + | <p>Hosted by our team, we invited Japanese iGEM teams to the Kansai Forum. We were able to exchange ideas and feedback on each of the teams’ projects. We sincerely thank all of the teams who attended this forum.</p> |
<ul> | <ul> | ||
<li><a href="https://2016.igem.org/Team:UT-Tokyo">UT-Tokyo</a></li> | <li><a href="https://2016.igem.org/Team:UT-Tokyo">UT-Tokyo</a></li> | ||
| Line 155: | Line 155: | ||
<h2 id="may festival">May Festival</h2> | <h2 id="may festival">May Festival</h2> | ||
| − | <p>UT-Tokyo hosted an event for Japanese iGEM teams in the school festival of University of Tokyo. We were able to exchange ideas and | + | <p>UT-Tokyo hosted an event for Japanese iGEM teams in the school festival of the University of Tokyo. We were able to exchange ideas and feedback on each of the teams’ projects. We sincerely thank UT-Tokyo for the amazing opportunity and all of the teams who attended this forum, giving us valuable feedback.</p> |
<ul> | <ul> | ||
<li><a href="https://2016.igem.org/Team:UT-Tokyo">UT-Tokyo</a></li> | <li><a href="https://2016.igem.org/Team:UT-Tokyo">UT-Tokyo</a></li> | ||
| Line 164: | Line 164: | ||
<h2 id="genetics society of japan">Genetics Society of Japan</h2> | <h2 id="genetics society of japan">Genetics Society of Japan</h2> | ||
| − | <p>Nagahama hosted an event in the 88th annual meeting of the Genetics Society of Japan for Japanese iGEM teams. We were able to exchange ideas and | + | <p>Nagahama hosted an event in the 88th annual meeting of the Genetics Society of Japan for Japanese iGEM teams. We were able to exchange ideas and feedback on each of the teams’ projects. We sincerely thank all participant teams for the amazing opportunity and all of the teams who attended this event, giving us valuable feedback.</p> |
<ul> | <ul> | ||
<li><a href="https://2016.igem.org/Team:UT-Tokyo">UT-Tokyo</a></li> | <li><a href="https://2016.igem.org/Team:UT-Tokyo">UT-Tokyo</a></li> | ||
| Line 173: | Line 173: | ||
<h2 id="providing wiki creation assisting software: keln to igem members"> Providing Wiki Creation Assisting Software: KELN to iGEM members</h2> | <h2 id="providing wiki creation assisting software: keln to igem members"> Providing Wiki Creation Assisting Software: KELN to iGEM members</h2> | ||
| − | <p> Our team has few members who can write HTML codes, making HTML tables for lab | + | <p> Our team has few members who can write HTML codes, making HTML tables for lab notebooks (experimentation results) a serious issue. This was the motivation for the creation of KELN, a software for easily making HTML codes for tables in lab notebook pages.<br> |
<a href="https://2016.igem.org/Team:Kyoto/Software">Software</a><br> | <a href="https://2016.igem.org/Team:Kyoto/Software">Software</a><br> | ||
<a href="https://github.com/iGEMKyoto/KELN/releases">KELN download</a><br> | <a href="https://github.com/iGEMKyoto/KELN/releases">KELN download</a><br> | ||
| − | During the forums as listed above, we realized that many iGEM teams are having the same problems. Thus, we made this software open-sourced for usage by any iGEM teams. What follows are their | + | During the forums as listed above, we realized that many iGEM teams are having the same problems. Thus, we made this software open-sourced for usage by any iGEM teams. What follows are their feedback</p> |
<div> | <div> | ||
| Line 188: | Line 188: | ||
<p>Positive traits: It was very easy to use.</p> | <p>Positive traits: It was very easy to use.</p> | ||
<p>Traits to improve: User interface: even though it was simple and easy to use, the output screen for showing HTML texts could have been larger.</p> | <p>Traits to improve: User interface: even though it was simple and easy to use, the output screen for showing HTML texts could have been larger.</p> | ||
| − | <p>Comments: Our team makes HTML version of lab notebooks by making a template first and letting people (who may not know HTML) fill in the blank template. If no one in the team | + | <p>Comments: Our team makes HTML version of lab notebooks by making a template first and letting people (who may not know HTML) fill in the blank template. If no one in the team knows how to write HTML codes, we think this software could be very helpful. However, if there were someone who can, it may be faster for them to create blank templates. However, a system to register names was very useful, as we didn’t have to type in the experimenter’s name every time. Biobrick parts are also very long and tiresome to type in, so allowing us to register BioBrickparts in the same manner may also improve user experience. We would like to use this software with such improvements in the future.</p> |
</div> | </div> | ||
| − | <p>From such | + | <p>From such feedback, we improved the registration process of the experimenter names, and continue to provide and upgrade this software. For more information, please follow the links we provided above.</p> |
Latest revision as of 01:14, 3 November 2016
Contents
Collaboration
iGEM Japan Kansai Forum
Hosted by our team, we invited Japanese iGEM teams to the Kansai Forum. We were able to exchange ideas and feedback on each of the teams’ projects. We sincerely thank all of the teams who attended this forum.
May Festival
UT-Tokyo hosted an event for Japanese iGEM teams in the school festival of the University of Tokyo. We were able to exchange ideas and feedback on each of the teams’ projects. We sincerely thank UT-Tokyo for the amazing opportunity and all of the teams who attended this forum, giving us valuable feedback.
Genetics Society of Japan
Nagahama hosted an event in the 88th annual meeting of the Genetics Society of Japan for Japanese iGEM teams. We were able to exchange ideas and feedback on each of the teams’ projects. We sincerely thank all participant teams for the amazing opportunity and all of the teams who attended this event, giving us valuable feedback.
Providing Wiki Creation Assisting Software: KELN to iGEM members
Our team has few members who can write HTML codes, making HTML tables for lab notebooks (experimentation results) a serious issue. This was the motivation for the creation of KELN, a software for easily making HTML codes for tables in lab notebook pages.
Software
KELN download
During the forums as listed above, we realized that many iGEM teams are having the same problems. Thus, we made this software open-sourced for usage by any iGEM teams. What follows are their feedback
Gifu
Positive traits: The user interface was very natural, and the time-consuming work of writing HTML codes were significantly shortened
Traits to improve: User manual was mostly about registration and protocols for Eclipse, and there were no instructions to the startup of KELN itself. Also, the table’s rows and column size were fixed, and they couldn’t be interchanged
Hokkaido-U
Positive traits: It was very easy to use.
Traits to improve: User interface: even though it was simple and easy to use, the output screen for showing HTML texts could have been larger.
Comments: Our team makes HTML version of lab notebooks by making a template first and letting people (who may not know HTML) fill in the blank template. If no one in the team knows how to write HTML codes, we think this software could be very helpful. However, if there were someone who can, it may be faster for them to create blank templates. However, a system to register names was very useful, as we didn’t have to type in the experimenter’s name every time. Biobrick parts are also very long and tiresome to type in, so allowing us to register BioBrickparts in the same manner may also improve user experience. We would like to use this software with such improvements in the future.
From such feedback, we improved the registration process of the experimenter names, and continue to provide and upgrade this software. For more information, please follow the links we provided above.
