Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

Checked in 2.1 RC1

Taverna 1 name(s)

Taverna 2 name(s)

Suggestion

User opinion

Done

Available Processors (in service panel)

Available Activities (in activity palette)

Available Services

Available Services

Done

Local Services (in service panel)

N/A

Service Templates (1)

Service Templates

Done

Scavenger (in service panel)

Activities (in top-level menu)

Introduce Services (2)
Import new services

Add New Services(9)

Done

Scavenger (like WSDL scavenger)

??

Service provider

??

Done

Beanshell scripting host

Beanshell

Beanshell

Beanshell

Done

Local Java widgets

Localworker

Localworkers (3)

Local services

Done

Tools->Plugin Manager

Advanced->Software Updates

(4)

Updates and Plugins

Done

Workflow (as name for thing)

Dataflow

Workflow

Workflow

Done

Metadata

Contextual View (approximately)

X Details (5)

X Details

Done

Workflow inputs

Inputs

Workflow Inputs (6)

Workflow Input Ports

Done

Workflow outputs

Outputs

Workflow Outputs (6)

Workflow Output Ports

Done

Control link / coordinate

Condition / Coordination

Control link
Run after... (menu/details)

Coordination(12)

Done

Iteration Strategy

List Handling

List Handling

????(10)

Done

Processor (in workflow)

Processor (in workflow)

(7)

Service (11)

Done 

????

Activity (thing inside processor)

Service (8)

Service (11)

Done

Save diagram

Save diagram image

Save Diagram

Save Diagram

Done

????

Graphical Editor

Workflow Diagram

Workflow Diagram

Done

Import workflow

n/a

Merge workflow
Insert-->Workflow(in right-click when the user will have to choose nested or merge)
Import workflow (title of dialogue for choosing nested or merged workflow import)

 

Done

Annotations / Templates (RDF-like thing for Jun's thesis)

n/a

n/a


Done

Metadata (Title/description etc)

Annotations

Annotations

 

(1) It is not clear that there should be a single category that embraces Beanshell, local workers, RShell etc.  I'd go for "template services" or "service templates" that covers Beanshell etc., and "local workers" for local workers.

(2) Needs to be much less confusing.  At the moment T2 implies that you can add new activities to the workflow from this.  "Find" has implications that it can do a search.  "Import" or "Add" imply adding to the workflow.   The thesaurus has "introduce" so I suggest "Introduce Services" -> "Introduce new WSDL services" etc.

(3) It may be better to have something that indicates that it is a beanshell.

(4) No idea for the correct name.  Having it under Advanced does not seem reasonable.

(5) I've no idea why it is called contextual. I'm suggesting it go "workflow details", "service details", "input port details" etc.

(6) Maybe add "port".

(7) Katy wants "step"; KNIME use "node" (but more as service); Triana uses "task"; Kepler has "actor"; BPEL has "process"; in Pipeline Pilot the concept is not obvious.  Other possibilities are on the lines of "service player", "service enactor", "service runner".

(8) Needs to be something based on "service". Could be "service" or "service instance". I think just "service" is easiest. The distinction between a service definition and a service instance is probably meaningless for most users.

(9) This is to be moved into the Activity Palette replacement.  Its meaning there should be obvious.

(10) This has been re-opened.

(11) The users want service for processor, activity and service.  They select a service from the service palette, put the service in the workflow, connect up ports of the service, configure the service etc.  We should not make the 90%+ of cases difficult and confusing just so that it reflects the possible special cases.  Special cases should be shown up as such.

(12) Alex thinks this should be "control links" and "runs after".