[TAVERNA-272] Provenance URIs for iterations not unique with multiple use of nested workflow

• Type: Bug
• Status: To Do
• Priority: Major
• Resolution: Unresolved
• Component/s: Taverna Engine
• Labels: janus nestedworkflows opm provenance uri
• Assignee: Unassigned
• Reporter: Stian Soiland-Reyes
• Created: 01/Jul/11 18:41
• Updated: 28/Apr/15 11:43

Description

Provenance export in OPM and Janus use an URI for the iteration process execution:

http://ns.taverna.org.uk/2011/run/6bf06207-8c57-46e8-88de-2492e3814ca4/workflow/e024ea01-89fd-4f93-b6ae-ad6da4a6df08/processor/P0/iteration/0

This does handle most cases - but if T2-1935 (OPM support for nested workflows) is implemented - there could be cases where the same workflow "e024ea01-89fd-4f93-b6ae-ad6da4a6df08" is included as two different processors - in which case the above URI would be ambigious.

As a nested workflow can also contain other nested workflows - using the processor name in the parent workflow is not enough - the complete path would be needed:

http://ns.taverna.org.uk/2011/run/6bf06207-8c57-46e8-88de-2492e3814ca4/workflow/e024ea01-89fd-4f93-b6ae-ad6da4a6df08/processor/P0/iteration/0-1/processor/P5/iteration/4/processor/P6/iteration/

Here:

• 6bf06207-8c57-46e8-88de-2492e3814ca4 is the run ID (global across nested workflows - but new per run)
• e024ea01-89fd-4f93-b6ae-ad6da4a6df08 is the master workflow (top level)
• P0 is a processor in e024ea01 which is a nested workflow
• 0-1 is the iteration [0,1] of P0
• P5 is a processor inside the P0 nested workflow (which ID is not shown here)
• 4 is the iteration of P5
• P6 is a processor inside the P5 nested workflow
• there were no implicit iterations over P6 - it's iteration []

This must obviously be shortened to be useful. The master workflow ID is probably not needed.. for instance:

http://ns.taverna.org.uk/2011/run/6bf06207-8c57-46e8-88de-2492e3814ca4/proc/P0/it/0-1/proc/P5/it/4/proc/P6/it/