|
|
| Line 1: |
Line 1: |
| | + | {{East_Chapel_Hill}} |
| | <html> | | <html> |
| | | | |
| − | <style>
| |
| − | #top_title {display: none;}
| |
| − | #sideMenu {display: none;}
| |
| − | #content {margin: auto; padding: 0; width: 60%;}
| |
| − | </style>
| |
| | | | |
| | | | |
| Line 11: |
Line 7: |
| | | | |
| | | | |
| − | <head> | + | <div class="clear"></div> |
| − | <title>East Chapel Hill Highschool iGem</title>
| + | |
| − | <meta charset="utf-8">
| + | |
| − | <meta name="viewport" content="width=device-width, initial-scale=1">
| + | |
| − | <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css">
| + | |
| − | <script src="https://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js"></script>
| + | |
| − | <script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/js/bootstrap.min.js"></script>
| + | |
| | | | |
| | + | <div class="column full_size"> |
| | + | <h1>Collaborations</h1> |
| | | | |
| − | <style>
| + | <p> |
| − | /* Remove the navbar's default margin-bottom and rounded borders */
| + | 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> |
| − | .navbar {
| + | |
| − | margin-bottom: 0;
| + | |
| − | margin-right: 0;
| + | |
| − | border-radius: 0;
| + | |
| − | width: 100%;
| + | |
| − | /*background-color: #ffcccc;*/
| + | |
| − | }
| + | |
| − | | + | |
| − | body {
| + | |
| − | background-color: black;
| + | |
| − | }
| + | |
| − |
| + | |
| − | */
| + | |
| − | /* Set height of the grid so .sidenav can be 100% (adjust as needed) */
| + | |
| − | .row.content {height: 450px}
| + | |
| − |
| + | |
| − | /* Set gray background color and 100% height */
| + | |
| − | .sidenav {
| + | |
| − | padding-top: 20px;
| + | |
| − | background-color: black;
| + | |
| − | height: 100%;
| + | |
| − | }
| + | |
| − |
| + | |
| − | ul.yourclass
| + | |
| − | { display: inline-block;
| + | |
| − |
| + | |
| − | padding-rigth: 15px;
| + | |
| − | }
| + | |
| − | | + | |
| − |
| + | |
| − |
| + | |
| − | /* Set black background color, white text and some padding */
| + | |
| − | footer {
| + | |
| − | background-color: #555;
| + | |
| − | color: white;
| + | |
| − | padding: 15px;
| + | |
| − | }
| + | |
| − |
| + | |
| − | /* On small screens, set height to 'auto' for sidenav and grid */
| + | |
| − | @media screen and (max-width: 767px) {
| + | |
| − | .sidenav {
| + | |
| − | height: auto;
| + | |
| − | padding: 15px;
| + | |
| − | }
| + | |
| − | .row.content {height:auto;}
| + | |
| − | }
| + | |
| − | </style>
| + | |
| − | | + | |
| − | | + | |
| − | </head>
| + | |
| − | <body>
| + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | <nav class="navbar navbar-inverse">
| + | |
| − | <div class="container-fluid">
| + | |
| − | <div class="navbar-header">
| + | |
| − | <button type="button" class="navbar-toggle" data-toggle="collapse" data-target="#myNavbar">
| + | |
| − | <span class="icon-bar"></span>
| + | |
| − | <span class="icon-bar"></span>
| + | |
| − | <span class="icon-bar"></span>
| + | |
| − | </button>
| + | |
| − | </div>
| + | |
| − | <div class="collapse navbar-collapse" id="myNavbar">
| + | |
| − | <ul class="nav navbar-nav">
| + | |
| − | <li><img align="middle" style="width:100%" height="50px" src="https://static.igem.org/mediawiki/2017/8/89/T--East_Chapel_Hill--Icon0.png"></img> </li>
| + | |
| − | </ul>
| + | |
| − | <ul class="nav navbar-nav navbar-right">
| + | |
| − | <li class="active"><a href="https://2017.igem.org/Team:East_Chapel_Hill">Home</a></li>
| + | |
| − | <li>
| + | |
| − | <a href="https://2017.igem.org/Team:East_Chapel_Hill/Team">Team </a>
| + | |
| − |
| + | |
| − | </li>
| + | |
| − | <li><a href="Project.html">Project</a></li>
| + | |
| − | <li><a href="https://2017.igem.org/Team:East_Chapel_Hill/results">Results</a></li>
| + | |
| − | <li><a href="https://2017.igem.org/Team:East_Chapel_Hill/testHumanPractices">Human Practices </a></li>
| + | |
| − | <li><a href="https://2017.igem.org/Team:East_Chapel_Hill/Attributions">Attributions</a></li>
| + | |
| − | <li><a href="https://2017.igem.org/Team:East_Chapel_Hill/Collaborations.html">Collaborations</a></li>
| + | |
| − | <li>
| + | |
| − | <a href="https://2017.igem.org/Team:East_Chapel_Hill/Awards">Awards </a>
| + | |
| − | </li>
| + | |
| − | | + | |
| − | | + | |
| − | </ul>
| + | |
| − | </div>
| + | |
| − | </nav>
| + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | <!-- div class="container-fluid" -->
| + | |
| − | <!-- div class="row content"-->
| + | |
| − | <div class="col-sm-2 sidenav">
| + | |
| − | <img align="middle" style="width:100%" height="900px" src="https://static.igem.org/mediawiki/2017/9/9d/EastChapelHillGIF.gif"></img>
| + | |
| − | </div>
| + | |
| − |
| + | |
| | | | |
| | + | <h3>Silver Medal Criterion #2</h3> |
| | + | <p> |
| | + | Complete this page if you intend to compete for the silver medal criterion #2 on collaboration. Please see the <a href="https://2017.igem.org/Judging/Medals">2017 Medals Page</a> for more information. |
| | + | </p> |
| | | | |
| | + | <div class="column half_size"> |
| | | | |
| | + | <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> |
| | + | 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 half_size"> |
| | + | <p> |
| | + | Here are some suggestions for projects you could work on with other teams: |
| | + | </p> |
| | | | |
| | <ul> | | <ul> |
| − | <li><b><center>Tasty-Style Videos <center></b>
| + | <li> Improve the function of another team's BioBrick Part or Device</li> |
| − | <p>Taking inspiration from Buzzfeed’s Tasty videos, our team created an instructional video describing how to properly execute a serial dilution. In the video, we carefully went through the process and proper lab techniques needed when conducting a serial dilution. After filming and editing the video, we posted it to Youtube to expand the educational potential of our video. After proposing the idea of a “Tasty-style” video to iGEM Peshawar, the Peshawar team created a video documenting the lab techniques of transformations. Our intention in creating these videos is to teach viewers about common lab techniques that may aid them in their scientific endeavors.
| + | <li> Characterize another team's part </li> |
| − | </p>
| + | <li> Debug a construct </li> |
| − | </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><b><center>CloneCademy & Collaboration with TU Darmstadt </center></b>
| + | <li> Mentor a high-school team</li> |
| − | <p>Under the instruction of the TU Darmstadt iGEM team, our team contributed to the educational program of CloneCademy. CloneCademy is a series of learning modules with the purpose of teaching readers about biology and related fields, including biotechnology and the ethics of scientific research. Our team sent our tasty-style video playlist to TU Darmstadt so their team would be able to incorporate our lab-technique videos into their teaching program. | + | |
| − | </p>
| + | |
| − | | + | |
| − | </li> | + | |
| − | | + | |
| − | <li><b><center> Mini iGEM Convention </b> </center>
| + | |
| − | <p>On August 4-5th, we collaborated with the Gaston Day School team to host the Southeastern iGEM Mini Convention for iGEM teams geographically close to us. Although there were not as many teams present as we would have hoped for (just Gaston and Duke), this event gave each of us the opportunity to get closer with all teams and focus our time and energy into giving thorough and in-depth feedback and analysis on each other’s projects. We were in charge of contacting guest speakers in the Biological Engineering field who would be willing to give a lecture on the emerging and flourishing field of synthetic biology, including its ethical implications. After sending out over a 100 emails, we finally got positive responses, thus finalizing the schedule for the first day of the convention. | + | |
| − | </p>
| + | |
| − | | + | |
| − | <p>The following speakers were in attendance:</p> | + | |
| − | <ul> | + | |
| − | <p> -Danielle Tullman Ercek, Associate Professor of Chemical and Biological Engineering at Northwestern University: Discussed the way synthetic biology becomes part of a living system and redefines life. Also talked about the scope of synthetic biology, what it can achieve, and the applications and goals of the field.
| + | |
| − | </p>
| + | |
| − | | + | |
| − | <p>-Connor McFadden, UNC - Chapel Hill: Discussed the formal definition of synthetic biology, and the subfields and components of contemporary synthetic biology. </p>
| + | |
| − | <p>-Emma Miles, Duke iGEM : Discussed the ethical implications of synthetic biology related to its applications (human advancement), distribution (biofuel production), and procedure (status of living machines). Also illustrated the importance of bridging the disconnect which makes it hard for the public to accept synthetic biology projects due to lack of communication and education from the scientists in charge of implementation.
| + | |
| − | </p>
| + | |
| − | | + | |
| − | <p>All three teams brainstormed collaboration ideas such as the “Building with Bio Revamp”. </p>
| + | |
| − | | + | |
| − | <p>There were also many fun and lighthearted activities for all of us to partake in. For example, the Duke iGEM team conducted an interview asking us questions like “Why do you love science?”, “What is your favorite piece of lab equipment and why?”, “If you could say something to any microorganism what would it be?”, etc. We socialized over a dinner consisting of pasta and salad from Olive Garden, ice cream, and a movie to kick off the night. </p>
| + | |
| − | | + | |
| | </ul> | | </ul> |
| − | | + | </div> |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | </body> | + | |
| | | | |
| | | | |
| | </html> | | </html> |
East_Chapel_Hill
Collaborations
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.
Silver Medal Criterion #2
Complete this page if you intend to compete for the silver medal criterion #2 on collaboration. Please see the 2017 Medals Page for more information.
Which other teams can we work with?
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.
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.
Here are some suggestions for projects you could work on with other teams:
- Improve the function of another team's BioBrick Part or Device
- Characterize another team's part
- Debug a construct
- Model or simulating another team's system
- Test another team's software
- Help build and test another team's hardware project
- Mentor a high-school team
