Current Status and Future Prospects of Taverna Server and Client Libraries
This document outlines the current status and developments regarding Taverna Server, with recent download statistics revealing significant user engagement in both Ruby and Java client libraries. The Taverna Server is based on the preview release 2.2r1 and is undergoing testing for the next version, 2.3. Upcoming features include enhanced functionality, workflow management capabilities, and integration with cloud services. Additionally, funding considerations for long-term support and strategic alignments with external platforms such as Galaxy and SysMO are discussed.
Current Status and Future Prospects of Taverna Server and Client Libraries
E N D
Presentation Transcript
Taverna Server + Client Libraries Donal Fellows and Rob Haines
Current Status • Outputs • Taverna Server - 251 downloads (10% of WB) • Taverna Server Client Libraries • Ruby – 1450 (!) downloads • Java – Announced last week • Taverna Server VM – 340 downloads
Current status • Based on Taverna 2.2 • Server (preview release 2.2r1) • Ruby client library (0.6.0) • Java client library (0.0.3) • In testing phase for 2.2r2 • Security • Notifications • Client libraries
Server + Libs within App4Andy • Client library: • Upload workflow • Start workflow runs • Check status of runs • Retrieve results
Next steps • Move to 2.3 Taverna codebase • Test phase of 2.3r1 • Upgraded functionality • Imminent release of version 2.3 • Closing down issues • Writing documentation • Alignment of Client Libraries with latest Server
Funding • Server • Helio ~5-6 months • After which Helio moves into support mode • Can a case be made for the University to fund it centrally? • Client libraries • Methodbox (via NeISS integration) • SysMO (top sliced)
Alignment • Strategic • Taverna on the Cloud • Galaxy integration • e-Science Central integration • Dependencies • Taverna • Command-line Tool (now) • Platform (long term)
Alignment • Dependents • Helio • e-Galaxy • Next Gen. (app4andy, TSB) • NeISS • Methodbox • SysMO (future?) • Taverna as a service (in the Cloud) • Platform Cloud Executor (circular dependency!)