Skip to end of metadata
Go to start of metadata
  • 1a - “Annotations about services can still only be seen in the BioCatalogue plugin and not on the services themselves. This information is most important when users are linking services together, so it should be visible when users try and do this”.** Is already in Taverna 2.4
  • 1b - “Annotations from the nested workflows are not propagating to the output workflows annotations”** This is a bug and will be fixed for Taverna 3
  • 1c - “Add more fields to annotations: to be able to specify not only authors names, but contributors as well”** This is being done as a continuation of the component work. It will go into Taverna 3.
  • 1d - “It would be nice to have people's myExperiment IDs automatically inserted in annotations”** This could be done for Taverna 3. It should not be automatic, but configured by a preference
  • 1e - “When users upload a workflow to myExperiment, they need to provide some information like the title and the description of the workflow. Usually, this information is in the details of the workflow, and users have to close the myExperiment panel to go to the design panel in order to copy this information and then paste in the myExperiment panel. It would be useful if this information were extracted from the details of the workflow”** This a bug and should be fixed in the myExperiment perspective of Taverna 3 beta
  • 2a - “When selecting an element in the workflow diagram pane, and choosing "Details" (so that the details pane appears for that element),  it is only possible to expand one "type" of thing at a time - i.e. "Description" OR "List Handling" OR "Predicted Behaviour" etc. But sometimes users want to look at several of these things at once, or even expand them ALL, it would be nice If user can open and see all submenu simultaneously”** This can be done for Taverna 3 beta by myGrid
  • 2b - “The description of the services in the “details” panel is not enough. Whenever users add a service to the workflow, they have to check the output of this service by running the whole workflow, in order to know what the output is”** We do not think this is a Taverna-related problem. The lack of useful annotations is a wider issue.
  • 3a - “Users build dialogs and GUI components in a separate JAR and deploy them in the Taverna Workbench”** Not sure what to do about this. It may be solved by the interaction service.
  • 3b - “It would be nice to be able to save users’ Beanshells to local services”** This requirement may be solved by use of components
  • 4a - “Beanshell idea is good, but when building slightly complex components, it is faster to separate them in a JAR (it also allows to build GUI)”** See 3a
  • 4b - “For now Python script is added from an external file”** A scripting service will be introduced for Taverna 3
  • 4c - “It is difficult to write the code in a small window, as a result code is implemented in another editor and then copy and paste to Tool in Taverna (also in Taverna there is no highlights when editing the code)”** We did not understand this issue
  • 5a - “Script output file: If users use a tool service template that receives a script as input and if the script implies the creation of some files, they are created in temp folders instead of the workflow folder”** We were not clear what is meant by “the workflow feature”. The separation of tool invocations is an essential requirement from (possibly other) users. To run multiple tool invocations in the same folder would cause unpredictable results. Taverna already allows the linking and copying of data between tool invocations on the same host.
  • 6a - “When there is a message “Workflow has warnings but still can be run” it is not clear what is the warning, more information would be helpful”** This could be fixed for Taverna 3 beta by myGrid
  • 6b - “It would be good to warn the user with an "alertbox" when datalinks are removed automatically”** This could be done for Taverna 3 but requires consultation with the users.
  • 7a - “The error report does not give sufficient information to figure out the problem”** Often Taverna does not “know” what the problem is. This may be improved by more constrained workflows realizing components.
  • 8a - “It would be nice when if one iteration fails to extract errors, but still allow w/f to run”** This has been examined before. It could be included in Taverna 3
  • 9a - “It would be nice to be able to set the default number of retries for all subservices”** This should probably be applicable to other changes. Multiple selection will go into Taverna 3 beta. Further work will be done for Taverna 3.
  • 12a - “In Taverna empty lists are created and passed to the nested workflows when single value can be passed instead”** We do not understand this comment
  • 12b - “When users have set iteration strategies or just link things together, the information about the depth of any lists created is available, but much hidden. It would be nice if you could see this on the diagram somehow”** This will be included in Taverna 3 beta
  • 12c - “Always get a list of list, but want single value (need to apply Flatten List to get single value)”** There are possible solutions to this, but they are difficult.** Could examine for Taverna 3
  • 13a - “To be able to save all the workflows up in the chain rather than saving each separately”** This will be done for Taverna 3 beta - Done
  • 13b - “To be able to expand the nested workflow from the context menu (sometimes you want to see nested workflow in context of the bigger workflow)”** You can already do this in Taverna 2.4
  • 13c -   “In the design pane, to look at the beanshell input ports, depths and script, users need to open the nested (or each of the nested nested nested) workflow(s), while in the Result Pane, it is possible to select, say, a Beanshell from within a nested (or nested nested nested) workflow, and look at its input and output result values. it does mean it can take quite a bit of dodging about to get to a particular beanshell description or service description to compare what its designed to do, with what result it gives”** This could be done for Taverna 3 beta
  • 13d - “When the workflow gets large it gets difficult to navigate and add components. The window is too small to get a good overview. Maybe workflows with X number of nested workflows or web services just become too complex and the user should be asked to consider stop adding components?”** Need to consult with users.** More intelligent zoom may help
  • 13e - “It would be nice to be able to copy easily a component from a nested workflow to the main workflow”** You can in Taverna 2.4
  • 13f - “It would be nice to be able to change the name of nested workflows in a bigger workflow, in a submenu”** Will be done for Taverna 3 beta
  • 13g - “When more nested workflows are added, it is becoming difficult to see thing on the screen, need to collapse ports”** Same underlying issue as 13d
  • 13h - “Encapsulate part of a workflow as nested workflow does not exist”** We do not understand this
  • 15a - “User has to delete parts of the workflow which he does not want to run now, it would be nice if user can “switch off” parts of the workflow”** This is not easy.** Some of this capability may come from the new capabilities of a component
  • 16a - “It would be convenient if we could copy and paste the entire w/f sections”** This will be included in Taverna 3 beta, leveraging multiple selection
  • 17a - “Output port names are too long by default”** This will be included in Taverna 3 beta, probably by using templates
  • 17b - “It would be nice if space is automatically replaced with underscore when naming ports”** This will be solved in Taverna 3 beta
  • 17c - “It would be nice to have guidelines on how to name the variables”** This requires consultation with the users. It may be done for the user manual of Taverna 3
  • 18a - “Sometimes it becomes difficult to see the workflows, when too many output ports are added”** It is not clear how this could be solved.** 13d may help
  • 18b - “If there is only 1 output port, you still have to change the view to see all ports before you can link things to it in the diagram”** This is not true
  • 18c - “We cannot inspect the output of the modules without having to add output ports to the workflow”** It is not clear how to solve this. Need to ask users, especially Katy.
  • 18d - “Additional output port needs to be created in order to see the result (and then deleted later)”** This is the same problem as 18c
  • 18e - “We cannot read anything, need to hide ports”** This may be helped by 13d
  • 18f - “I would like to have better export options for the output, and to be able to organize my output data in a more interactive and useful way”** This will be helped by better annotation and support for structured data. It will be done for Taverna 3.
  • 19a - “Output ports order is not convenient”** Need to consult users
  • 19b - “Alphabetical order of the output ports of Biomart is awkward”** See 19a
  • 20a - “To have button to delete provenance history together/using keyboard, not only within Taverna”** Not clear what is meant by “not only within Taverna”
  • 20b - “Deleting provenance history one by one is not convenient”** This can be done in Taverna 2.4
  • 21a - “It is nice in Taverna that we can go to each component and check the output”** Not clear why this is an issue
  • 21b - “When Results appear, “Values” are not active; user needs to click on “Value” it to be active at the beginning”** This has been attempted to be solved. It will be re-examined for Taverna 3 beta and solved for Taverna 3 - Done
  • 21c - “It is useful to check the results of previous runs of the workflow, but sometimes they are not stored. Maybe there is an option in Taverna to keep the results of the workflows, but it is not clear where this option is”** This could be done for Taverna 3 beta by myGrid. - Done
  • 22a - “If you import a service, and then later, its wsdls breaks or is unavailable, Taverna tries to import it on startup and complains slightly. If, after many times failing and you do not use that service anyway, you might want to remove it from the list. But how? It is not on the available services list, because it failed”** This is a bug. It is not clear when it will be solved
  • 22b - “Local services’ description is available only in user’s manual; it would be nice to have the description inside Taverna without going to User’s Manual web-page”** This could be solved for Taverna 3
  • 23a - “It would be more convenient if the string constant (default name) take the name of the service content”** This could be solved for Taverna 3
  • 23b - “When adding W/F input/output's names replace space with underscore”** This is the same as 17b
  • 23c - “Rename the services in the service list. At the moment users always see the URL to the service, but only a small part of the URL is significant in finding the service”** Unclear what to do about this.
  • 23d - “It is annoying that cannot use spaces in names”** This is the same as 17b
  • 24a - “Click on a particular parameter and add XML splitter rather than add XML splitter to the whole service”** This could be fixed for Taverna 3 beta by myGrid
  • 25a - “When there is a constant value in the workflow, it would be handy if the value itself were displayed somewhere, more easily accessible, on the diagram. e.g. on hover”** This could be fixed for Taverna 3 beta
  • 26a - “For scientists, non-technical users: easier environment only for running workflows”** This sounds like Taverna Player
  • 1a# - “The inputs window is not disappearing. It is unclear if that means the workflow is running or not (usually it disappears when things work good)”** This is a bug and needs to be investigated for Taverna 3
  • 1b - “If input is not specified w/f still runs but hangs later”** This is a bug. We are not sure how it could happen
  • 2a - “It would be nice to be able to change memory allocation to Taverna in TAVERNA itself, without editing Taverna shell script”** This is a difficult issue. It can be investigated for Taverna 3 beta by myGrid
  • 3a - “myExperiment is lovely and useful. Would benefit from being more easilysearchable - e.g. when you search for a workflow which you know the name of it does not always appear anywhere in the top of the list, even though you wrote title exactly”** This is a bug in myExperiment and has been fixed in the sandbox
  • 4a - “It would be great to have SAMP functionality (button in the result view) integrated in Taverna to send a table to TOPCAT/Aladin”** It is difficult to justify this as a general Taverna requirement.
  • 5a - “To remember certain variables in the entire Taverna session”** We assume this means global variables. Work has been done in this area. Needs user review and comment
  • 6a - “On the Updates and Plugins dialog, available from the Advanced menu, it is unclear what the Find Updates button does. Does it find updates for the selected plugin (this would seem most natural) or for all plugins in the list (this would seem most useful). If the latter is a case, then maybe the button should be renamed. If the former, then updating the plugins one-by-one would be tedious, so would be good to have a Find Updates to all plugins button”** The updates and plugin support is being updated in Taverna 3 beta - Done
  • 7a - “It would be nice to have user forum for all users to communicate”** We agree
  • 8a - “Because w/f has the long pathname, the name is not displayed. it would be handy to hover over the pathname and the name of the w/f would be displayed. At the moment there is no place where w/f name is displayed”** The w/f name is currently displayed in the Details tab.** A more user-friendly capability will be done for Taverna 3 beta - Done
Labels
  • None