Difference between revisions of "Team:Michigan Software/HP/Silver"

Line 1: Line 1:
 
{{Michigan_Software}}
 
{{Michigan_Software}}
 
<html>
 
<html>
−
 
+
<body>
−
<div class="clear"></div>
+
<header>
−
 
+
        <div class="container-fluid">
−
 
+
            <div class="row">
−
<div class="column full_size">
+
              <div class="col-12" id = "headerImage">
−
 
+
                  <img class = "Header-img" src="https://static.igem.org/mediawiki/2017/8/8d/MichiganSoftware_2017_HP.png" />
−
<h1>Silver Medal Human Practices</h1>
+
                  <h1 id = "headerImageh1">Human Practices - Silver</h1>
−
<p>iGEM teams are leading in the area of Human Practices because they conduct their projects within a social/environmental context, to better understand issues that might influence the design and use of their technologies.</p>
+
              </div>
−
<p>Teams work with students and advisors from the humanities and social sciences to explore topics concerning ethical, legal, social, economic, safety or security issues related to their work. Consideration of these Human Practices is crucial for building safe and sustainable projects that serve the public interest. </p>
+
            </div>
−
<p>For more information, please see the <a href="https://2017.igem.org/Competition/Human_Practices">Human Practices page</a>.</p>
+
        </div>
−
</div>
+
      </header>
−
 
+
      <div class="top-buffer container-fluid">
−
<div class="clear"></div>
+
        <div class="col-xs-1"></div>
−
 
+
        <div class="col-xs-10">
−
<div class="column half_size">
+
            <div>
−
<h3>Silver Medal Criterion #3</h3>
+
              <br>
−
<p>Convince the judges you have thought carefully and creatively about whether your work is safe, responsible and good for the world. You could accomplish this through engaging with your local, national and/or international communities or other approaches. Please note that standard surveys will not fulfill this criteria.</p>
+
              <br>
−
</div>
+
              <br>
−
 
+
              <br>
−
<div class="column half_size">
+
              <br>
−
<h5>Some Human Practices topic areas </h5>
+
              <br>
−
<ul>
+
              <p>
−
<li>Philosophy</li>
+
              <h1 class="grey-text heading-weight" align = "center">Protocol Model Development</h1>
−
<li>Public Engagement / Dialogue</li>
+
              <p>
−
<li>Education</li>
+
                  <br>
−
<li>Product Design</li>
+
              <div class="row" style="border-bottom:thin solid;"></div>
−
<li>Scale-Up and Deployment Issues</li>
+
              <br>
−
<li>Environmental Impact</li>
+
              <br>
−
<li>Ethics</li>
+
              <p id = "doubleSpace" class="p-font grey-text">Prior to beginning the development of ProtoCat 3.0, we did research
−
<li>Safety</li>
+
                  on currently used protocol models. We began by brainstorming with members of our team who had
−
<li>Security</li>
+
                  lab experience to get a foundation upon which we could improve. We tested the robustness of
−
<li>Public Policy</li>
+
                  this initial model by trying to represent the protocols uploaded to ProtoCat 2.0 with our new
−
<li>Law and Regulation</li>
+
                  model, tweaking and updating it along the way. Once we felt our model could adequately handle
−
<li>Risk Assessment</li>
+
                  the protocols we anticipated in ProtoCat 3.0, we met with our adviser, Dr. Santiago Schnell,
−
</ul>
+
                  and ran our protocol model by him. Taking his feedback, we went back and further refined our
−
</div>
+
                  model to the one that we use in our current implementation of ProtoCat 3.0.
−
 
+
              </p>
−
 
+
              <br>
−
<div class="column half_size">
+
              <br>
−
<h5>What should we write about on this page?</h5>
+
              <br>
−
<p>On this page, you should write about the Human Practices topics you considered in your project, and document any special activities you did (such as visiting experts, talking to lawmakers, or doing public engagement). This should include all of the work done for the Silver Medal Criterion #3. Details for your Gold medal work and/or work for the two Human Practices special prizes should be put on those specified pages.</p>
+
              <br>
−
</div>
+
              <p>
−
 
+
              <h1 class="grey-text heading-weight" align = "center">Standard Protocol Format</h1>
−
 
+
              </p>
−
<div class="column half_size">
+
              <br>
−
<h5>Inspiration</h5>
+
              <div class="row" style="border-bottom:thin solid;"></div>
−
<p>Read what other teams have done:</p>
+
              <br>
−
<ul>
+
              <br>
−
<li><a href="https://2014.igem.org/Team:Dundee/policypractice/experts">2014 Dundee </a></li>
+
              <p id = "doubleSpace" class="p-font grey-text">Standardization in synthetic biology has gained a lot of traction,
−
<li><a href="https://2014.igem.org/Team:UC_Davis/Policy_Practices_Overview">2014 UC Davis </a></li>
+
                  such as the BioBrick and Registry of Standardized Biological Parts. However, the procedures
−
<li><a href="https://2013.igem.org/Team:Manchester/HumanPractices">2013 Manchester </a></li>
+
                  used to generate them tend to be diverse in nature, with a bacterial transformation
−
<li><a href="https://2013.igem.org/Team:Cornell/outreach">2013 Cornell </a></li>
+
                  protocol likely requiring different information than a ligation protocol. Online protocol
−
</ul>
+
                  repositories must account for such differences when creating their data models, which will
−
</div>
+
                  usually require either a simplified model (such as solely text-based) or a more arduous
−
 
+
                  upload process. These different models become a problem when trying to share protocols between
−
 
+
                  the repositories, because the formats that the protocols are stored in are not compatible and
−
 
+
                  require an external conversion tool to get from one format to the other. In order to begin
 +
                  working towards a standardized protocol format format, we reached out to OpenWetWare and
 +
                  Protocols.io, two well known protocol repositories. We have began discussing how we will
 +
                  reconcile our respective protocol models in order to get the best protocol model. The first
 +
                  steps have been taken to build a cooperative relationship and create a standard protocol that
 +
                  will help make protocols even easier to use, test, review, and design.
 +
              </p>
 +
              <br>
 +
              <br>
 +
              <br>
 +
            </div>
 +
        </div>
 +
      </div>
 +
      <footer id = "footer">
 +
        <div class="container-footer bg-3">
 +
            <div class = "row">
 +
              <div class = "col-sm-12 text-center">
 +
                  <h3 id = "h3Header">Important Links:</h3>
 +
                  <table class = "Footer-Table" align = "center">
 +
                      <tr>
 +
                        <td>
 +
                          <p><a href="https://2017.igem.org/Team:Michigan_Software/Overview">Overview</a></p>
 +
                        </td>
 +
                        <td>
 +
                          <p><a href="https://2017.igem.org/Team:Michigan_Software/Results">Results</a></p>
 +
                        </td>
 +
                    </tr>
 +
                    <tr>
 +
                        <td>
 +
                          <p><a href="https://2017.igem.org/Team:Michigan_Software/Installation">Installation</a></p>
 +
                        </td>
 +
                        <td>
 +
                          <p><a href="https://2017.igem.org/Team:Michigan_Software/Collaboration">Collaboration</a></p>
 +
                        </td>
 +
                    </tr>
 +
                    <tr>
 +
                        <td>
 +
                        <p><a href="https://2017.igem.org/Team:Michigan_Software/HP">HP Silver</a></p>
 +
                        </td>
 +
                        <td>
 +
                          <p><a href="https://2017.igem.org/Team:Michigan_Software/Attributions">Attributions</a></p>
 +
                        </td>
 +
                    </tr>
 +
                   
 +
                    <td>
 +
                        <p><a href="https://2017.igem.org/Team:Michigan_Software/Demonstration">Demonstration</a></p>
 +
                    </td>
 +
                    </tr>
 +
                  </table>
 +
              </div>
 +
            </div>
 +
        </div>
 +
      </footer>
 +
  </body>
 
</html>
 
</html>

Revision as of 23:40, 30 October 2017

Human Practices - Silver







Protocol Model Development




Prior to beginning the development of ProtoCat 3.0, we did research on currently used protocol models. We began by brainstorming with members of our team who had lab experience to get a foundation upon which we could improve. We tested the robustness of this initial model by trying to represent the protocols uploaded to ProtoCat 2.0 with our new model, tweaking and updating it along the way. Once we felt our model could adequately handle the protocols we anticipated in ProtoCat 3.0, we met with our adviser, Dr. Santiago Schnell, and ran our protocol model by him. Taking his feedback, we went back and further refined our model to the one that we use in our current implementation of ProtoCat 3.0.





Standard Protocol Format




Standardization in synthetic biology has gained a lot of traction, such as the BioBrick and Registry of Standardized Biological Parts. However, the procedures used to generate them tend to be diverse in nature, with a bacterial transformation protocol likely requiring different information than a ligation protocol. Online protocol repositories must account for such differences when creating their data models, which will usually require either a simplified model (such as solely text-based) or a more arduous upload process. These different models become a problem when trying to share protocols between the repositories, because the formats that the protocols are stored in are not compatible and require an external conversion tool to get from one format to the other. In order to begin working towards a standardized protocol format format, we reached out to OpenWetWare and Protocols.io, two well known protocol repositories. We have began discussing how we will reconcile our respective protocol models in order to get the best protocol model. The first steps have been taken to build a cooperative relationship and create a standard protocol that will help make protocols even easier to use, test, review, and design.