Skip to end of metadata
Go to start of metadata


 
Have templates and localworkers first. Then the other services preferably in some predictable order e.g. alphabetic. The ordering in subtrees should also be predictable.

1.

  • Says "Available Services" rather than "Available Processors" in 1.7.1 or "Available Activities" in 2.0 - may be altered depending upon naming decisions
  • Has number of leaf services in parentheses - forget this if it is too difficult
  • Right click will give the options for adding new services (identical to Add New Services button's functionality)
  • Need expand/collapse all

3.

  • Idea is to gather all template services under one heading - approved by users
  • This would include Beanshell, R, String Constant, Abstract Service (if this is there)
  • In 1.7.1 collected together with local workers under "Local Services"

Questions:

b) For coders: Is it possible from the API to find out what are "template" services?

4.

  • R-click will bring up:
    Add To Workflow (was "Add to model" in 1.7.1)
    Add To Workflow with Name (was "Add to model with name" in 1.7.1) - brings up Rename Processor (will be "Rename Service" I think) dialog
  • Drag and drop into graphical editor must still be available
  • Adding a service that requires configuration will automatically bring up the configuration panel
  • Left click causes descriptions to appear in the to-be-renamed contextual view
  • Includes Nested Workflow as a template

Questions:

c) For coders: How hard is "invoke"?

5.

  • Categorized into sub-trees according to category
  • Name is still being debated (11/02/2009) - users currently prefer "local services"

6.

  • "Biomart" rather than "Biomart service" for consistency
  • Need "remove from tree" on r-click

7.

  • Same as for (3) plus
  • Need remove from tree

8.

  • Porttype has gone

Questions:

d) For coders: What does porttype mean?  Users do not understand it.

9.

  • Users enter text.  As they do so, the tree is dynamically filtered, only showing leaf nodes that match and also only branches down to those nodes.  The match is done broadly i.e. search on any attribute, not just name.  If users delete text, then the tree shows the (probably) larger number of matches.  When no search text is left, or when the user presses reset, the tree reverts to showing its original content with the original (pre-search) node expansion settings.

10.

  • Add New Services has same kind of options as currently in 2.0 under Activities on the top
  • Also available by e-click on Available Services

11, 13.

  •  Icons same as currently.  Need new icon for search hits
Labels
  • None
  1. 2009-02-13

    Don't like Service Templates - but if thats what our users say then we should go with it.

    a) For coders: Can the Search Hits be deleted when reset/empty is done?

    Yes

    b) For coders: Is it possible from the API to find out what are "template" services?

    Not as it currently stands, but It could be a property added to the metadata (along with provider,type,style etc..) or a new API attribute - I prefer the former.

    c) For coders: How hard is "invoke"?

    This was acheived in T1 by wrapping up the service into a tiny workflow and running it. We could do this again, but we should look into invoking the Activity directly.Need to be careful of handling "dangling" data in the data manager that isn't associated with a workflow run.

    d) For coders: What does porttype mean?  Users do not understand it. 

    portType referred to the collection of operations defined in the WSDL. Its a web service term and we should probably get rid of it from the activity palette, sorry Service palette, but its useful to be able to get to the information in some other way. More important was the style, e.g. DOCUMENT or RPC. Once again doesn't need to be in the S.P but could be displayed along with the description and other metadata.

  2. 2009-02-13

    2. Reset button and r-click on Search Hits->Empty option should be named the same for consistency. 'Clear' seems a more standard option, but needs to be checked with users.

    2a) Question for coders: Can the Search Hits be deleted when reset/empty is done? YES. Search hits folder can remain but be emptied and say 'Search Hits (0)'. Or the whole folder can be removed. Not quite sure what users want.

    3. Should include nested workflow as well under 'Service templates'

    4. 'Left click causes descriptions to appear in the to-be-renamed contextual view' - this may clash with contextual view of an item selected in the graph as you can have both an activity in activity palette and a graph component selected at the same time. We'll have to separate these somehow.

    5c) Question for coders: porttype is a set of operations (methods) supported by a service endpoint.

    10. Should it be 'Add new services' or 'Add new service'?

    1. 2009-02-16

      (2) I agree about reset/empty/clear.

      (3) Yes I'd class it as a service template

      (4) That sounds nasty

      (10) Needs to new serviceS because you generally get more than one service added.

  3. 2009-02-13

    portType referred to the collection of operations defined in the WSDL. Its a web service term and we should probably get rid of it from the activity palette, sorry Service palette, but its useful to be able to get to the information in some other way. More important was the style, e.g. DOCUMENT or RPC. Once again doesn't need to be in the S.P but could be displayed along with the description and other metadata.

    In addition to this - we should have bright red flashing lights and alarm bells if anybody adds DOCUMENT/ENCODED or RPC/LITERAL - also UNWRAPPED/LITERAL but this is more difficult to determine.

    1. 2009-02-13

      I think it would be better for the WSDL Query (I think it is) to recognise that it has read a WSDL document describing operations that Taverna cannot do, and then to put up a Dialog.  i.e., the uncallable services should not make it into the service panel at all.

  4. 2009-02-16

    This sounds like a plausible first solution and should be possible to implement. We should easily be able to ignore one-branch-one-child folders as exposed in Taverna 1 (for instance the "WSDL port type").

    I don't like "Local workers" - "Local services" is a bit better - it implies that it happens on your machine, but it's still a service, not a "worker". I'm the worker.

    1. 2009-02-16

      The users wanted "local services" as well.