Difference between revisions of "Team:Nankai/Practices"

 
(129 intermediate revisions by 3 users not shown)
Line 1: Line 1:
−
<html lang="en">
+
{{Nankai}}
−
<head>
+
<html>
−
<script>
+
<link rel="stylesheet" type="text/css" href="https://2015.igem.org/Template:Nankai/miscCSS?action=raw&ctype=text/css" />
−
         document.styleSheets[0].disabled = true
+
        <link rel="stylesheet" type="text/css" href="https://2015.igem.org/Template:Nankai/bootstrapCSS?action=raw&ctype=text/css" />
−
         </script>
+
         <link rel="stylesheet" type="text/css" href="https://2015.igem.org/Template:Nankai/blue-schemeCSS?action=raw&ctype=text/css" />
 +
         <link rel="stylesheet" type="text/css" href="https://2015.igem.org/Template:Nankai/newCSS?action=raw&ctype=text/css" />
  
−
    <meta charset="utf-8">
 
−
    <title>DesignPortfolio</title>
 
−
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
 
−
    <meta name="description" content="">
 
−
    <meta name="author" content="">
 
−
 
−
    <!-- Styles -->
 
−
    <link href='http://fonts.useso.com/css?family=Open+Sans:400,700' rel='stylesheet' >
 
−
    <link href="https://2015.igem.org/Team:Nankai/Practices/bootstrap.css?action=raw&ctype=text/css" rel="stylesheet">
 
−
    <link href="https://2015.igem.org/Team:Nankai/Practices/responsive.bootstrap.css?action=raw&ctype=text/css" rel="stylesheet" />
 
−
    <link href="https://2015.igem.org/Team:Nankai/Practices/screen.css?action=raw&ctype=text/css" rel="stylesheet">
 
−
    <!--[if lt IE 9]>
 
−
      <script src="http://html5shiv.googlecode.com/svn/trunk/html5.js"></script>
 
−
    <![endif]-->
 
 
<style>
 
<style>
 +
#blog {
 +
  background-image: url("https://static.igem.org/mediawiki/2015/d/da/Nankai_HP_Blog.jpg");
 +
}
 +
.col-md-8 blog-posts h4{
 +
text-align: center;
 +
}
 +
.ref1{
 +
text-align:justify;
 +
width:100%;
 +
margin-top:20px;
 +
}
 +
.ref1 p{
 +
font-size:21px;
 +
font-weight:100;
 +
font-family: 'Lucida Sans Unicode',Gill Sans,Lucida Sans,Consolas;
 +
text-indent: 40px;
 +
}
 +
.ref1 h4{
 +
font-size:35px;
 +
font-weight:600;
 +
line-height:40px;
 +
font-family:"Segoe UI",Gill Sans,Lucida Sans,Consolas;
 +
}
 +
.ref1 h5{
 +
margin-top:70px;
 +
line-height:35px;
 +
font-size:30px;
 +
font-weight:600;
  
−
  /*Clear existing style*/
+
font-family:"Segoe UI",Gill Sans,Lucida Sans,Consolas;
 +
}
 +
.ref1 img{
 +
width:100%;
 +
height:auto;
 +
margin-top:35px;
 +
}
 +
.ref1 h6{
 +
font-size:15px;
 +
margin-bottom:40px;
 +
text-align:center;
 +
font-weight:bold;
 +
font-family:"Constantia",Gotham,Consolas;
 +
line-height:17px;
 +
}
 +
.sidebar{
 +
margin-top:50px;
 +
}
 +
.blog-posts{
 +
margin-top:0px;
 +
}
 +
.smallpic{
 +
width:50%;
 +
margin-left:auto;
 +
margin-right:auto;
 +
height:auto;
 +
}
 +
.midpic{
 +
width:80%;
 +
margin-left:auto;
 +
margin-right:auto;
 +
height:auto;
 +
}
 +
</style>
  
  
−
  #contentSub, #menubar, #footer-box, #siteSub, #catlinks, #search-controls, #p-logo, .printfooter, .firstHeading, .visualClear
+
<div class="first-widget parallax" id="blog">
−
{
+
<div class="parallax-overlay">
−
    display:none;
+
                    <p>Your place:&nbsp;<a href="https://2015.igem.org/Team:Nankai">Home</a>>&nbsp;&gt;&nbsp;<a href="https://2015.igem.org/Team:Nankai/Practices">Human Practice</a></p>
−
  }
+
<div class="container pageTitle">
 +
<div class="row">
 +
<div class="col-md-6 col-sm-6">
 +
<h2 class="page-title">Human Practice</h2>
 +
</div> <!-- /.col-md-6 -->
 +
</div> <!-- /.row -->
 +
</div> <!-- /.container -->
 +
</div> <!-- /.parallax-overlay -->
 +
</div> <!-- /.pageTitle -->
  
−
  html, body {
+
<div class="container">
−
    width: auto !important;
+
<div class="ref1">
−
    /*overflow-x: hidden !important;*/
+
<h4>Human Practice: An Amazing Summer！！ </h4>
−
    height: 100% !important;
+
  
−
  }
+
<p>As Peter Carr puts it, "Human Practices is the study of how your work affects the world, and how the world affects your work." This summer, Nankai iGEM team worked our best to put the spirits of collaboration and sharing into practice. Not only have we attended many important activities<a name="No1"> and</a> conferences, but also a new information-sharing platform— iShare has become reality. Let’s see what our team did in this amazing summer.</p>
−
  /*End claer*/
+
</div>
−
</style>
+
  
 +
<div class="row">
  
−
   
+
<div class="col-md-8 blog-posts">
−
</head>
+
−
<body>
+
−
+
−
<div class="container-fluid bigSlider">
+
−
<div class="rs_mainslider">
+
−
<ul class="rs_mainslider_items unstyled">
+
−
<li class="rs_mainslider_items_active">
+
−
<img src="https://static.igem.org/mediawiki/2015/a/af/Nankai_HP_slide1.jpg" alt="slide1" class="rs_mainslider_items_image">
+
−
<div class="rs_mainslider_items_text container">
+
−
<h2>Lorem ipsum dolor sit amet, consectetur</h2>
+
−
<h2>Donec mattis, magna nec lacinia </h2>
+
−
</div>
+
−
</li>
+
−
<li class="rs_mainslider_items_active">
+
−
<img src="https://static.igem.org/mediawiki/2015/c/c3/Nankai_HP_slide2.jpg" alt="slide2" class="rs_mainslider_items_image">
+
−
<div class="rs_mainslider_items_text container">
+
−
<h2>Lorem ipsum dolor sit amet, consectetur</h2>
+
−
<h2>Donec mattis, magna nec lacinia </h2>
+
−
</div>
+
−
</li>
+
−
<li class="rs_mainslider_items_active">
+
−
<img src="https://static.igem.org/mediawiki/2015/2/2c/Nankai_HP_slide3.jpg" alt="slide3" class="rs_mainslider_items_image">
+
−
<div class="rs_mainslider_items_text container">
+
−
<h2>Lorem ipsum dolor sit amet, consectetur</h2>
+
−
<h2>Donec mattis, magna nec lacinia </h2>
+
−
</div>
+
−
</li>
+
−
</ul>
+
  
−
    <div class="rs_mainslider_left_container rs_center_vertical_container">
+
<h4>1. What is iShare?</h4>
−
    <div class="rs_mainslider_left rs_center_vertical"></div>
+
<p>During the summer, we ran into many problems when we were working on our experiments. The lack of materials for instance, is one major difficulty that occurred to us. To continue our project, we had to acquire those materials from other laboratories, which involved us into intellectual property issues..</p>
−
    </div>
+
<p>Thanks to the current system of material transformation, we managed to put all the things we needed together. Most of the laboratories would share their resources with us if we sign the material transfer agreement with them. However a small community as Nankai University is, it still took us a long time to find the right materials we needed. We could imagine how difficult if an iGEM team seeks for information about certain materials among the hundreds of previous teams.</p>
 +
<p>As far as we have concerned, iGEM has already established a functional platform for all the participators to share Bio-bricks that have been submitted since the birth of the event, which is absolutely an excellent work for resources sharing. But there is no information about other materials related to the Bio-bricks, such as bacteria strains, antibodies, enzymes and so on. So our suggestion is that iGEM design a special webpage or a section on wiki for iGEM teams to list the materials they use in their experiments. In addition, iGEM teams could label the materials which they are willing to share. And teams who are interested in those materials could contact the owner for more information or a way to acquire the materials. In this way, future teams could have more resources for similar work and may come up with more improvements, while all iGEM need to do is to provide an information platform like “iShare”.</p>
 +
<p>A mature system of all-round resources sharing could definitely make iGEM a better community. Before it could be accomplished, let’s make the first step by setting up an information sharing platform to promote material sharing. Team Nankai has already designed a model for i-Share. See more information<a name="No2"> on</a> our wiki, and join us to make iShare better and better!See iShare wiki platform <a href="https://2015.igem.org/Team:Nankai/Practices/iShare">here</a>!</p>
  
−
    <div class="rs_mainslider_right_container rs_center_vertical_container">
 
−
    <div class="rs_mainslider_right rs_center_vertical"></div>
 
−
    </div>
 
  
−
    <div class="rs_mainslider_dots_container rs_center_horizontal_container">
+
−
      <ul class="rs_mainslider_dots rs_center_horizontal clearfix"></ul>
+
</div> <!-- /.col-md-8 -->
−
    </div>
+
  
−
</div><!-- / -->
+
<div class="col-md-4">
−
</div><!-- /.container-fluid [bigSlider] -->
+
<div class="sidebar">
−
+
<div class="sidebar-widget">
 +
<h6><a href="https://2015.igem.org/Team:Nankai/Practices"><a href="#No1">iShare Description</a></a></h6>
 +
<h6><a href="https://2015.igem.org/Team:Nankai/Practices_iShare survey"><a href="#No2">iShare survey</a></a></h6>
 +
<h6><a href="https://2015.igem.org/Team:Nankai/Practices_Communition and Collaboration"><a href="#No3">Communition and Collaboration</a></a></h6>
 +
 +
</div> <!-- /.sidebar-widget -->
 +
<div class="sidebar-widget">
 +
<img src="https://static.igem.org/mediawiki/2015/4/4f/Nankai_HP_iShare_Logo1.jpg">
 +
                                                <p>IShare Logo</p>
 +
<img src="https://static.igem.org/mediawiki/2015/c/cd/Nankai_HP_iShare_wikipage.jpg">
 +
                                                <p>iShare Wikipage</p>
 +
 +
                                               
  
−
<div class="container">
+
</div> <!-- /.sidebar-widget -->
−
<div class="row">
+
 
−
<div class="span12 viewProjects">
+
 
−
<a href="#">VIEW ALL PROJECT &#8594;</a>
+
</div> <!-- /.sidebar -->
−
</div>
+
</div> <!-- /.col-md-4 -->
−
</div>
+
 
−
<ul class="row portfolioItems">
+
</div> <!-- /.row -->
−
<li class="span3">
+
<div class="ref1">
−
<figure>
+
<h5>2. iShare Survey </h5>
−
<a href="single_project.html" class="thumbnail">
+
 
−
<img src="https://static.igem.org/mediawiki/2015/c/cc/Nankai_HP_item1.jpg" alt="project">
+
<p>Before a functional platform could be established, we surveyed its popularity among iGEM teams this year. Questionnaires were sent to 281 iGEM teams separately and 82 of them were filled and retrieved. Statistics and analysis of the questions are as following.</p>
−
</a>
+
<p>Most of those teams were undergraduate teams (76.14%), some were graduate teams (20.45%) and two were high school teams (2.27%). </p>
−
<figcaption>
+
<div class="smallpic">
−
<h3><a href="single_project.html">Photo of morning grass</a></h3>
+
<img src="https://static.igem.org/mediawiki/2015/9/90/IShare_HP_iShare_Survey1.jpg">
−
<p>
+
<h6>Q1. Which section is your team in?</h6>
−
Class aptent taciti sociosqu ad litora torque
+
</div>
−
</p>
+
<p>Also most teams surveyed were from Asia (53.41%), some were from North America (21.59%) and Europe (18.18%), 5 teams were from South America (5.68%) and one team from Africa (1.14%).</p>
−
</figcaption>
+
<p>As we explained, “ishare” wants promotes communication and material sharing between iGEM teams. However interactions between teams are greatly limited by the distances of teams. It’s easier for us to reach those teams that are close to us, teams in Asia, but it’s pretty clear that we still need help in organizing real material sharing events on anther continental.</p>
−
</figure>
+
<div class="smallpic">
−
</li>
+
<img src="https://static.igem.org/mediawiki/2015/d/d7/IShare_HP_iShare_Survey2.jpg">
−
<li class="span3">
+
<h6>Q2. Which region is your team in?</h6>
−
<figure>
+
</div>
−
<a href="single_project.html" class="thumbnail">
+
<p>Among those teams interviewed, 77% of them had difficulty finding experimental materials related to their projects and about 53% of those troubled teams said their project was greatly delayed due to the lack of materials. </p>
−
<img src="https://static.igem.org/mediawiki/2015/d/d8/Nankai_HP_item2.jpg" alt="project">
+
<p>It’s usually very difficult for a new team to start on their project. We experienced this inconvenience last summer and that was where the idea of “ishare” came from. Information on wiki could sometimes be too overwhelming, and most of the time we never know how to contact a team by just reviewing their wiki. Therefore it would be great if “ishare” can provide a chance for two-way communication as, a supplement for team wiki. Teams who join “ishare” could put project description and e-mails on it, so that teams with similar interest could find and help each other.</p>
−
</a>
+
<div class="smallpic">
−
<figcaption>
+
<img src="https://static.igem.org/mediawiki/2015/3/38/IShare_HP_iShare_Survey3.png">
−
<h3><a href="single_project.html">Stylish coffee cup</a></h3>
+
<h6>Q3. Have you met any difficulties in finding experimental material related to your project?</h6>
−
<p>
+
</div>
−
Class aptent taciti sociosqu ad litora torque
+
<p>In the meantime, 34.09% of teams found it difficult to repeat or improve previous iGEM projects, 56.82% of teams thought it was hard to say and only the 6% of the teams said it would be easy to do so.</p>
−
</p>
+
<p>iGEM has already established a functional platform of biobricks on registry, and iGEM teams are recommended to use and improve those parts. However information related to those biobricks is often ignored on registry, such as information about bacteria strains, antibodies, enzymes and so on. How can another team acquire certain bacteria strain, when the biobrick is better expressed in this strain than it is in E.coli? Can other teams get this strain directly from the original team, or is it possible that they obtain it from a third party? If those information could be well collected and presented on the platform, independently or as a supplement for registry, “ishare” would be of great help for teams to repeat and improve previous projects, independently or as a supplement for registry.</p>
−
</figcaption>
+
<div class="smallpic">
−
</figure>
+
<img src="https://static.igem.org/mediawiki/2015/6/60/IShare_HP_iShare_Survey4.png">
−
</li>
+
<h6>Q4. How difficult do you think it would be to repeat or improve previous iGEM projects?</h6>
−
<li class="span3">
+
</div>
−
<figure>
+
<p>Like we expected, 84.09% of the teams agreed that a resource sharing platform like "ishare" would help on solving the problems above.</p>
−
<a href="single_project.html" class="thumbnail">
+
<div class="smallpic">
−
<img src="https://static.igem.org/mediawiki/2015/a/a1/Nankai_HP_item3.jpg" alt="project">
+
<img src="https://static.igem.org/mediawiki/2015/f/f9/IShare_HP_iShare_Survey5.png">
−
</a>
+
<h6>Q5. Would a resource sharing platform help in improving previous iGEM project?</h6>
−
<figcaption>
+
</div>
−
<h3><a href="single_project.html">Burlesque</a></h3>
+
<p>And 84.09% of the teams would like to join “ishare”.</p>
−
<p>
+
<div class="smallpic">
−
Class aptent taciti sociosqu ad litora torque
+
<img src="https://static.igem.org/mediawiki/2015/1/17/IShare_HP_iShare_Survey6.png">
−
</p>
+
<h6>Q6. Would you like to be part of iShare?</h6>
−
</figcaption>
+
</div>
−
</figure>
+
<p>In addition, we questioned about team’s preference about sharing materials. 78.41% of the teams would like to share bacterial strains, 57.95% of them would like to share cells strains, 67.05% of them would share enzymes, 55.68% of them would share antibodies, 80.68% of them would share plasmids and another 21.59% would share other materials. </p>
−
</li>
+
<p>Showed in the histogram below, teams were generous about real materials they would offer. In the meantime the actual process of sharing the material for instance shipment of bacterial strains may still be troublesome. However it won’t remain as a problem for long, as long as teams are truly involved in “ishare”. There could dozens of solutions between different teams, and in the future, a wider list of material’s information would be presented on “ishare”.</p>
−
<li class="span3">
+
<div class="smallpic">
−
<figure>
+
<img src="https://static.igem.org/mediawiki/2015/9/9a/IShare_HP_iShare_Survey7.png">
−
<a href="single_project.html" class="thumbnail">
+
<h6>Q7. What kind of material do you expect to get or share on iShare?</h6>
−
<img src="https://static.igem.org/mediawiki/2015/c/cc/Nankai_HP_item4.jpg" alt="project">
+
</div>
−
</a>
+
<p>Now "ishare" is fully functional and 4 iGEM teams have already provided information of materials related to their project on the platform. We want to show iGEM HQ that this is a trouble solving idea. We hope in the future "ishare" could be presented on the upstream of wiki server <a name="No3">and</a> be put into actual use.</p>
−
<figcaption>
+
 
−
<h3><a href="single_project.html">Daredevil</a></h3>
+
<p>If you want to participate in the survey, Click <a href="http://www.sojump.com/jq/5722679.aspx">here</a>.</p>
−
<p>
+
 
−
Class aptent taciti sociosqu ad litora torque
+
<h5>3. Collaborations and Conferences </h5>
−
</p>
+
 
−
</figcaption>
+
<p>This year is the second year of team Nankai participating in iGEM. We have been working with other teams more frequently than before. Tianjin University is our neighbor and intimate partner, and we share a lot on experiments, projects design and human practice. What’s more, during summer vacation, team Nankai had a meetup with team ZJU and team SYSU in Zhejiang University to exchange ideas on iGEM 2015.
−
</figure>
+
</p>
−
</li>
+
<div class="smallpic">
−
<li class="span3">
+
<img src="https://static.igem.org/mediawiki/2015/1/1f/Nankai_HP_project1.jpg">
−
<figure>
+
<h6>Nankai University & Tianjian University</h6>
−
<a href="single_project.html" class="thumbnail">
+
</div>
−
<img src="https://static.igem.org/mediawiki/2015/e/e0/Nankai_HP_item5.jpg" alt="project">
+
<p>Until now, we have built up the collaboration with TJU, ZJU and SYSU. In the near future, we will further communicate with more universities and build up collaborations. We have the same wish for a better tomorrow! Let’s communicate and collaborate!</p>
−
</a>
+
<div class="smallpic">
−
<figcaption>
+
<img src="https://static.igem.org/mediawiki/2015/2/23/Nankai_HP_project6.jpg">
−
<h3><a href="single_project.html">Illuminary creatives</a></h3>
+
<h6>Meeting in Zhejiang University: team Nankai, team ZJU and team SYSU</h6>
−
<p>
+
</div>
−
Class aptent taciti sociosqu ad litora torque
+
<p>What’s more, to promote team's public engagement, we showed up in the iGEM meet up held by Peking University this summer. Besides, we took part in the 3rd Symposium of Bohai-RIM Microbiology and presented our work to other participants.</p>
−
</p>
+
 
−
</figcaption>
+
<div class="lf">
−
</figure>
+
<img src="https://static.igem.org/mediawiki/2015/5/58/Nankai_HP_PEKING_CCIC.jpg">
−
</li>
+
</div>
−
<li class="span3">
+
<div class="rf">
−
<figure>
+
<img src="https://static.igem.org/mediawiki/2015/1/15/Nankai_HP_BOHAI_RIM.jpg">
−
<a href="single_project.html" class="thumbnail">
+
</div>
−
<img src="https://static.igem.org/mediawiki/2015/0/05/Nankai_HP_item6.jpg" alt="project">
+
 
−
</a>
+
<p>During those conferences, we got precious suggestion from experts and other iGEM teams. In the meantime it has broaden our horizons on synthetic biology. </p>
−
<figcaption>
+
</div> <!-- /.container -->
−
<h3><a href="single_project.html">Haselbled</a></h3>
+
−
<p>
+
−
Class aptent taciti sociosqu ad litora torque
+
−
</p>
+
−
</figcaption>
+
−
</figure>
+
−
</li>
+
−
<li class="span3">
+
−
<figure>
+
−
<a href="single_project.html" class="thumbnail">
+
−
<img src="https://static.igem.org/mediawiki/2015/5/53/Nankai_HP_item7.jpg" alt="project">
+
−
</a>
+
−
<figcaption>
+
−
<h3><a href="single_project.html">Sandwich</a></h3>
+
−
<p>
+
−
Class aptent taciti sociosqu ad litora torque
+
−
</p>
+
−
</figcaption>
+
−
</figure>
+
−
</li>
+
−
<li class="span3">
+
−
<figure>
+
−
<a href="single_project.html" class="thumbnail">
+
−
<img src="https://static.igem.org/mediawiki/2015/1/16/Nankai_HP_item8.jpg" alt="project">
+
−
</a>
+
−
<figcaption>
+
−
<h3><a href="single_project.html">London office</a></h3>
+
−
<p>
+
−
Class aptent taciti sociosqu ad litora torque
+
−
</p>
+
−
</figcaption>
+
−
</figure>
+
−
</li>
+
−
</ul><!-- /.portfolioItems -->
+
−
</div><!-- /.container [] -->
+
  
 
 
  
−
<!-- Scripts -->
+
−
<script src="http://code.jquery.com/jquery-1.7.2.js"></script>
+
−
<script src="http://code.jquery.com/ui/1.10.1/jquery-ui.js"></script>
+
−
    <script src="https://2015.igem.org/Team:Nankai/Practices/bootstrap.min.js?action=raw&ctype=text/javascript"></script>
+
−
<script src="https://2015.igem.org/Team:Nankai/Practices/settingsbox.js?action=raw&ctype=text/javascript"></script>
+
−
<script src="https://2015.igem.org/Team:Nankai/Practices/farbtastic.js?action=raw&ctype=text/javascript"></script>
+
−
<script src="https://2015.igem.org/Team:Nankai/Practices/jquery.prettyPhoto.js?action=raw&ctype=text/javascript"></script>
+
−
<script src="https://2015.igem.org/Team:Nankai/Practices/izotope.js?action=raw&ctype=text/javascript"></script>
+
−
<script src="https://2015.igem.org/Team:Nankai/Practices/option.js?action=raw&ctype=text/javascript"></script>
+
−
</body>
+
  
 +
<!-- Scripts -->
 
</html>
 
</html>
 +
{{Nankaifoot}}

Latest revision as of 23:33, 18 September 2015

Medigo Blue, free responsive template

Your place: Home> > Human Practice

Human Practice

Human Practice: An Amazing Summer！！

As Peter Carr puts it, "Human Practices is the study of how your work affects the world, and how the world affects your work." This summer, Nankai iGEM team worked our best to put the spirits of collaboration and sharing into practice. Not only have we attended many important activities and conferences, but also a new information-sharing platform— iShare has become reality. Let’s see what our team did in this amazing summer.

1. What is iShare?

During the summer, we ran into many problems when we were working on our experiments. The lack of materials for instance, is one major difficulty that occurred to us. To continue our project, we had to acquire those materials from other laboratories, which involved us into intellectual property issues..

Thanks to the current system of material transformation, we managed to put all the things we needed together. Most of the laboratories would share their resources with us if we sign the material transfer agreement with them. However a small community as Nankai University is, it still took us a long time to find the right materials we needed. We could imagine how difficult if an iGEM team seeks for information about certain materials among the hundreds of previous teams.

As far as we have concerned, iGEM has already established a functional platform for all the participators to share Bio-bricks that have been submitted since the birth of the event, which is absolutely an excellent work for resources sharing. But there is no information about other materials related to the Bio-bricks, such as bacteria strains, antibodies, enzymes and so on. So our suggestion is that iGEM design a special webpage or a section on wiki for iGEM teams to list the materials they use in their experiments. In addition, iGEM teams could label the materials which they are willing to share. And teams who are interested in those materials could contact the owner for more information or a way to acquire the materials. In this way, future teams could have more resources for similar work and may come up with more improvements, while all iGEM need to do is to provide an information platform like “iShare”.

A mature system of all-round resources sharing could definitely make iGEM a better community. Before it could be accomplished, let’s make the first step by setting up an information sharing platform to promote material sharing. Team Nankai has already designed a model for i-Share. See more information on our wiki, and join us to make iShare better and better!See iShare wiki platform here!

iShare Description
iShare survey
Communition and Collaboration

IShare Logo

iShare Wikipage

2. iShare Survey

Before a functional platform could be established, we surveyed its popularity among iGEM teams this year. Questionnaires were sent to 281 iGEM teams separately and 82 of them were filled and retrieved. Statistics and analysis of the questions are as following.

Most of those teams were undergraduate teams (76.14%), some were graduate teams (20.45%) and two were high school teams (2.27%).

Q1. Which section is your team in?

Also most teams surveyed were from Asia (53.41%), some were from North America (21.59%) and Europe (18.18%), 5 teams were from South America (5.68%) and one team from Africa (1.14%).

As we explained, “ishare” wants promotes communication and material sharing between iGEM teams. However interactions between teams are greatly limited by the distances of teams. It’s easier for us to reach those teams that are close to us, teams in Asia, but it’s pretty clear that we still need help in organizing real material sharing events on anther continental.

Q2. Which region is your team in?

Among those teams interviewed, 77% of them had difficulty finding experimental materials related to their projects and about 53% of those troubled teams said their project was greatly delayed due to the lack of materials.

It’s usually very difficult for a new team to start on their project. We experienced this inconvenience last summer and that was where the idea of “ishare” came from. Information on wiki could sometimes be too overwhelming, and most of the time we never know how to contact a team by just reviewing their wiki. Therefore it would be great if “ishare” can provide a chance for two-way communication as, a supplement for team wiki. Teams who join “ishare” could put project description and e-mails on it, so that teams with similar interest could find and help each other.

Q3. Have you met any difficulties in finding experimental material related to your project?

In the meantime, 34.09% of teams found it difficult to repeat or improve previous iGEM projects, 56.82% of teams thought it was hard to say and only the 6% of the teams said it would be easy to do so.

iGEM has already established a functional platform of biobricks on registry, and iGEM teams are recommended to use and improve those parts. However information related to those biobricks is often ignored on registry, such as information about bacteria strains, antibodies, enzymes and so on. How can another team acquire certain bacteria strain, when the biobrick is better expressed in this strain than it is in E.coli? Can other teams get this strain directly from the original team, or is it possible that they obtain it from a third party? If those information could be well collected and presented on the platform, independently or as a supplement for registry, “ishare” would be of great help for teams to repeat and improve previous projects, independently or as a supplement for registry.

Q4. How difficult do you think it would be to repeat or improve previous iGEM projects?

Like we expected, 84.09% of the teams agreed that a resource sharing platform like "ishare" would help on solving the problems above.

Q5. Would a resource sharing platform help in improving previous iGEM project?

And 84.09% of the teams would like to join “ishare”.

Q6. Would you like to be part of iShare?

In addition, we questioned about team’s preference about sharing materials. 78.41% of the teams would like to share bacterial strains, 57.95% of them would like to share cells strains, 67.05% of them would share enzymes, 55.68% of them would share antibodies, 80.68% of them would share plasmids and another 21.59% would share other materials.

Showed in the histogram below, teams were generous about real materials they would offer. In the meantime the actual process of sharing the material for instance shipment of bacterial strains may still be troublesome. However it won’t remain as a problem for long, as long as teams are truly involved in “ishare”. There could dozens of solutions between different teams, and in the future, a wider list of material’s information would be presented on “ishare”.

Q7. What kind of material do you expect to get or share on iShare?

Now "ishare" is fully functional and 4 iGEM teams have already provided information of materials related to their project on the platform. We want to show iGEM HQ that this is a trouble solving idea. We hope in the future "ishare" could be presented on the upstream of wiki server and be put into actual use.

If you want to participate in the survey, Click here.

3. Collaborations and Conferences

This year is the second year of team Nankai participating in iGEM. We have been working with other teams more frequently than before. Tianjin University is our neighbor and intimate partner, and we share a lot on experiments, projects design and human practice. What’s more, during summer vacation, team Nankai had a meetup with team ZJU and team SYSU in Zhejiang University to exchange ideas on iGEM 2015.

Nankai University & Tianjian University

Until now, we have built up the collaboration with TJU, ZJU and SYSU. In the near future, we will further communicate with more universities and build up collaborations. We have the same wish for a better tomorrow! Let’s communicate and collaborate!

Meeting in Zhejiang University: team Nankai, team ZJU and team SYSU

What’s more, to promote team's public engagement, we showed up in the iGEM meet up held by Peking University this summer. Besides, we took part in the 3rd Symposium of Bohai-RIM Microbiology and presented our work to other participants.

During those conferences, we got precious suggestion from experts and other iGEM teams. In the meantime it has broaden our horizons on synthetic biology.

Medigo Blue, free responsive template

Copyright © Nankai University

Nankai IGEM Team 2015