Difference between revisions of "Team:Kyoto/Collaborations"

 
(119 intermediate revisions by 5 users not shown)
Line 5: Line 5:
 
   a.collabo{
 
   a.collabo{
 
     color:#ffac70;
 
     color:#ffac70;
  }
 
  ul.index{
 
    font-size: 150%;
 
    font-family: serif, 'Times New Roman';
 
    text-align : left;
 
    list-style: none;
 
    margin-left:15%;
 
    margin-right:15%;
 
    color:#556c14;
 
 
   }
 
   }
 
   p.collabopic{
 
   p.collabopic{
 
     text-align:center;
 
     text-align:center;
 +
    font-family:  'Segoe UI';
 
   }
 
   }
 
   p.collabo{
 
   p.collabo{
     color:#000000;
+
     color:#757575;
     text-align:left;
+
     text-align : left;
     font-size:14.5px;
+
     font-size:160%;
 +
    font-family:  'Segoe UI';
 
   }
 
   }
  
 +
  p.arigato{
 +
    color:#757575;
 +
    text-align : center;
 +
    font-size:160%;
 +
    font-family:  'Segoe UI';
 +
  }
 +
 +
  p.linkjump{
 +
      color:#606060;
 +
      text-align : center;
 +
      font-size:140%;
 +
      font-family:  'Segoe UI';
 +
  }
 +
 +
  ul.index1 {
 +
    list-style:none;
 +
    text-align:left;
 +
    font-family: 'Segoe UI';
 +
    font-size:160%;
 +
    margin-top: 15px;
 +
    margin-left:10%;
 +
    margin-right:10%;
 +
    margin-bottom: 10px;
 +
    color: #f0f8ff;
 +
  }
 +
  ul.index1 ul{
 +
    list-style:none;
 +
   
 +
  }
 +
  li{
 +
    list-style:none;
 +
  }
 +
 +
 +
  ul.KELN {
 +
    list-style:none;
 +
    text-align:left;
 +
    font-family: serif, 'Segoe UI';
 +
    font-size:160%;
 +
    margin-top: 15px;
 +
    margin-left:10%;
 +
    margin-right:10%;
 +
    margin-bottom: 10px;
 +
    color: #757575;
 +
  }
 +
  ul.KELN ul{
 +
    list-style:none;
 +
   
 +
  }
 +
h5 {
 +
background: linear-gradient(transparent 90%, #25B6CA 80%);
 +
margin-left: 10%;
 +
}
 
#jump{
 
#jump{
 
     position:fixed;
 
     position:fixed;
     bottom:10%;
+
     bottom:5%;
     right:7%;
+
     right:0;
 
     width:9%;
 
     width:9%;
 
}
 
}
 
#jump img{
 
#jump img{
     width:100%;
+
     width:70%;
 
}
 
}
 
 
</style>
 
</style>
  
  
 
<body>
 
<body>
<div id="jump"><a href="#wrapper"><img src="https://static.igem.org/mediawiki/2017/c/c5/Kyoto_notebook_jump.png"></a></div>
+
<div class="clear"></div>
  <div id="BACKGROUND">
+
<div id="jump">
  <div id="wrapper">
+
    <h1>Collaborations with other teams</h1>
+
      <h5>Table of contents</h5>
+
  <ul class="index">
+
      <li><a href="#Rikadai">1) Meetup with Botchan_Lab_Tokyo</li>
+
      <li><a href="#Kansai">2) iGEM Japan Kansai Forum</a></li>
+
      <li><a href="#Tokyo">3) May Festival</a></li>
+
      <li><a href="#Taiwan1">4) Asia Conference in Taiwan</a></li>
+
      <li><a href="#Taiwan2">5) The exchange of opinions with Taiwan team</a></li>
+
      <li><a href="#KELN">6) Providing Wiki Creation Assisting Software: KELN to iGEM members</a></li>
+
  </ul>
+
  <h5 id="Rikadai">1) Meetup with Botchan_Lab_Tokyo</h5>
+
      <p>私たちはBotchan_Lab_Tokyoを3/10に京都へ招待し、互いのチームの暫定プロジェクトやiGEM活動の進め方についてプレゼンをして意見を交換しました。主に組織体制、資金獲得方法 fundraising、ヒューマンプラクティス、コラボレーションに関して議論した。We invited Team Botchan_Lab_Tokyo to Kyoto, and exchanged our opinions about each putative project and the way of iGEM activities. We especially discussed the below components.Botchan_Lab_Tokyoは、総務課など私たちにはない部門まで細分化して活動を効率化していたのでとても参考になりました。
+
また、互いの財政状況も教え合いました。どのようにクラウドファンディングをしているかをBotchan_Lab_Tokyoに教え、Botchan_Lab_Tokyoに大学から支援を受ける      </p>
+
  
<center><img src="https://static.igem.org/mediawiki/2018/e/e9/T--Kyoto--BotchanCollabo.png" width="70%"></center>
+
<a href="#wrapper">
 +
<img src="https://static.igem.org/mediawiki/2018/1/11/T--Kyoto--upbotton.jpg"></a></div>
 +
<div id="BACKGROUND">
 +
<div style='padding-top: 100px;'><h1 id="wrapper"><img src="https://static.igem.org/mediawiki/2018/1/1c/T--Kyoto--collaborations_title.png" width="30%"></div></h1>
  
  
 +
    <div class="box27">
 +
    <span class="box-title"><font face="Segoe UI">Table of contents</font></span>
 +
  <ul class="index1">
 +
      <li><a href="#Rikadai">1) Meetup with Botchan_Lab_Tokyo</a></li>
 +
      <li><a href="#Aachen">2) Advice from Aachen</a></li>
 +
      <li><a href="#AsiaConfe">3) 6th Asia Pasific conference</a></li>
 +
      <li><a href="#Gifu">4) Meetup with Gifu</a></li>
 +
      <li><a href="#KELN">5) Providing Wiki Creation Assisting Software: KELN to other Teams</a></li>
 +
        </ul>
 +
  </div>
 +
  <br>
 +
      <h5 id="Rikadai">1) Meetup with Botchan_Lab_Tokyo</h5>
  
  <h5 id="Kansai">2) iGEM Japan Kansai Forum</h5>
 
      <p>Hosted by our team, we invited Japanese iGEM teams to the Kansai Forum on 19th February 2017. In the forum, each team presented their project progress and team management methods, followed by heated discussions on each other’s project and management methods. Advices and thoughts were exchanged, and it inspired teams as they continued their projects. <a href="https://static.igem.org/mediawiki/2017/5/5b/Kyoto-collaboration-questionnaire.pdf" class="collabo">Here</a> is the questionnaire taken during this forum!<br>
 
      <img src="https://static.igem.org/mediawiki/2017/e/e9/Kansai.jpeg" width="70%"></p>
 
      <p><a href="https://2017.igem.org/Team:Kobe/Collaborations">Kobe Collaboration</a><br>
 
      <a href="https://2017.igem.org/Team:Nagahama/Collaborations#iGEM_Japan_Kansai_Forum">Nagahama Collaboration</a><br>
 
      <a href="https://2017.igem.org/Team:Gifu/Collaborations">Gifu Collaboration</a><br>
 
      <a href="https://2017.igem.org/Team:Botchan_Lab_Tokyo/Collaborations">Botchan_Lab_Tokyo Collaboration</a><br>
 
      <a href="https://2017.igem.org/Team:HokkaidoU_Japan/Collaborations">Hokkaido collaboration</a>
 
      </p>
 
  <h5 id="Tokyo">3) May Festival</h5>
 
      <p>On 20th and 21st May 2017, UT-Tokyo hosted an event for Japanese iGEM teams during the school festival of the University of Tokyo, “May Festival”. Participating teams presented their projects and offered advices on other teams’ projects. It provided us with a chance to reassess our presentation in terms of intelligibility and simplicity.<br><a href="https://2017.igem.org/Community/Meetups#MayFestTokyo">May festival in Tokyo University</a><br><img src="https://static.igem.org/mediawiki/2017/2/2d/Kyoto_humanpra18.jpeg" width="40%"></p>
 
  <h5 id="Taiwan1">4) Asia Conference in Taiwan</h5>
 
      <p>Asian iGEM teams gathered together in Taiwan and presented their projects and their progress. After that, we exchanged opinions on each other’s projects.<br><a href="https://2017.igem.org/Community/Meetups#AsiaPac">5th Asia Pacific International Genetically Engineered Machine Conference</a><br><img src="https://static.igem.org/mediawiki/2017/3/33/Kyoto_humanpra10.jpeg" width="50%"></p>
 
  <h5 id="Taiwan2">5) The exchange of opinions with Taiwan team</h5>
 
      <p>After 5th Asia Pacific iGEM Conference, we have contacted Taiwan teams online, and discussed further our projects.</p>
 
  
<p><img src="https://static.igem.org/mediawiki/2017/9/93/Collaboratin11.png" width="40%"></p>
+
      <p class="collabo">
 +
 On March 10th, we invited Team Botchan_Lab_Tokyo to Kyoto and exchanged opinions about each other's projects and how to proceed with iGEM activities. We specifically discussed the organizational framework of iGEM, fund-raising, human Practices and collaboration activities.<br><br>
  
 +
 By taking advantage of their large number of members, Botchan_Lab_Tokyo established several departments for a division of work. They have a department specialized in a collaboration which is a strategy our team had not considered. This was a good example for efficient management of team organization.<br><br>
 +
We also talked about the financial support strategies of each team, such as how we started cloud funding, and they explained to us how they were raising money.<br><br>
  
 +
 Interestingly, Botchan_Lab_Tokyo has only participated in iGEM twice so they were not sure how to meet all the standard iGEM criteria. Therefore, from our past experience attending iGEM competitions, we taught them how to interpret the criteria and design their project. For example, they were conducting science experiments for junior high and high school students so as to meet the criteria of “Education & Public Engagement” but they did not incorporate synthetic biology concepts, nor their specific project. We advised them that their Public Engagement will improve by taking in more lectures and doing practical work with DNA.<br><br>
  
   <h5 id="KELN">6) Providing Wiki Creation Assisting Software: KELN to iGEM members</h5>
+
 Finally, as they were having trouble looking for opportunities for collaboration, we told them about the existence of the “Meetup” page and suggested attending the Asia Conference. It was exciting to interact with other Japanese teams through our iGEM activities.<br><br></p>
       <p>Last year, our team developed KELN, a software for easily making HTML codes for tables in lab notebook pages. It is highly useful when making HTML tables for lab notebooks (experimentation results), and we provided the software for Kobe iGEM team. They sent us feedback on the software, and we found some room for improvement. We are currently revising the software. We sincerely thank Kobe team for the pointers.
+
 
The feedback was as follows:</p>
+
<p class="arigato">Thank you, Botchan_Lab_Tokyo!!!<br><br></p>
<p>-Feedback on KELN-</p>
+
 
<ul class="index">
+
<center><img src="https://static.igem.org/mediawiki/2018/e/e9/T--Kyoto--BotchanCollabo.png" width="70%"><br><br>
   <li>1. You kindly gave us a manual for KELN, and it helped us understand how to use it. However, we were a little bit confused which version we should install and how to change members’ name, because the manual was not for the latest version but for the original version.</li>
+
<a href="https://2018.igem.org/Team:Botchan_Lab_Tokyo/Collaborations"><img src="https://static.igem.org/mediawiki/2018/9/92/T--Kyoto--collabo_botchan.png" width="30%"></a></center>
   <li>2. We found that KELN was very helpful to write about routine work by using tables. However, we felt that the format is to some extent restricted. For example, we found it a little hard to put comments into a necessary space. It might be better to add some functions so that one can design pages as they want.</li>
+
<p class="linkjump">↑Go to the Wiki Collaboration page of Team Botchan_Lab_Tokyo↑</p>
   <li>3. We tried to change some codes so that it would fit out aims. However, even though we installed Eclipse, we couldn’t even run the original code (probably we should construct some settings, because ‘import’ doesn’t work correctly). Of course, it came from the lack of our knowledge. But, we hope you will add some explanation so that other teams like us can change this tool easily.</li>
+
<br>
 +
   <h5 id="Aachen">2) Mentoring from Team Aachen</h5>
 +
       <p class="collabo">
 +
<a href="https://2017.igem.org/Team:Aachen" class="collabo">  The Aachen 2017 team</a>  was trying to collect Na + efficiently as a previous project, but because there was no assay method or detailed data on the Wiki, we contact them and repeatedly asked for advice via e-mail.<br>
 +
 
 +
 The Aachen 2017 team was trying to collect Na + efficiently in their previous project, but because there was no assay method or detailed data on the Wiki, we contacted them and asked for advice via e-mail.<br><br>
 +
 
 +
 We were worried about how to measure the amount of Na + uptake of yeast, so team Aachen suggested their assay method. Their method was to cultivate yeast in a salt-containing medium and measure 1 or 2 ml of the separated supernatant after several hours in the culture. <br><br>
 +
 
 +
 Unfortunately, their method requires expensive equipment so we couldn't use the method directly but referred to it for the last assay. Furthermore, according to their modeling, they advised that the peak of Na + absorption by yeast is 6 hours, and advised to divide measurements by the culture OD in order to measure uptake between different yeast strains. Their mentoring was truly encouraging and helpful. Thanks to their help, we were able to launch an improved project.<br><br>
 +
 
 +
 
 +
<p class="arigato">Thank you, Team Aachen!!!<br><br></p><center>
 +
<a href="https://2018.igem.org/Team:Aachen/Collaborations"><img src="https://static.igem.org/mediawiki/2018/8/8b/T--Kyoto--collabo_aachen.png" width="30%"></a></center>
 +
<p class="linkjump">↑Go to the Wiki Collaboration page of Team Aachen↑</p>
 +
 
 +
   <h5 id="AsiaConfe">3) 6th Asia Pasific conference</h5>
 +
      <p class="collabo">
 +
We went to Taiwan and attended the 6th Asia Conference. We were very inspired by the presentations and posters from teams all over Asia. Also, it was good practice for us our own presentation and poster. At the conference, other iGEMers gave us valuable advice on our projects which was very helpful. After the conference, we have continued to exchanged opinions through SNS.</p>
 +
   <h5 id="Gifu">4) Meetup with Gifu</h5>
 +
      <p class="collabo">
 +
We met up with Ryo Niwa, Leader of Team Gifu, who came to visit us in Kyoto. We discussed the current situation of Japanese iGEM teams and shared detailed progress of our projects. We discussed how to meet the criteria and gave advice to each other. In addition, we informed him about how we secured lab space and how we are conducting experiments. Ryo also advised us that an important point to make an iGEM project successful is to take in adequate food and sleep. There are very few teams in Japan, but we encouraged each other to do our best. It was a very unique and meaningful meetup.<br><br>
 +
 
 +
<p class="arigato">Thank you, Team Gifu!!!<br><br></p>
 +
<center><img src="https://static.igem.org/mediawiki/2018/d/d8/T--Kyoto--NiwaDou.jpeg" width="40%"></center>
 +
<center><a href="https://2018.igem.org/Team:Gifu/Collaborations"><img src="https://static.igem.org/mediawiki/2018/c/cb/T--Kyoto--collabo_gifu.png" width="30%"></a></center>
 +
<p class="linkjump">↑Go to the Wiki Collaboration page of Team Gifu↑</p>
 +
 
 +
</p>
 +
 
 +
   <h5 id="KELN">5) Providing Wiki Creation Assisting Software: KELN to other Teams</h5>
 +
      <p class="collabo">
 +
Based on last year's feedback, we improved our KELN software which automatically changes experiment notes to HTML-language and distributed it to Team Gifu and Team Botchan_Lab_Tokyo. The following is their feedback:<br></p>
 +
 
 +
 
 +
<ul class="KELN"><i>From Team Botchan_Lab_Tokyo
 +
<li>・It was easy to use even for people who are not computer-savy. So we could divide the work among many people.</li>
 +
<li>・It was easy to customize the "KELN" software because the edit display is simple.
 +
</li>
 +
<li>・Our experiment sample numbers was so many that we couldn’t write all sample data into a single cell.</li>
 +
<li>・If we can use copy and paste in the software, we will complete the wiki more smoothly.
 +
</li>
 +
From Team Gifu
 +
<li>・ Without any special knowledge ,KELN can be used to get HTML code from a lab notebook, so we recommend this software to all iGEM teams!</i>
 
</ul>
 
</ul>
 +
<br>
 +
<p class="collabo">
 +
We are very happy that KELN was helpful for you. All iGEMers can download KELN from here!
 +
<a href="https://github.com/iGEMKyoto/KELN/wiki" class="collabo">All iGEMers can download KELN from here!</a>
 +
</p>
 +
 +
 
<br>
 
<br>
 
<br>
 
<br>

Latest revision as of 01:29, 7 December 2018


1) Meetup with Botchan_Lab_Tokyo

 On March 10th, we invited Team Botchan_Lab_Tokyo to Kyoto and exchanged opinions about each other's projects and how to proceed with iGEM activities. We specifically discussed the organizational framework of iGEM, fund-raising, human Practices and collaboration activities.

 By taking advantage of their large number of members, Botchan_Lab_Tokyo established several departments for a division of work. They have a department specialized in a collaboration which is a strategy our team had not considered. This was a good example for efficient management of team organization.

We also talked about the financial support strategies of each team, such as how we started cloud funding, and they explained to us how they were raising money.

 Interestingly, Botchan_Lab_Tokyo has only participated in iGEM twice so they were not sure how to meet all the standard iGEM criteria. Therefore, from our past experience attending iGEM competitions, we taught them how to interpret the criteria and design their project. For example, they were conducting science experiments for junior high and high school students so as to meet the criteria of “Education & Public Engagement” but they did not incorporate synthetic biology concepts, nor their specific project. We advised them that their Public Engagement will improve by taking in more lectures and doing practical work with DNA.

 Finally, as they were having trouble looking for opportunities for collaboration, we told them about the existence of the “Meetup” page and suggested attending the Asia Conference. It was exciting to interact with other Japanese teams through our iGEM activities.

Thank you, Botchan_Lab_Tokyo!!!



↑Go to the Wiki Collaboration page of Team Botchan_Lab_Tokyo↑


2) Mentoring from Team Aachen

  The Aachen 2017 team was trying to collect Na + efficiently as a previous project, but because there was no assay method or detailed data on the Wiki, we contact them and repeatedly asked for advice via e-mail.
 The Aachen 2017 team was trying to collect Na + efficiently in their previous project, but because there was no assay method or detailed data on the Wiki, we contacted them and asked for advice via e-mail.

 We were worried about how to measure the amount of Na + uptake of yeast, so team Aachen suggested their assay method. Their method was to cultivate yeast in a salt-containing medium and measure 1 or 2 ml of the separated supernatant after several hours in the culture.

 Unfortunately, their method requires expensive equipment so we couldn't use the method directly but referred to it for the last assay. Furthermore, according to their modeling, they advised that the peak of Na + absorption by yeast is 6 hours, and advised to divide measurements by the culture OD in order to measure uptake between different yeast strains. Their mentoring was truly encouraging and helpful. Thanks to their help, we were able to launch an improved project.

Thank you, Team Aachen!!!

↑Go to the Wiki Collaboration page of Team Aachen↑

3) 6th Asia Pasific conference

We went to Taiwan and attended the 6th Asia Conference. We were very inspired by the presentations and posters from teams all over Asia. Also, it was good practice for us our own presentation and poster. At the conference, other iGEMers gave us valuable advice on our projects which was very helpful. After the conference, we have continued to exchanged opinions through SNS.

4) Meetup with Gifu

We met up with Ryo Niwa, Leader of Team Gifu, who came to visit us in Kyoto. We discussed the current situation of Japanese iGEM teams and shared detailed progress of our projects. We discussed how to meet the criteria and gave advice to each other. In addition, we informed him about how we secured lab space and how we are conducting experiments. Ryo also advised us that an important point to make an iGEM project successful is to take in adequate food and sleep. There are very few teams in Japan, but we encouraged each other to do our best. It was a very unique and meaningful meetup.

Thank you, Team Gifu!!!

↑Go to the Wiki Collaboration page of Team Gifu↑

5) Providing Wiki Creation Assisting Software: KELN to other Teams

Based on last year's feedback, we improved our KELN software which automatically changes experiment notes to HTML-language and distributed it to Team Gifu and Team Botchan_Lab_Tokyo. The following is their feedback:

    From Team Botchan_Lab_Tokyo
  • ・It was easy to use even for people who are not computer-savy. So we could divide the work among many people.
  • ・It was easy to customize the "KELN" software because the edit display is simple.
  • ・Our experiment sample numbers was so many that we couldn’t write all sample data into a single cell.
  • ・If we can use copy and paste in the software, we will complete the wiki more smoothly.
  • From Team Gifu
  • ・ Without any special knowledge ,KELN can be used to get HTML code from a lab notebook, so we recommend this software to all iGEM teams!

We are very happy that KELN was helpful for you. All iGEMers can download KELN from here! All iGEMers can download KELN from here!