Team:BU Wellesley Software/eLabNotebook

From 2011.igem.org

(Difference between revisions)
Line 23: Line 23:
/*actual content styles*/
/*actual content styles*/
-
body {width: 860px; margin:auto;}
+
body {width: 800px; margin:auto;}
#bu-wellesley_wiki_content {height:auto; line-height:100%;}
#bu-wellesley_wiki_content {height:auto; line-height:100%;}
-
#bu-wellesley_wiki_content a {color:#69d01d;}
+
/*#bu-wellesley_wiki_content a {color:#69d01d;}*/
-
#bu-wellesley_wiki_content a:hover {text-decoration:none; color:#bababa;}
+
#bu-wellesley_wiki_content a:hover {text-decoration:none; color:#3d3f3c;}
-
</style>
+
.navbar li {color: #ffffff;}
-
<link rel="stylesheet" type="text/css" href="http://cs.wellesley.edu/~hcilab/iGEM_wiki/css/ProjectSpecific.css">
+
.navbar li a {color: #ffffff;}
 +
.navbar li a:hover {background:#69d01d; color: #ffffff;}
 +
/*only use for current page content header (i.e. Team, G-nomeSurferPro, etc)*/
 +
H6 {
 +
      font-family: Helvetica;
 +
      text-transform: uppercase;
 +
      text-decoration: none;
 +
      text-align: left;
 +
      color: #3d3f3c;
 +
      font-size: 32pt;
 +
    }
 +
</style>
 +
<link rel="stylesheet" type="text/css" href="http://cs.wellesley.edu/~hcilab/iGEM_wiki/css/Team.css">
</head>
</head>
<body class="basiclayout">
<body class="basiclayout">
-
 
<div id="bu-wellesley_wiki_content">
<div id="bu-wellesley_wiki_content">
 +
<p  style="text-align:center;"><a href="https://2011.igem.org/Team:BU_Wellesley_Software"><img src="http://cs.wellesley.edu/~hcilab/iGEM_wiki/images/banner.png" width="800px"></a></p>
<p  style="text-align:center;"><a href="https://2011.igem.org/Team:BU_Wellesley_Software"><img src="http://cs.wellesley.edu/~hcilab/iGEM_wiki/images/banner.png" width="800px"></a></p>
-
<!-- "previous page" action -->
 
-
<a class="prev browse left"></a>
 
-
<!-- root element for scrollable -->
 
-
<div class="scrollable" width="800px"> 
 
-
  <div class="items">
 
-
  <div id="comp">
 
-
<h1>Computational Team</h1>
 
-
<!-- Comp people's content here-->
 
-
<h5>Motivation</h5>
 
-
In this project, we were motivated by the disconnect that we observed between biologists' planning stages and their work in the lab, and by the large amount of time the biologists spent maintaining their notebooks during lab work.  Often, when biologists planned for the future, they would create a long-term plan with multiple involved steps, each building on the last, that would lead to interesting results.  However, there was still lots of work to be done before the biologists could begin their actual work: they had to figure out what protocols were necessary for each step of their work, check that there were enough supplies in the stock room for those protocols, and schedule lab time with other students to ensure that no two people needed to use a machine at the same time.  While iGEM teams had many creative solutions to these problems, including the use of Google Docs and spreadsheets to track timing, or Doodle polls for lab scheduling, there was no simple way for them to accomplish all of these tasks simultaneously. 
 
-
<!--Over the summer, we studied biologists in their lab and observed their work practices. We interviewed biologists and asked what were their challenges in the lab. We brainstormed with them what were possible solutions to their problems.
 
-
<a href="http://cs.wellesley.edu/~hcilab/iGEM_wiki/images/System/elabnotebook.png"><img style="float:right; width:280px; height:200px" src="http://cs.wellesley.edu/~hcilab/iGEM_wiki/images/System/elabnotebook.png"/></a>Largest among the challenges is the issue with contamination. Having to take gloves off to interact with a computer, to take notes, to handle certain things. Our solution was a tablet interface that replaced the traditional lab notebook and improved the use experience by allowing hands-free interaction. The tablet was designed to display biological protocols, tasks, notes, lab status, and more. The switching of applications was streamlined by allowing voice activation. We also explored the possibility of using gestures to navigate the application as well. -->
 
-
<br><br>
 
-
<h5><a name=eLabNotebookFuture></a>Future Work:</h5>
 
-
 
-
In our next iteration of the eLabNotebook, we hope to improve the user interface on the iPad. Currently, the protocols visualization still depends on touch input. The hope is to move to gesture based input or voice commands to check off steps that have been completed during a protocol. In addition, reference material might also be considered as another integration, even something as simple as a Wikipedia link for any special terms. 
 
-
<br><br><br>
+
<div class="navbar">
-
<h5>Results:</h5>
+
<a href="https://2011.igem.org/Team:BU_Wellesley_Software/Team">Team</a>  
-
Ut eu nunc eget ante egestas egestas at eu metus. Integer quam justo,
+
<a href="https://2011.igem.org/Team:BU_Wellesley_Software/Project_Overview">Project Overview</a>  
-
vehicula non sodales id, consequat vitae eros.<br>
+
<a href="https://2011.igem.org/Team:BU_Wellesley_Software/Notebook">Notebook</a>
-
Aenean egestas, ipsum sed fringilla porta, erat mi facilisis lectus, quis elementum quam felis nec elit.
+
<a href="https://2011.igem.org/Team:BU_Wellesley_Software/Safety">Safety</a>  
-
+
<a href="https://2011.igem.org/Team:BU_Wellesley_Software/Acknowledgement">Acknowledgement</a>  
-
<br><br>
+
<a href="https://2011.igem.org/Team:BU_Wellesley_Software/Social">Fun</a>  
-
<h5>Ethical User Study practices:</h5>
+
<a href="https://2011.igem.org/Team:BU_Wellesley_Software/Gold">Medal Fulfillment</a>  
-
Aliquam in felis sit amet eros pharetra volutpat.
+
<a href="https://2011.igem.org/Team:BU_Wellesley_Software/Outreach">Outreach</a>
-
</div>
+
<a href="https://2011.igem.org/Team:BU_Wellesley_Software/Tips">Tips & Tricks</a>  
-
<div id="overview">
+
<a href="https://2011.igem.org/Team:BU_Wellesley_Software/Downloads_and_Tutorials">Downloads/Tutorials</a>  
-
<h1>Overview: eLabNotebook</h1>
+
</div>
-
<h5>Hypothesis Forming</h5>
+
-
<br><br>
+
-
The eLabNotebook is an electronic lab notebook that facilitates collaborative, effective, and safe assembly of biological systems. The eLabNotebook allows users to:
+
 +
<br>
 +
<h6>eLabNotebook</h6>
 +
 +
<div id="tracking_nav">
 +
JUMP TO...<br>
 +
<a href="#bu-wellesley_wiki_content">Top</a><br>
 +
<a href="#overview">Tool Overview</a><br>
 +
<a href="#results">Results</a><br>
 +
<a href="#futurework">Future Work</a>
 +
</div>
 +
 +
<div id="overview">
 +
<h1>Tool Overview</h1>
 +
<p>
 +
The eLabNotebook is an electronic lab notebook that facilitates collaborative, effective, and safe assembly of biological systems. The eLabNotebook allows users to:
 +
<p>
<ul>
<ul>
<li>Capture multimodal data inside and outside the lab with minimal effort</li>
<li>Capture multimodal data inside and outside the lab with minimal effort</li>
-
 
<li>Follow a protocol in the lab while modifying and annotating steps as needed</li>
<li>Follow a protocol in the lab while modifying and annotating steps as needed</li>
-
 
<li>Access a wide variety of digital resources</li>
<li>Access a wide variety of digital resources</li>
-
 
<li>Get an overview of current activity and progress</li>
<li>Get an overview of current activity and progress</li>
-
 
<li>share physical and digital resources in real-time</li>
<li>share physical and digital resources in real-time</li>
-
 
</ul>
</ul>
-
 
+
<p>
-
<br><br>
+
The implementation of the eLabNotebook entails:  
The implementation of the eLabNotebook entails:  
<ul>
<ul>
Line 92: Line 95:
<li>Visualizing current lab activity and progress
<li>Visualizing current lab activity and progress
<li>Designing for multiple contexts and devices
<li>Designing for multiple contexts and devices
-
<br><br>
+
</ul>
-
The eLabNotebook will be initially prototyped on the iPad platform. <br><br><br>
+
<p>The eLabNotebook will be initially prototyped on the iPad platform.  
-
+
<p>
-
<a href="#"><img id="download_button" src="http://cs.wellesley.edu/~hcilab/iGEM_wiki/images/temp_download_button.jpg"/></a>
+
In this project, we were motivated by the disconnect that we observed between biologists' planning stages and their work in the lab, and by the large amount of time the biologists spent maintaining their notebooks during lab work.  Often, when biologists planned for the future, they would create a long-term plan with multiple involved steps, each building on the last, that would lead to interesting results.  However, there was still lots of work to be done before the biologists could begin their actual work: they had to figure out what protocols were necessary for each step of their work, check that there were enough supplies in the stock room for those protocols, and schedule lab time with other students to ensure that no two people needed to use a machine at the same time.  While iGEM teams had many creative solutions to these problems, including the use of Google Docs and spreadsheets to track timing, or Doodle polls for lab scheduling, there was no simple way for them to accomplish all of these tasks simultaneously.
-
<br><br><br><br><br><br><br>
+
<p>
-
<h5>Demo Video</h5>
+
Over the summer, we studied biologists in their lab and observed their work practices. We interviewed biologists and asked what were their challenges in the lab. We brainstormed with them what were possible solutions to their problems. <a href="http://cs.wellesley.edu/~hcilab/iGEM_wiki/images/System/elabnotebook.png"><img style="float:right; width:280px; height:200px" src="http://cs.wellesley.edu/~hcilab/iGEM_wiki/images/System/elabnotebook.png"/></a>Largest among the challenges is the issue with contamination. Having to take gloves off to interact with a computer, to take notes, to handle certain things. Our solution was a tablet interface that replaced the traditional lab notebook and improved the use experience by allowing hands-free interaction. The tablet was designed to display biological protocols, tasks, notes, lab status, and more. The switching of applications was streamlined by allowing voice activation. We also explored the possibility of using gestures to navigate the application as well.
 +
<p>
 +
<b>Download: </b><a href="#"><img id="download_button" src="http://cs.wellesley.edu/~hcilab/iGEM_wiki/images/temp_download_button.jpg"/></a>
 +
 
</div>
</div>
-
<div id="wetlab">
+
 
-
<h1>Wetlab</h1>
+
<div id="results">
-
Lorem ipsum dolor sit amet, consectetur adipiscing elit. In et dictum
+
<h1>Results</h1>
-
leo. Maecenas porttitor augue nec arcu lacinia ultricies. Maecenas at
+
-
dictum augue. Proin eget odio ac mi tristique scelerisque.
+
-
<img style="width:400px; height:300px" src="http://cs.wellesley.edu/~hcilab/iGEM_wiki/images/temp_placeholder.png"/>Integer at
+
-
nisl nec purus laoreet condimentum sed semper dui. Duis feugiat, ligula
+
-
eu vehicula vulputate, sem nisl ornare neque, eu dictum lacus sapien
+
-
eu neque.
+
-
<br><br>
+
-
Vestibulum gravida, turpis tempus suscipit euismod, ipsum mi
+
-
tristique nibh, sed sagittis ante felis at urna. Suspendisse eu neque
+
-
vitae lorem elementum elementum sit amet ac ligula. Mauris vestibulum
+
-
Donec ac sapien erat. Proin id enim sed
+
-
dolor suscipit laoreet vitae sit amet ligula. Nam ultricies orci vitae
+
-
mauris egestas tincidunt. Vestibulum sit amet est dolor.
+
-
<br><br><br>
+
-
<h5>Results:</h5>
+
-
Ut eu nunc eget ante egestas egestas at eu metus. Integer quam justo,
+
-
vehicula non sodales id, consequat vitae eros.<br>
+
-
  Aenean egestas, ipsum sed fringilla porta, erat mi facilisis lectus, quis elementum quam felis nec elit.
+
-
+
-
  <br><br>
+
-
  <h5>Safety practices:</h5>
+
-
  Aliquam in felis sit amet eros pharetra volutpat.
+
</div>
</div>
-
 
 
-
  </div>
 
-
 
 
-
</div>
 
-
<!-- "next page" action -->
 
-
<a class="next browse right"></a>
 
-
 
-
<script>
 
-
// execute your scripts when the DOM is ready. this is mostly a good habit
 
-
$(function() {
 
-
// initialize scrollable
+
<div id="futurework">
-
$(".scrollable").scrollable();
+
<h1>Future Work</h1>
-
 
+
<p>
-
//move the scrollable content to show the middle section
+
<ul>
-
                        var api = $(".scrollable").data("scrollable");
+
<li>In our next iteration of the eLabNotebook, we hope to improve the user interface on the iPad. Currently, the protocols visualization still depends on touch input. The hope is to move to gesture based input or voice commands to check off steps that have been completed during a protocol. In addition, reference material might also be considered as another integration, even something as simple as a Wikipedia link for any special terms. 
-
                        api.seekTo(1, 500);
+
</ul>
-
});
+
</div>
-
</script>
+
-
+
</div><!--end bu-wellesley_wiki_content div-->
</div><!--end bu-wellesley_wiki_content div-->

Revision as of 02:23, 13 September 2011

BU-Wellesley iGEM Team: eLabNotebook

Team Project Overview Notebook Safety Acknowledgement Fun Medal Fulfillment Outreach Tips & Tricks Downloads/Tutorials

eLabNotebook

Tool Overview

The eLabNotebook is an electronic lab notebook that facilitates collaborative, effective, and safe assembly of biological systems. The eLabNotebook allows users to:

  • Capture multimodal data inside and outside the lab with minimal effort
  • Follow a protocol in the lab while modifying and annotating steps as needed
  • Access a wide variety of digital resources
  • Get an overview of current activity and progress
  • share physical and digital resources in real-time

The implementation of the eLabNotebook entails:

  • Developing light-weight interaction techniques for capturing information
  • Considering strategies for organizing and sharing heterogeneous information
  • Visualizing current lab activity and progress
  • Designing for multiple contexts and devices

The eLabNotebook will be initially prototyped on the iPad platform.

In this project, we were motivated by the disconnect that we observed between biologists' planning stages and their work in the lab, and by the large amount of time the biologists spent maintaining their notebooks during lab work. Often, when biologists planned for the future, they would create a long-term plan with multiple involved steps, each building on the last, that would lead to interesting results. However, there was still lots of work to be done before the biologists could begin their actual work: they had to figure out what protocols were necessary for each step of their work, check that there were enough supplies in the stock room for those protocols, and schedule lab time with other students to ensure that no two people needed to use a machine at the same time. While iGEM teams had many creative solutions to these problems, including the use of Google Docs and spreadsheets to track timing, or Doodle polls for lab scheduling, there was no simple way for them to accomplish all of these tasks simultaneously.

Over the summer, we studied biologists in their lab and observed their work practices. We interviewed biologists and asked what were their challenges in the lab. We brainstormed with them what were possible solutions to their problems. Largest among the challenges is the issue with contamination. Having to take gloves off to interact with a computer, to take notes, to handle certain things. Our solution was a tablet interface that replaced the traditional lab notebook and improved the use experience by allowing hands-free interaction. The tablet was designed to display biological protocols, tasks, notes, lab status, and more. The switching of applications was streamlined by allowing voice activation. We also explored the possibility of using gestures to navigate the application as well.

Download:

Results

Future Work

  • In our next iteration of the eLabNotebook, we hope to improve the user interface on the iPad. Currently, the protocols visualization still depends on touch input. The hope is to move to gesture based input or voice commands to check off steps that have been completed during a protocol. In addition, reference material might also be considered as another integration, even something as simple as a Wikipedia link for any special terms.

Retrieved from "http://2011.igem.org/Team:BU_Wellesley_Software/eLabNotebook"