Provenance in Taverna

Taverna assigns an LSID to each workflow instance (ie run/enactment) and to each data item in an instance.

During the enactment of a workflow, Taverna also emits WorkflowInstanceEvents which can be listened to by registered WorkflowEventListeners. These events provide rich provenance information, which, if recorded, allows one to reconstruct the entire enactment. The TavernaProvenancePlugin does exactly that, translating the events into RDF triples typed by a suitable OWL Provenance Ontology and then storing them in an RDF triple store.

Starting from version 0.9.1 of the Provenance plugin, the data is also stored by the same listener: this allows the LSIDs of data items to be resolved against the actual data. (Prior to version 0.9.1 one could use Taverna's BaclavaDataStore to persist data).

A further Taverna plugin, the ProvenanceBrowser, is available which allows one to browse both data and metadata recorded by the TavernaProvenancePlugin within the Taverna GUI.

Metadata and Data

• TavernaProvenancePlugin
• Recording implemented as a Taverna WorkflowEventListener

Browsing

• ProvenanceBrowser
• Plugin reusing Taverna GUI components

Security

• Work in progress

Ideas

• Smart reruns
• MyExperiment
• Local provenance and then publish selected provenance in MyExperiment

See Also

• Requirements: StefAssess
• ProvenanceResources
• Power Point Presentation