NBIC myExperiment wish wiki

From BioAssist
Jump to: navigation, search

NBIC wish-list for myExperiment and BioCatalogue

Dave De Roure, Director of myExperiment wrote:

We regularly have meetings for identifying, prioritising and planning our myExperiment developments. We have input from a number of sources, but one of the most important ones is... you :-)
Please let us know what you would like to see myExperiment doing. If you’re not sure you’re up to date on where we are with things just now, take a look at http://wiki.myexperiment.org – for example, you’ll see we’re building up our developer activity.
Please share your thoughts – whether about the web site, the software, the API, whatever – no ideas are too big or small!

Our BioAssist wishes

Please add your wish here on separate lines. Please indicate how important you consider your wish between 1: nice to have, and 5: (close to) essential. Do not worry whether your idea is mature enough, is exactly a myExperiment wish, or if the wording is understandable for software developers. The development team has friends to sort that out. Please add four tildes to indicate your name and the date.

myExperiment wishes

  • Web services registry [rate: 5] => BioCatalogue (Mroos 11:18, 27 August 2008 (CEST))
  • Ability to switch between collapsed and expanded view of a workflow, and default set by workflow owner [rate: 4] (Mroos 11:18, 27 August 2008 (CEST))
  • Ability to be notified as owner of a workflow who is using it; possibility to set a gradient of notification requirements under the sharing tab (from 'anonymous use (do not notify me)' to 'identification and approval required'). [rate: 4] (Mroos 11:18, 27 August 2008 (CEST))

BioCatalogue wishes

  • Ways to make users of web services aware of version changes of the service [rate: 4] (Mroos 11:18, 27 August 2008 (CEST))
  • Ways to make users of web services aware of the stability of the services [rate: 4] (Marcvandriel 11:22, 27 August 2008 (CEST))
  • I would like to see the item above implemented as:
    • 1. Remote unit tests. Think of web services as remote modules!
    • 2. Uptime stats.
    • 3. Citation/usage stats. The more people use or cite a service, usually means the better.
  • For 1 and 2 BioCatalogue could use something like a web crawler that checks the catalogue for known example inputs + example outputs and checks whether the service still works as advertised in the catalogue. Such functionality has been discussed before for the BioMoby services. We already have a crawler a.k.a. RDF Agent for BioMoby that uses a BioMoby ping to check if a service is still alive, but it doesn't use an example to check if the service works as advertised. Hence mis-registration of BioMoby services is still a problem... [rate: 5] (Pneerincx 17:16, 27 August 2008 (CEST))

Uncategorized wishes

  • Ability to run a workflow (seemingly) without Taverna [rate: 4] (Mroos 11:18, 27 August 2008 (CEST))