Project

General

Profile

Actions

Story #9044

open

[Crunch2] [Workbench] Browse and show tools using the GA4GH tool registry API

Added by Brett Smith almost 7 years ago. Updated 17 days ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
Workbench2
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
-

Description

This first version will just allow users to browse/select public workflows that have been registered at dockstore.org.

The API endpoint should be configurable, though, so that when Arvados supports the tool registry API itself (#9042) users will be able to select tools that are registered in Arvados.


Related issues

Related to Arvados - Story #9043: [Crunch2] [Workbench] Render CWL input selection formsResolvedPeter Amstutz07/26/2016

Actions
Actions #1

Updated by Tom Clegg over 6 years ago

  • Description updated (diff)
  • Category set to Workbench
Actions #2

Updated by Tom Clegg over 6 years ago

  • Description updated (diff)
Actions #3

Updated by Brett Smith over 6 years ago

  • Target version set to 2016-07-20 sprint
Actions #4

Updated by Brett Smith over 6 years ago

  • Target version deleted (2016-07-20 sprint)
Actions #5

Updated by Brett Smith over 6 years ago

  • Assigned To set to Radhika Chippada

Radhika's for grooming.

Actions #6

Updated by Brett Smith over 6 years ago

  • Subject changed from [Crunch2] [Workbench] Browse and show tools using the tool registry API to [Crunch2] [Workbench] Browse and show tools using the GA4GH tool registry API
Actions #7

Updated by Tom Morris over 6 years ago

  • Target version set to Arvados Future Sprints
Actions #9

Updated by Radhika Chippada over 6 years ago

Implementation:

  • Add a “Run a tool” button in the panel header next to “Run a pipeline” in dashboard.
  • Add a config parameter to workbench to configure the tool registry end-point
  • When this button is pressed, present a “Choose a tool to run” modal similar to “Choose a pipeline to run” to the user
    • Get the tool json from the configured end point (do we want to cache this and pull at regular intervals or for each click?)
    • Present each version of each tool from the json as a separate link in the popup
      pcawg-merge-annotate - master
      pcawg-merge-annotate - 1.0.0
      …
      
    • When a link from the popup is clicked on, show the tool detail in preview pane on the right
    • When OK button is selected, create a CR with the selection as mount(s) and take the user to the CR page
    • The CR created for the selected tool version will have:
      • Name = tool - version (ex: pcawg-merge-annotate - master)
      • use mount kind json to store the selection
      • store the entire selected tool record including all version as mount point “/var/lib/cwl/tool”
      • store the selected tool version as mount “/var/lib/cwl/tool_version”

Out of scope for this story:

  • Support for json mount kind
  • Presenting appropriate input selection options based on the selected tool description
  • Running the selected tool
Actions #10

Updated by Tom Morris over 6 years ago

  • Target version deleted (Arvados Future Sprints)
Actions #11

Updated by Tom Morris almost 5 years ago

  • Release deleted (11)
Actions #12

Updated by Peter Amstutz 17 days ago

  • Target version set to To be groomed
  • Assigned To deleted (Radhika Chippada)
  • Category changed from Workbench to Workbench2
Actions

Also available in: Atom PDF