The Taverna team are pleased to announce that Taverna 2.3.0 Workbench and the Command Line Tool are now available for download.
Taverna 2.3.0 includes new service types, integration with service catalogues and experimental export of provenance information. Here are a few of the new features in the Workbench:
- REST service allowing you to perform GET, POST, PUT and DELETE operations configured using a template
- XPath service where you can create an XPath expression from an example XML document
- Tool service that allows you to run commands or scripts as part of your workflow
- Searching and browsing of service catalogues, such as the BioCatalogue, and addition of those services to your Workbench or workflow
- Experimental export of provenance in the OPM and Janus formats
- Help via the online User Manual
Taverna 2.3.0 also includes the Command Line Tool that allows you to execute workflows outside of the Workbench. The Command Line Tool is available either as a stand-alone download or bundled with the Workbench.
Tutorials and examples
Tutorials for Taverna are available under the Taverna 2.x documentation.
Example workflows can be found under the Starter pack tab in the myExperiment perspective of the Workbench. They can also be downloaded from the myExperiment Web site at http://www.myexperiment.org/packs/192.
Although Taverna 2.3.0 contains many improvements there are some known issues with it. These are detailed in known-issues.txt in the download bundle. An updated and more detailed list can be found in our issue tracker Jira at:
Details of Taverna’s system requirements are available on-line.
Licence and source code
Taverna is distributed under the LGPL 2.1 licence.
If you find any problems that are not listed in known-issues.txt, then please send them to the taverna-users or taverna-hackers mailing lists. Our support team is monitoring the mailing lists and will try to respond to questions as soon as possible.
If you prefer not to subscribe to our mailing lists, you can send your questions directly to email@example.com and a member of our support team will respond to your inquiries.