|
|
| (4 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| =Summary Page= | | =Project Summary= |
| =Research Plan= | | =Project Description= |
| ==Background & Motivations== | | ==Motivation== |
| Scientific laboratories in the biological sciences produce and manage a wide variety of information. Each laboratory has developed its own mechanisms for curating, archiving, and sharing this information when appropriate. However, most of these approaches are severely hindered by a lack of integration with modern information technologies. As a result biological information is frequently incomplete, difficult to search, and out of date. These shortcomings lead to a serious reduction in the overall efficiency of biological research, and are a particular glaring problem in light of the existing technologies for publishing and organizing information widely utilized in other fields. The slow pace of adoption of internet and information technologies by biological scientists has been highlighted in the press lately [nature refs], but the problem still persists.
| | ==Research Plan== |
|
| |
|
| ===Equipment=== | | ===Information=== |
| There is a large body of important information associated with laboratory equipment, including: instructions for usage, control data, maintenance records, troubleshooting tips, etc. This information is typically stored locally in labs and often is not stored in a persistent manner (e.g., it is bound up in the lab “expert” for a particular machine and promptly disappears upon departure from the lab). Most importantly, this information is rarely shared widely among labs even though many utilize the same make and model of equipment.
| | ====Overview==== |
|
| |
|
| ==Laboratory Information Management== | | ====Significance==== |
| *Individual laboratories and collaborative groups generate many types of information.
| |
| *#Laboratory protocols -- recipes, expected results, tips and tricks
| |
| *#equipment -- operation, calibration, expected results
| |
| *#Current research plans/researchers --
| |
| *#research results
| |
| *#Stocks -- locations/quantities of chemicals, biologicals
| |
| *#Information aggregation -- strains, collections of useful tools
| |
| *Ways to access information
| |
| *#protocols
| |
| *#*current access; methods section of published research, aggregated protocol collecions (CPMB), disparate collections of protocols from lab web pages, unpublished lab protocols & personal communication
| |
| *#*problems; not detailed enough to enable replication, nature wiki article
| |
| *#equipment
| |
| *#*current access:company documentation, personal communication
| |
| *#*company documentation is often insufficient to troubleshoot problems, get ideas on expected results, et cetera. individual expertise within a lab, often departs with individual. no mechanisms for sharing this information between labs other than direct contact.
| |
| *#current information on what's happening in lab
| |
| *#*individual laboratory websites, publications, personal communication, conferences (posters & talks)
| |
| *#*often out of date; current information largely unavailable... not all of it due to secrecy (ie., they talk about it at conferences, you just have to be there).
| |
| *#research results
| |
| *#*peer-reviewed publication
| |
| *#*often insufficient, not always easy to find information; negative results, smaller results that don't go into paper
| |
| *#stocks
| |
| *#*internal laboratory documents, LABASE (Chan & Endy, antiquity)
| |
| *#*historical records lacking,
| |
| *#information aggregation
| |
| *#*disparate online and offline information
| |
| *#*could aggregate data to ease access to information; i.e, e. coli genotypes
| |
| *Some communities have been able to harness information for tight knit communities. For example C. elegans. This works when community is very centralized; everybody knows each other. Not many communities have the centralization, resources, tech savvy to be able to pull something like that off. In addition, Information must be very structured. Still miss out on other many other sets of data. Not very extendable on the fly.
| |
|
| |
|
| ==OpenWetWare== | | ====Preliminary results==== |
| *OpenWetWare was an experiment in trying to see if we could use a wiki to solve some of these problems.
| | |
| **A wiki is...
| | ====Proposal==== |
| **OpenWetWare is...
| | |
| *OpenWetWare, going through above problems
| | ===Community=== |
| *#protocols
| | ====Overview==== |
| *#equipment
| | |
| *#research&researchers
| | ====Significance==== |
| *#research results
| | |
| *#lims
| | ====Preliminary results==== |
| *#information aggregation
| | |
| | ====Proposal==== |
| | |
| | ===Education=== |
| | ====Overview==== |
| | |
| | ====Significance==== |
| | |
| | ====Preliminary results==== |
| | |
| | ====Proposal==== |
| | |
| | ==Assessment== |
| | How do we evaluate success? Analysis and assessment. |
| | |
| | ==Project management== |
| | Who runs what? Oversight. Hiring. Stabilitization of backend. Long term support. |
| | |
| | =Budget= |
| | |
| | =Facilities, equipment and other resources= |
