Vscode-extension-for-zowe: Support Search/Filter on Data Sets without High Level Qualifier

Created on 12 Jun 2020  路  5Comments  路  Source: zowe/vscode-extension-for-zowe

Problem
Search/Filter requires a user know the high-level qualifier. This puts a burden on the user to know what data sets exist and where they are located.

Solution
Add support for search on data set name without the qualifier data.

enhancement

Most helpful comment

@jelaplan - a typical user will know what their HLQ is or the set of HLQ's they are going to work with. So for the majority of the use cases, its safe to assume the user knows the HLQ. The other part of the problem statement is about whether a dataset exists or not, so allowing the user go get a list of datasets for HLQ1.* or HLQ2.* (as filters) is fine in the explorer

The other related capabilities fall into the realm of "Search" which include scenarios like: I as a user know partial information about my data set, so I would like to do a search of HLQ..SOURCE (as an example), and then work on the results obtained from that search. Having capability like adding a search result to Favorites to persist that info would be a desirable capability.

All 5 comments

@jelaplan - This is a risky proposition. If no HLQ specified - then you are searching the whole catalog and that can be really time consuming and costly operation.

Isn't it safe to presume that a user would at least know the HLQ information to do the search?

I think at least one character is requiered at begining of High Level Qualifier: 芦聽A*.**聽禄 is allowed, but not 芦聽*A*.**聽禄.
On case of a global search with a 芦聽*聽禄 in first position of HLQ a confirmation should be requiered.

We should either prompt or introduce an easily configurable prefix. 馃憤

@venkatzhub There may be some way to help the user without searching across the whole catalog. The issue is one of recognition vs. recall. Dana has often pointed out how we've made the ZE too much like the CLI where we are prompting people for information rather than giving them choices. Is there a way to expose a list of HLQ?

@jelaplan - a typical user will know what their HLQ is or the set of HLQ's they are going to work with. So for the majority of the use cases, its safe to assume the user knows the HLQ. The other part of the problem statement is about whether a dataset exists or not, so allowing the user go get a list of datasets for HLQ1.* or HLQ2.* (as filters) is fine in the explorer

The other related capabilities fall into the realm of "Search" which include scenarios like: I as a user know partial information about my data set, so I would like to do a search of HLQ..SOURCE (as an example), and then work on the results obtained from that search. Having capability like adding a search result to Favorites to persist that info would be a desirable capability.

Was this page helpful?
0 / 5 - 0 ratings