Difference between revisions of "Team:WLC-Milwaukee/Collaborations"

 
(11 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
{{WLC-Milwaukee}}
+
{{WLC-Milwaukee/header}}
 +
{{WLC-Milwaukee/CSS}}
 
<html>
 
<html>
 +
<head lang="en">
 +
    <meta charset="utf-8">
 +
    <meta http-equiv="x-ua-compatible" content="IE=edge; chrome=1">
 +
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
  
 +
    <!--IMPORT CSS-->
 +
    <link href="fonts.css" rel="stylesheet">
 +
    <link href="main.css" rel="stylesheet">
 +
    <!--IMPORT JQUERY-->
 +
    <script src="jquery.js.txt"></script>
  
 +
    <script>
 +
        //Include Header and Footer Files using jQuery
 +
        $(function(){
 +
            $("#header").load("header.html");
 +
            $("#footer").load("footer.html");
 +
        });
 +
    </script>
  
 +
    <!--PAGE TITLE-->
 +
    <title>WLC iGEM 2018 | Collaborations</title>
 +
</head>
  
  
 +
<body>
  
−
<div class="clear"></div>
+
    <!--BEGIN HEADER IMPORT-->
 +
    <div id="header"></div>
 +
    <!--END HEADER IMPORT-->
  
−
 
+
    <div class="content">
−
<div class="column full_size">
+
          <!--CONTENT CONTAINER-->
−
<h1>Collaborations</h1>
+
          <div class="container">
−
 
+
            <div class="row centered header-image-container dark-overlay" style="background-image: url(https://static.igem.org/mediawiki/2018/0/06/T--WLC-Milwaukee--CollaborationsHeader.jpeg)">
−
<p>
+
                <img id="img" src="https://static.igem.org/mediawiki/2018/0/06/T--WLC-Milwaukee--CollaborationsHeader.jpeg">
−
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.
+
                <div class="header-image-text">
 +
                <h1>Collaborations</h1>
 +
                </div>
 +
            </div>        
 +
            <br/><br/>
 +
            <div class="col-lg">
 +
                    <p><strong>We collaborated with other iGEM teams</strong> in two primary ways: providing data through surveys and receiving assistance in dealing with a growing team from Cornell iGEM.  
 +
We provided data to the IIT Kanpur iGEM Team for their project that worked with other aspects of water pollution, namely detergent degradation, which is one area we are interested in as a team.
 
</p>
 
</p>
 +
            </div> 
 +
           
 +
            <div class="row centered">
 +
                <img width=50% alt="Image 1" id="img" src="https://static.igem.org/mediawiki/2018/0/0a/T--WLC-Milwaukee--KanpurCollab.png">
 +
            </div>     
 +
           
 +
            <div class="col-lg">
 +
                    <p>Perhaps most significantly, we also collaborated with the Cornell iGEM team after a member of our lab met with, and was able to tour the Cornell iGEM Lab spaces over the summer! This initial interaction and discussion of how the Cornell iGEM team is organized led to future collaboration between our two teams looking at how as a team we can practically implement some of the strategies Cornell iGEM has used to manage their large team size. We have been excited to have a large influx of members this fall, but have struggled to effectively communicate and delegate assignments for the team. As a result, the methods for team member evaluation, establishment of sub-team leads, and meeting schedules with the various sub-team leads that we received from Cornell iGEM have aided us greatly in setting more concrete standards for communication and team operation. Additionally, we have been trying to find a way to better ingrain our iGEM team into our institutions research program and with some help from the Cornell team we have made significant progress in setting standards of evaluation and a more defined structure for our team. This necessary structure and method of evaluation were previously lacking in our team, but with the suggested revisions suggested we will now be able to be more formally recognized by our home institution and receive official acknowledgement for our work. </p>
 +
            </div> 
 +
            <div class="row centered">
 +
                <img width=50% alt="Image 1" id="img" src="https://static.igem.org/mediawiki/2018/1/1d/T--WLC-Milwaukee--WeillHall.jpeg">
 +
            </div>     
 +
                      <div class="col-lg">
 +
                    <p>Finally, we have also been immensely grateful to collaborate with a team of software developers at our home institution, W.A.S.D., to construct and implement our Wiki! They have done amazing work taking our ideas and turning them into a well-structured and beautiful Wiki that allows us to display our work in a clear and organized format. We couldn’t have completed our Wiki without the help of Elijah Tesch, John Sell, and Tyler Kemnitz, and we feel that this collaboration, although not with an outside iGEM team, has improved our project presentation immeasurably. </p>
 +
            </div>             
 +
            </div>
 +
           
 +
                               
 +
                   
 +
          </div>
 +
          <!--END CONTENT CONTAINER-->
 +
    </div>
  
−
<h3>Silver Medal Criterion #2</h3>
+
    <!--BEGIN FOOTER IMPORT-->
−
<p>
+
    <div id="footer"></div>
−
Complete this page if you intend to compete for the silver medal criterion #2 on collaboration. Please see the <a href="https://2018.igem.org/Judging/Medals">2018 Medals Page</a> for more information.
+
    <!--END FOOTER IMPORT-->
−
</p>
+
−
</div>
+
  
−
<div class="column two_thirds_size">
+
</body>
 +
</html>
  
−
<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 iGEM team collaboration silver medal criterion.
 
−
</p>
 
  
−
<p>
+
{{WLC-Milwaukee/footer}}
−
In order to meet the silver medal criteria on helping another team, you must complete this page and detail the nature of your collaboration with another iGEM team.
+
−
</p>
+
−
 
+
−
</div>
+
−
 
+
−
 
+
−
 
+
−
<div class="column third_size">
+
−
<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 simulate 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>
+
−
 
+
−
 
+
−
</html>
+

Latest revision as of 00:36, 18 October 2018

PLACEHOLDER

WLC iGEM 2018 | Collaborations

Collaborations



We collaborated with other iGEM teams in two primary ways: providing data through surveys and receiving assistance in dealing with a growing team from Cornell iGEM. We provided data to the IIT Kanpur iGEM Team for their project that worked with other aspects of water pollution, namely detergent degradation, which is one area we are interested in as a team.

Image 1

Perhaps most significantly, we also collaborated with the Cornell iGEM team after a member of our lab met with, and was able to tour the Cornell iGEM Lab spaces over the summer! This initial interaction and discussion of how the Cornell iGEM team is organized led to future collaboration between our two teams looking at how as a team we can practically implement some of the strategies Cornell iGEM has used to manage their large team size. We have been excited to have a large influx of members this fall, but have struggled to effectively communicate and delegate assignments for the team. As a result, the methods for team member evaluation, establishment of sub-team leads, and meeting schedules with the various sub-team leads that we received from Cornell iGEM have aided us greatly in setting more concrete standards for communication and team operation. Additionally, we have been trying to find a way to better ingrain our iGEM team into our institutions research program and with some help from the Cornell team we have made significant progress in setting standards of evaluation and a more defined structure for our team. This necessary structure and method of evaluation were previously lacking in our team, but with the suggested revisions suggested we will now be able to be more formally recognized by our home institution and receive official acknowledgement for our work.

Image 1

Finally, we have also been immensely grateful to collaborate with a team of software developers at our home institution, W.A.S.D., to construct and implement our Wiki! They have done amazing work taking our ideas and turning them into a well-structured and beautiful Wiki that allows us to display our work in a clear and organized format. We couldn’t have completed our Wiki without the help of Elijah Tesch, John Sell, and Tyler Kemnitz, and we feel that this collaboration, although not with an outside iGEM team, has improved our project presentation immeasurably.


WLC-Milwaukee