Bench Press

The Crossroads of Science and Tech

Archive for the ‘CambridgeSoft’ tag

ChemBioDrawCrowdsource

without comments

One challenge with getting scientists to collaborate over the internet is the difficulty of representing scientific data in a way that can be readily manipulated and analyzed. Take Chemistry for an example. How does one share information about pathways and chemical structures in a way which allows for an entire group to collaborate on particular problems (e.g. synthesis pathways)?

Imaginitik, a startup specializing in software to help companies and institutions use crowdsourcing, and partially funded by Pfizer, has one such idea (HT: VentureBeat). Most scientists who are working or have worked in chemistry or biology are familiar with software company CambridgeSoft’s scientific software products like ChemDraw or BioDraw. What Imaginitik did was combine CambridgeSoft’s software with the collaborative features of Imaginitik’s Idea Central software to create ChemBioConnect, a crowdsourcing platform for a company or institution to deploy.

The idea is pretty simple. Imagitinik’s Idea Central platform creates web portal where scientists and management can list topics that can benefit from a multi-person collaborative approach and organize responses/suggestions/workflow and to rate individual ideas and contributions. But what differentiates ChemBioConnect from other life sciences collaboration solutions or more generic crowdsourcing platforms is integration with ChemBioDraw’s interface which provides more features than a standard collaboration platform (which will only let you share pictures/text) and a more familiar and robust user-interface than other life sciences-targeted solutions. Interestingly, Imagitinik’s platform also allows the creation of personality profiles (e.g. “creative” or “inquisitive”) to better help scientists network and target the right set of people to solve these problems. Not surprisingly, Imagitinik’s funder Pfizer has been rolling out this solution since Spring 2009!

A poorly scripted demo video is below (I personally think the speaker focuses too much time on basic ChemDraw functionality and less time on how this ties together with the collaborative features for my taste):

I, unfortunately, haven’t had the chance to actually try out the software (although reasonable pricing for enterprise software, I don’t have $50,000 – $500,000 to shell out to evaluate the software), but I think this is a great look into what a prototype for scientific collaborative software:

  • Web-based: The need for ease of access across many machines and locations and the need for a central repository with which to organize a group’s information generally means that collaborative platforms should be web-based or, if not, sufficiently web-like as to not be an issue.
  • Social networking features: It doesn’t have to be a full-fledged version of Facebook or MySpace, but a collaborative tool should encourage its users to network with one another and allow people to show off what projects they’ve contributed to. Not doing this fails to create the sense of community and personal attachment that crowdsourcing/community collaboration need
  • Integration with existing tools: It’s a sad fact of life that inertia is a big factor when people are deciding whether or not to use something. But it’s a fact nevertheless. The best way to encourage quality adoption is to make sure that tools that are commonly used by the target user base tie in nicely for two reasons. First, new users won’t have to learn a new set of techniques, interfaces, and processes to adopt. And secondly, the tools that currently exist oftentimes support features that are harder to develop and more useful than developers of new platforms would like to admit. Sure, lots of people (including this humble commentator) have bashed ChemDraw as clunky and awkward, but someone developing a chemistry crowdsourcing platform is likely to skimp on things like NMR-simulation or smooth rotation of a structure.
  • Managed workflow: Collaboration, even face-to-face, can be very difficult because information and suggestions and ideas are not organized effectively. It’s not enough to let people share their information and insights. You have to organize them and create tools with which to evaluate and encourage action on them.

As I haven’t actually put my hands on the software, I’m not sure if ChemBioConnect already supports these, but there are two additional features that I’d strongly suggest a collaboration platform to have:

  • Easy way to export work: Too often, developers of a platform or tool forget that there is a world beyond their innovations. This is especially true when people are testing out a piece of software for the first time – it’s important that they can quickly move a piece of work off the tool to integrate with the rest of their work schedule, whether it be in printed form, in the form of a presentation, on a PDF, in web page/HTML form, or even just as a industry file format to share with another. Going the extra mile to make this easy makes it easier for someone to try out your software as well as provides a valuable service that just may win an adopter over.
  • Semantics: This is harder to describe, but many web-based tools are very rigid, requiring a user to identify exactly what they want to do and figure out what part of the website is best suited for that particular type of work. Better, instead, to apply semantics/language processing to figure this out for the user. One example of a product that has done this is Google Calendar. Instead of requiring a user to try to figure out which fields correspond to what data when trying to create a calendar entry, a user can simply enter “Lunch with Jenny at Chez Carla on Sept 9, 2009 from 9 PM to 11 PM”. Google will decode the string and fill in the appropriate data. This feature is especially powerful for a collaborative tool where a user doesn’t want to have to figure out if something is a “task” or an “event” or an “idea” and doesn’t want to have to memorize what each of the tool’s special quirks and vocabulary are.

Does anyone else have any thoughts on ChemBioConnect or on other principles of good collaborative tool design?

Written by ben

August 10th, 2009 at 7:00 am