Carole Goble

1
A Web 2.0 Virtual Research Environment

• Carole Goble
• The University of Manchester, UK
• David De Roure
• University of Southampton, UK

2

• Motivation
• Realisation

myexperiment.org
3
E. Science laboris

• Workflows are the new rock and roll.
• Machinery for coordinating the execution of
  (scientific) services and linking together
  (scientific) resources.
• The era of Service Oriented Applications
• Repetitive and mundane boring stuff made easier

4
Taverna Workflow Workbench
5
Taverna domains

• Systems biology
• Proteomics
• Gene/protein annotation
• Microarray data analysis
• Medical image analysis
• Heart simulations
• High throughput screening
• Phenotypical studies
• Phylogeny
• Text mining
• Plants, Mouse, Human
• Astronomy

6
Recycling, Reuse, Repurposing

• Paul writes workflows for identifying biological
  pathways implicated in resistance to
  Trypanosomiasis in cattle
• Paul meets Jo. Jo is investigating Whipworm in
  mouse.
• Jo reuses one of Pauls workflow without change.
• Jo identifies the biological pathways involved in
  sex dependence in the mouse model, believed to be
  involved in the ability of mice to expel the
  parasite.
• Previously a manual two year study by Jo had
  failed to do this.

7
e-Services in the CLOUD

• Independent third party world-wide service
  providers of applications, tools and data sets.
  In the Cloud.
• 850 databases, 166 web servers Nucleic Acids
  Research Jan 2006
• My local applications, tools and datasets. In the
  Enterprise. In the laboratory.
• Easily incorporate new service without coding. So
  even more services from the cloud and enterprise.

8
e-Scientists in the CLOUD

• Individual life scientists, in under-resourced
  labs, who use other peoples applications, with
  little systems support.
• Exploratory workflows
• Developers (often) the users.
• Consumers are providers.

A distributed, disconnected community of
scientists.
9
Taverna has averaged 40 downloads per day since
2006
39,714 total sourceforge downloads to 22 October
2007 Ranked in sourceforge top 200 in June 2007
10
Scientific memes. Scientific virusesAccompany
their published outcomes400 Scufl workflows in
the Web Cloud
11
New Scientist
12
(No Transcript)
13
Tryps Twiki World
14
Tagging In the Web Cloud

• Picture of workflow in Flicker evidence of
  social tagging and networking

15
openwetware.org
16
Blogging The Lab

• Blogging the lab

17
Key evaluator and inspiration

• Cat De Roure
• Her idea.
• 15 years old.
• This is one of her MySpace pictures.
• Facebook, LinkedIn, blah blah
• Amazon, VivaLaDiva

18
myExperiment.org is

• A market place.
• A community social network.
• A gateway to other publishing environments.
• A federated repository
• A platform for launching workflows.
• Publishing self-describing Encapsulated
  myExperiment Objects.
• Mindful publication.
• Started March 2007.
• Closed beta since July 2007
• Open beta Oct 31 2007

19
myExperiment.org principles

• Make it easy to publish, easy to participate,
  easy to add value through mash-ups
• Use familiar techniques
• Shopping, Social networking, gaming
• Use off the shelf, open source web tooling, not
  restrictive portals. Keep it funky, keep it
  flexible, keep it extensible. Assume other people
  will add functionality.
• Ruby on Rails, Facebook platform
• Aim it at young people. Make it fun and
  attractive. Say no to 1970s library interfaces!

20
The world isnt just my workflows

• Kepler, Triana, BPEL
• Music Information Retrieval workflows
• Experimental plans (chemistry)
• And other stuff
• Matlab scripts
• Ontologies
• Computational Economics
• And the associated data!

21
The Demo
22
(No Transcript)
23
(No Transcript)
24
(No Transcript)
25
(No Transcript)
26
Scoping Challenges

• Workflow warehouse / federation of repositories
  Open Archives Initiative. Federated
  myExperiments. Sharepoint.
• Social space organised rich site Social
  discourse organised service / workflow space
  using curated semantics.
• Granularity and identifiers Rolling-up
  provenance. Id resolution
• Open vs protected content Quality, Reliability,
  Validation, Safety, Intellectual Property,
  Ownership, Secrecy, A duty of guardianship.
  Curation? Policing? Local data mixed with shared
  resources
• Desktop integration Google gadgets for workflows.
  Interacting with workflows through Office
  products.
• Workflow execution (WHIP) Workflows Hosted in
  Portals project
• Evolving the myExperiment software Community
  development
• Enabling Scientists added value through
  applications and collaborative tagging

27
Front End.A market place.A community social
network.User Participation.
28
A Market Place Shoe Shop?

• Shopping for Workflows and Services and Data
  should be as easy as shopping for shoes.
• Dont need to train people.
• Fuel for diagnostics. Find a similar workflow.
• Organic growth good and bad.
• We need good, organised metadata for automated
  use.
• Impedance mismatch
• Identity and Ontology Authority

29
Screen shot of bio Service shopping site
30
A Social Network and Collective Intelligence

• Source of large amount of metadata.
• Open tagging, folksonomies, blogging, profiles,
  recommendations.
• Masses -gt Curator pipeline?
• Social network analysis and e-tracking are
  valuable intelligence.
• How do we avoid being deafened by the shouting?
• What are the incentive models for scientists?

31
Leveraging and Serving The Long Tail of Users in
the Cloud

• Small labs or individuals
• Specialist workflows, Niche
• Expert and inexpert

• Big labs big groups
• Common de facto workflows

32
Challenge Semantic Sweatshop

• Service vocabularies and curation in the wild
• Keywords and tagging only goes some of the way.
• Curation
• Workflow metadata
• Find a workflow that is similar to what I want or
  need similar to this one. Or hers. Hmmmm.
• Recommendations, people profiles
• Fuel for discovery and diagnostics
• Pipeline from tag cloud to shop

33
Challenge Policy and Permissions without Tears
34
Back End.Federated repositories.A gateway to
other publishing environments.A platform for
launching workflows.User Participation.
35
Warehouse or Federation

• Community web site, federated repository.
• Multiple and My.
• Publish what I want when I want within the group
  I want.
• Mixed identity regimes an identity authority
• Open Archives Initiative. http//www.openarchives.
  org/
• The CombeChem project. http//www.combechem.org/

36
A gateway to other publishing services

• Tryps team already has a wiki
• Mash up with Facebook and workflow hosting apps.
• Bring functionality to the user. Cooperate! Dont
  Control.

37
We Need You! Cooperate, Don't Control

• A network of cooperating data services with
  simple interfaces which make it easy to work with
  content.
• Provides services
• Reuses the service of others.
• Support lightweight programming models so that it
  can easily be part of loosely coupled systems.
• You add a mashup!
• Workflows as content syndication?

38
Developers are Users Too.

• How to Develop and Grow myExperiment?
• Dont just listen to the Scientist.
• Get them to do the work!

39
Parties

• 28th 29th Sept 2006
• Hand picked Taverna users Taverna developers
• Facilitated by National Centre for e-Social
  Science
• AJAX based development
• Previous experiences from other projects
  CombeChem, myTea.

• A social networking environment for sharing any
  workflow
• A Taverna workflow run environment
• A multi-workflow launch environment

26/2/2007 myExperiment Slide 39
40
Hack Fests
41
Web 2 Implementation
42
Experiments are collections of stuff
Mash up
Application
43
EMO Examples

• A workflow with its inputs and the products of
  executing it (including logs), perhaps multiple
  times
• Data from instruments, coupled with log book
  entries
• A collection of all the digital items associated
  with one experimentincluding EMOs
• A collection of workflows with instructions and
  examples
• A reproducible academic paper with workflows and
  data

44
EMO Challenges

• What happens when the parts are scattered across
  multiple stores?
• What happens if someone updates a part?
• How will my EMO be discovered on the Web?
• How can I work with an EMO offline?
• What is the provenance of the EMO and its parts?
• What happens if a part is unavailable?

• How do I send an EMO by email?
• Can I turn an EMO into a tarball?
• Can I archive an EMO to a CDROM?
• If I delete this file will it break anyones
  EMOs?
• How do I trust an EMO?
• How do I handle an EMO RESTfully?
• Can my EMO link to objects outside the EMO?

45
Our Approach

• Designed for compatibility with Linked Data and
  with Open Archives Initiative Object Reuse and
  Exchange (OAI-ORE) which deals with compound
  object information and aims to build standardised
  and interoperable mechanisms

• An EMO file is a Resource Map describing all the
  distinct parts contained in the EMO
• Like a resource snapshot
• EMOs map to the familiar folders and files
  interface

46
Microsoft

• Cool front end
• Interface constructed using Silverlight
• Desktop savvy
• Feasibility of blending with desktop tools (e.g.
  excel) and exposing myExperiment objects through
  existing applications
• Mashed up services
• Demonstrate functionality mashups to build new
  services over the APIs including other science
  content in back end, EMOs and other content and
  information surfaced through other services
• Research Information Centre
• Windows workflows

24/5/2007 myExperiment Slide 46
47
Timeline

• Closed Beta released in July 2007
• Open Beta from November 2007
• In friends and family trials now with
  bioinformaticians and chemists
• Linking up to Triana
• Enactment and EMOs coming next
• Music and social science in pipeline
• API available
• Open Source
• Join us!

48
Take homes

• myExperiment is a Web 2.0 Environment for
  Scientists to share experiments
• Join us!
• David De Roure
• dder_at_ecs.soton.ac.uk
• Carole Goble
• carole.goble_at_manchester.ac.uk

49
Credits

• myGrid and CombeChem
• Matt Lee
• David Withers
• Don Cruickshank
• David Newman
• Mark Borkum
• Rob Procter
• Alex Voss
• Duncan Hull
• Katy Wolstencroft

• June Finch
• Ed Zaluska
• Jeremy Frey
• Simon Coles
• Danius Michaelides
• Marco Roos
• All the users inc. embedders

50
Web 2.0 Design Patterns

• The Long Tail
• Data is the Next Intel Inside
• Users Add Value
• Network Effects by Default
• Some Rights Reserved
• The Perpetual Beta
• Cooperate, Don't Control
• Software Above the Level of a Single Device

• http//www.oreillynet.com/pub/a/oreilly/tim/news/2
  005/09/30/what-is-web-20.html

51
1. The Long Tail

• Our target users are not just the specialist
  e-Scientists using computing resources to tackle
  major scientific breakthroughs, but also the
  large number of scientists conducting the routine
  processes of science on a daily basis.
• Through sharing we have the potential to enable
  smart scientists to be smarter and propagate
  their smartness, in turn enabling other
  scientists to become better and conduct better
  science.

52
2. Data is the Next Intel Inside

• myExperiment understands that scientists are
  focused on data, not software or one particular
  workflow engine.
• Workflows are components of customised
  applications, many of which are data-oriented
  rather than process-oriented.
• Users manipulate, through their own applications,
  the product (data, model) yielded by the
  workflow.
• Furthermore, workflows themselves are the data of
  myExperiment and provide its unique value.

53
3. Users Add Value

• myExperiment makes it easy to find workflows and
  is designed to make it useful and straightforward
  to share workflows and add workflows to the pool.
  
• To succeed we draw on the insights into the
  incentive models of scientists gained through
  experience with Taverna.

54
4. Network Effects by Default

• myExperiment aggregates user data as a
  side-effect of using the VRE.
• The ability to execute workflows from
  myExperiment, and the integration of tools such
  as Taverna with myExperiment, further enable us
  to achieve increased value through usage.

55
5. Some Rights Reserved

• myExperiment users require protection as well as
  sharing, but the environment is designed for
  maximum ease of sharing to achieve collective
  benefits workflows are "hackable" and
  "remixable".
• Initiatives such as Science Commons provide a
  useful context for this.

56
6. The Perpetual Beta

• myExperiment is an online service (a collection
  of online services) and is continually evolving
  in response to its users.
• To support this, the project commenced with
  developers being embedded in the user community.
• Through day-to-day contact between designers and
  researchers, design is both inspired and
  validated.

57
7. Cooperate, Don't Control

• myExperiment is a network of cooperating data
  services with simple interfaces which make it
  easy to work with content.
• It both provides services and reuses the service
  of others.
• It aims to support lightweight programming models
  so that it can easily be part of loosely coupled
  systems.

58
8. Software Above the Level of a Single Device

• The current model of Taverna running on the
  scientists desktop PC or laptop is evolving into
  myExperiment being available through a variety of
  interfaces and supporting workflow execution.