Skip to end of metadata
Go to start of metadata

Note: I am not assuming that these capabilities should be done by r-click

Missing capabilities from looking at Taverna 1.7.1 AME, Taverna 2.0 Graphical Editor and user requests

I am not saying all these capabilities should go in.

Thanks to Alex for much of the source material.

The green items are already included in the WE.

 The Workflow Explorer must keep the expansion state when a new service or link etc. is added to the workflow.  It currently re-expands everything.

I have included the diagram killers here so that some consistency is maintained.

Workflow

  1. Offline capability - should this be somewhere - needed but not a killer (F & K), doesn't work properly in 1.7.1 as cannot be undone, very useful maybe not a killer (P)
  2. Add Nested Workflow - possibly beanshell etc. as well - nested workflow is a killer (F & K & P)
  3. Rename - sets the title of the workflow - can be done by annotation/configuration - is there a need for name and title for a workflow - Franck says needed but not killer, didn't know about it (P)
  4. Create New Input
  5. Create New Output
  6. Annotation/metadata via contextual view - save button, keep on chosen tab! (P)
  7. Collapse (expand?) all sub-items (P)

Killers: (2), (7)

Workflow inputs

  1. Create new input

 Individual workflow input port

  1. Rename - currently as edit
  2. Edit metadata - description and mimetypes - description is killer , mimetype is "a good thing" (F & K) ; need both (P)
  3. Incoming links - merge all data - don't care(F & K & P)
  4. Incoming links - select first link - don't care (F & K & P)
  5. Connection via dragging in T2 GE - need connection capability (not via dragging) via r-click
  6. Edit Output Port
  7. Delete Output Port

Killers: (2), (5)

Diagram killers: (2), (5) - via r-click

Workflow outputs

  1. Create new output

Individual workflow output port

  1. Rename - currently as edit
  2. Edit metadata - description and mimetypes - description is killer , mimetype is "a good thing" (F & K). need both (P)
  3. Connect to workflow outputs ... - killer (F & K & P)
  4. Connect to processors -> individual input - killer (F & K & P)
  5. Connection via dragging in T2 Graphical Editor (covered by 3 and 4)
  6. Edit Input Port
  7. Delete Input Port

Killers: (2), (3), (4)

Diagram killers: (2) , 3,4,5 via r-click

Processors

  1.  Remote Resource Usage - what services are called, where they are - killer
  2. Collapse (expand?) all activities - (P)

The real requirement is to be able to see the original name etc. for a service

 Killers: (2)

Processor/Service

  1. Metadata - killer (F & K & P)
  2. Retries, Delay, Back off, Thread, Critical - killer (K), care but not killer (F), never used (P)
  3. Configure (available for some in 1.7.1), need all in T2.1 - r-click configure is killer (F & K & P) - may be list of ways to configure e.g. list handling, annotation, beanshell-ness.
  4. Set as boring - don't care but like idea (K), not a killer and needs to be cleverer (F), never use (P)
  5. Add breakpoint - doesn't work anyway (K), never used (F & P)
  6. Edit templates (1.7.1 has a really weird general RDF annotation capability) - never used (F & K & P)
  7. Show/Hide ports (in T2 GE) - not needed (F & K), useful but not killer (P)
  8. Link from output... (in T2 GE) - killer but on input/output ports (F & K & P)
  9. Link to input... (in T2 GE) - killer but on input/output ports (F & K & P)
  10. Nested workflow show/hide contents in 1.7.1 and T2 GE - not a killer but current WE capability is not good enough (K), is OK (F) - Note needs edit workflow etc.; needs redoing to not show code guts, as T1, very important, maimer (P)
  11. Real name for a service (currently done by remote resource usage) - killer (F & P) (should be in contextual view)
  12. Coordinate from
  13. Delete Processor
  14. Contextual view including details, list handling, looping

Killers: (1), (2), (3), (11)

Diagram killers: (1), (2), (3), (11)

Service input port

  1. Set default value - should be able to quickly go for connecting a constant value - killer (F & K); useful not killer (P)
  2. Incoming links - merge all data - don't care (F & K & P)
  3. Incoming links - select first link - don't care (F & K & P)
  4. Set processor's List Handling - (in T2 GE but should probably be removed from GE)
  5. Connection via dragging in T2 GE - need connection capability (not via dragging)

Killers: (1), (5)

Diagram Killers: (1), (5) via r-click

Service output port

  1. Connect to workflow outputs ... - killer (F & K & P)
  2. Connect to processors -> individual input - killer (F & K & P)
  3. Contextual view - not clear what purpose it has - pointless (K), should be same as corresponding part of service's details (F), never used (P)

Killers: (1), (2)

Diagram Killers:  (1, 2) via r-click

Data links

The Workflow Explorer is currently inconsistent in the names it uses "Datalink" v "Link" v "Data link"
Individual Data link

  1. Remove data link - OK
  2. Contextual view - not clear what purpose it has - OK (K), Not clear what for (F), no point (P)

Control Links

  1. Totally missing - killer (F & K & P)

Killers: (1)

Individual Control Link / Coordination

  1. Remove from model - killer (F & K & P)

Killers: (1)

Merge (in T2 GE)

  1. Totally missing from Workflow - killer (K), needed but not a killer (F), never use (P)
  2. Remove Merge - killer (F & K), never use (P)
  3. Strange contextual view - needs order capabilities - killer (F & K), never use but need order (P)

Killers: (1), (2), (3)

Diagram Killers: (3)

Labels
  • None