Story #3016

[Workbench] Pipeline template can specify a search string to restrict choices shown in collection chooser dialog

Added by Tom Clegg almost 6 years ago. Updated almost 6 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Radhika Chippada
Category:
-
Target version:
Start date:
07/28/2014
Due date:
% Done:

100%

Estimated time:
(Total: 1.00 h)
Story points:
1.0

Subtasks

Task #3393: Update build a pipeline template documentationClosedRadhika Chippada

Task #3394: Pass the search string from template to the input chooser popupResolvedRadhika Chippada

Task #3424: Update the schema docResolvedRadhika Chippada

Task #3423: Review 3016-pipeline-template-search-stringResolvedTom Clegg

Associated revisions

Revision 033c9aee
Added by Radhika Chippada almost 6 years ago

refs #3016
Merge branch '3016-pipeline-template-search-string'

History

#1 Updated by Tom Clegg almost 6 years ago

  • Subject changed from Pipeline template can specify a list of filename extensions to restrict choices shown in collection chooser dialog to Pipeline template can specify a search string to restrict choices shown in collection chooser dialog
  • Story points changed from 2.0 to 1.0

#2 Updated by Brett Smith almost 6 years ago

  • Assigned To set to Brett Smith

#3 Updated by Tom Clegg almost 6 years ago

  • Target version changed from 2014-07-16 Sprint to 2014-08-06 Sprint

#4 Updated by Tom Clegg almost 6 years ago

  • Subject changed from Pipeline template can specify a search string to restrict choices shown in collection chooser dialog to [Workbench] Pipeline template can specify a search string to restrict choices shown in collection chooser dialog

#5 Updated by Brett Smith almost 6 years ago

I would like to understand better:

  • How does a specified limit restrict the Collections chosen? Does Workbench show every Collection with at least one matching file? Every Collection where all the files match? Every Collection that has exactly one file that matches?
  • Should the component be able to specify more than one limit? If so, do we AND or OR those limits?
  • What format(s) do we want to support for limits? Simple strings, shell globs, regular expressions, something else?

#6 Updated by Tom Clegg almost 6 years ago

This story is just a channel between the pipeline author and the search box in the collection chooser: the desired search behavior is "whatever the collection chooser would do if you typed that string in the search box yourself".

Making better search operators is a worthwhile but separate story. As the search box becomes more capable, that benefit will automatically extend to this scenario. But we can play with it on the Workbench side. I don't want to overthink this before we have some more real-life examples. (Then I'll want to overthink it.)

#7 Updated by Radhika Chippada almost 6 years ago

  • Status changed from New to In Progress
  • Assigned To changed from Brett Smith to Radhika Chippada

#8 Updated by Tom Clegg almost 6 years ago

At c28309c, LGTM.

#9 Updated by Radhika Chippada almost 6 years ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF