Difference between revisions of "Team:HAFS-Korea/Collaborations"

 
Line 1: Line 1:
 
{{HAFS-Korea}}
 
{{HAFS-Korea}}
 
<html>
 
<html>
 +
<h1>Collaborations</h1><br>
 +
<h3> a. communicating with other iGEM teams</h3>
 +
<h4>#Korean Regional Meetup  8/15 @ Lotte hotel Athen’s Garden</h4>
 +
<p>The three Korean teams gathered together and presented their own projects. We had an opportunity to show our idea and receive comments during Q&A sessions.
 +
Particularly, one overgraduate team called Korea_U_Seoul team asked us why we used E.coli instead of other microorganisms. We answered that it is for accessibility. Since our project is headed toward the welfare of farmers, we focus on the technology that is “available” and “easy” for them to use.
 +
<img src=https://static.igem.org/mediawiki/2015/d/d3/6_Cllaboration_1.jpeg width=80%><br>
 +
<p>We also offered some opinions about two other teams. Three Korean teams collaborated to achieve better at Giant Jamboree. It was indeed a great time.<br><br>
 +
<h4>#i GEM mentors</h4>
 +
<p>Gha Young Lee, David Brown, Ricardo Chavez
 +
We have applied for Pilot Mentorship Program, and were able to meet three great mentors who had experienced Giant Jamboree. In particular, Gha Young helped us a lot. She shared her experience about preparing for Giant Jamboree. We can’t wait until meeting her at Boston :) Also, we have skyped twice during the summer vacation( 7/1/15 10AM and 8/17/15 11 PM in Korean time) and got advice about part submission, human practice and the purpose of our project.<br><br><br>
 +
<h3> b. communicating with Bio Ethanol Research Institutes </h3>
 +
<h4>#Jeon-nam University Bioethanol Research Institute 8/19</h4><br>
 +
<img src=https://static.igem.org/mediawiki/2015/a/a6/6_Collaboration_2.png width=80%><br>
 +
<p>We started exchangin emails with JU Bioethanol Research Institute on August 19th. We not only introduced our bioengineering project but also Our questions were related to the problems that this institute encounters during their research. It answered that the economic feasibility and construction of infrastructure were the main problem it often faces.<br><br><br>
 +
<h3> c. Testing other teams’ systems</h3>
 +
<p>We’ve tested some systems of other iGEM teams such as Korea_U_Seoul,Nankai and Paris-Bettencourt.
  
<h2> Collaborations</h2>
 
  
<p>
 
Sharing and collaboration are core values of iGEM. We encourage you to reach out and work with other teams on difficult problems that you can more easily solve together.
 
</p>
 
  
<div class="highlightBox">
 
 
<h4> Which other teams can we work with? </h4>
 
<p>
 
You can work with any other team in the competition, including software, hardware, high school and other tracks. You can also work with non-iGEM research groups, but they do not count towards the <a hreef="https://2015.igem.org/Judging/Awards#Medals">iGEM team collaboration gold medal criterion</a>.
 
</p>
 
 
<p>
 
In order to meet the gold medal criteria on helping another team, you must complete this page and detail the nature of your collaboration with another iGEM team.
 
</p>
 
</div>
 
 
<p>
 
Here are some suggestions for projects you could work on with other teams:
 
</p>
 
 
<ul>
 
<li> Improve the function of another team's BioBrick Part or Device</li>
 
<li> Characterize another team's part </li>
 
<li> Debug a construct </li>
 
<li> Model or simulating another team's system </li>
 
<li> Test another team's software</li>
 
<li> Help build and test another team's hardware project</li>
 
<li> Mentor a high-school team</li>
 
</ul>
 
 
 
 
</div>
 
<!-- Start of CSS-->
 
<style type="text/css">
 
 
p, #content {
 
color:#85C380;
 
}
 
 
a, a:visited {
 
color:#84FD2C;
 
}
 
 
 
 
/* PAGE LAYOUT */
 
 
 
/* Set up a width, height and color of the body wrapper*/
 
body {
 
background-color: #534743;
 
}
 
 
/* Creates a container that will wrap all of the content inside your wiki pages. */
 
#mainContainer { 
 
width: 980px;
 
overflow:hidden;
 
float:left;
 
margin-left:20px;
 
margin-bottom: 10px;
 
background-color: #fff;
 
border-bottom: 20px solid #963F20;
 
}
 
 
/* Creates the container for the menu */
 
#menuContainer  {
 
float:left;
 
width: 150px;
 
padding: 20px 0px;
 
background-color: #D65664;
 
border-top: 20px solid #963F20;
 
font-family: "Lucida Sans Unicode", "Lucida Grande", sans-serif;
 
}
 
 
/* Creates the container for the content */
 
#contentContainer {
 
padding-top:20px;
 
padding-right:10px;
 
margin-bottom: 20px;
 
width: 800px;
 
padding-left: 20px;
 
float: left;
 
border-top: 20px solid #963F20;
 
background-color: #fff;
 
font-family: "Lucida Sans Unicode", "Lucida Grande", sans-serif;
 
}
 
 
 
/*Set up height place holder for the banner*/
 
#bannerContainer {
 
height:200px;
 
margin:auto;
 
text-align:center;
 
color: #84F22A;
 
}
 
 
/*VISUAL STYLE (TABLES, FONTS, LINKS, IMAGES, UL) */
 
 
/*Change the styling of text for everything inside main container*/
 
#mainContainer p {
 
font-size: 13px;
 
color: #000000;
 
}
 
 
/*This changes the color and font family */
 
#contentContainer h1, h2, h3, h4, h5, h6 {
 
font-family: "Lucida Sans Unicode", "Lucida Grande", sans-serif;
 
color: #534743;
 
border-bottom: none;
 
font-weight: bold;
 
margin-top:10px;
 
}
 
 
/*Style of the links - links are different inside the menu */
 
#contentContainer a {
 
font-weight: bold;
 
color: #84FD2C;
 
}
 
 
  /* Styling links on hover- links are different inside the menu */
 
#contentContainer a:hover {
 
color: #963F20;
 
}
 
 
/*Change the styling of tables */
 
        #contentContainer table {
 
    border: 2px solid #534743;
 
    border-collapse: collapse;
 
    margin: auto;
 
    margin-bottom: 15px;
 
    margin-top: 15px;
 
    margin-right: 10px;
 
    margin-left: 10px;
 
    }
 
 
/*Change the styling of table cells*/
 
    #contentContainer  td {
 
    background-color: #fff;
 
    padding: 10px;
 
    border: 2px solid #534743;
 
    border-collapse: collapse;
 
    vertical-align: text-top;
 
    }
 
 
 
/*Change the styling of table headers */
 
    #contentContainer th {
 
    background-color: #F4F0D8;
 
    padding: 10px;
 
    border: 2px solid #534743;
 
    border-collapse: collapse;
 
    vertical-align: text-top;
 
    }
 
 
 
 
 
/*MENU STYLING */
 
 
/*Styling for the links in the menu */
 
#menuContainer a {
 
color: #fff;
 
text-decoration:none;
 
font-weight: bold;
 
}
 
 
/* Sets the style for lists inside menuContainer  */
 
#menuContainer ul {
 
list-style: none;
 
margin-left:0px;
 
}
 
 
/*Styles the list items to become menu buttons */
 
#menuContainer ul li {
 
text-align: center;
 
display: block;
 
width: 100%;
 
height:30px;
 
padding-top:10px;
 
}
 
 
/*For the menu buttons, changes the color when hovering*/
 
#menuContainer li:hover {
 
color:  #FFF;
 
background-color: #963F20;
 
}
 
 
/*Submenus are not displayed as default*/
 
#menuContainer li ul {
 
display: none;
 
padding-top:15px;
 
margin-left: -19px;
 
}
 
 
/*Submenus are displayed when hovering the menu button */
 
#menuContainer li:hover ul {
 
/*display: inline-block; */
 
display: block;
 
position: absolute;
 
float:right;
 
margin-left: 150px;
 
margin-top:-42px;
 
}
 
 
/*Style the submenu buttons*/
 
#menuContainer li ul li{
 
background-color: #84FD2C;
 
padding-left:20px;
 
padding-right:20px;
 
height:30px;
 
padding-top:10px;
 
margin-top:-2px;
 
color: #332B29;
 
width: 170px;
 
}
 
 
/*CLASSES */
 
 
/*Clear class for all the pages, adds spacing too*/
 
.clear{
 
clear:both;
 
height: 10px;
 
}
 
 
 
/* highlight box for special messages */
 
          .highlightBox {
 
            width:500px;
 
            margin:auto;
 
            background-color: #F4F0D8;
 
    margin-bottom: 15px;
 
    margin-top: 15px;
 
    padding: 15px;
 
    padding-top: 5px;
 
            }
 
 
</style>
 
<!-- End of CSS -->
 
  
  
 
</html>
 
</html>

Latest revision as of 03:59, 19 September 2015

Collaborations


a. communicating with other iGEM teams

#Korean Regional Meetup 8/15 @ Lotte hotel Athen’s Garden

The three Korean teams gathered together and presented their own projects. We had an opportunity to show our idea and receive comments during Q&A sessions. Particularly, one overgraduate team called Korea_U_Seoul team asked us why we used E.coli instead of other microorganisms. We answered that it is for accessibility. Since our project is headed toward the welfare of farmers, we focus on the technology that is “available” and “easy” for them to use.

We also offered some opinions about two other teams. Three Korean teams collaborated to achieve better at Giant Jamboree. It was indeed a great time.

#i GEM mentors

Gha Young Lee, David Brown, Ricardo Chavez We have applied for Pilot Mentorship Program, and were able to meet three great mentors who had experienced Giant Jamboree. In particular, Gha Young helped us a lot. She shared her experience about preparing for Giant Jamboree. We can’t wait until meeting her at Boston :) Also, we have skyped twice during the summer vacation( 7/1/15 10AM and 8/17/15 11 PM in Korean time) and got advice about part submission, human practice and the purpose of our project.


b. communicating with Bio Ethanol Research Institutes

#Jeon-nam University Bioethanol Research Institute 8/19



We started exchangin emails with JU Bioethanol Research Institute on August 19th. We not only introduced our bioengineering project but also Our questions were related to the problems that this institute encounters during their research. It answered that the economic feasibility and construction of infrastructure were the main problem it often faces.


c. Testing other teams’ systems

We’ve tested some systems of other iGEM teams such as Korea_U_Seoul,Nankai and Paris-Bettencourt.