-
-
Notifications
You must be signed in to change notification settings - Fork 347
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Master Search box #2736
Comments
=) or another way to settle this is supporting & and | relation: |
Should in your first proposal the "[x] by LGG" be a dropdown selection box? We can go with a normal search text box then, like now. The second one is too complex in my opinion. Users don't want to learn a complete search system just to search a mod in CKAN. Also I don't think an "Or |" relationship makes much sense here. |
it is usual search text box, the same as now, but searching all fields at once. Someone indeed may want to search mods by name and author, and I would prefer the name and the desc have one search box, so maybe something like this? filter by name: [--------------] [x] include by description filter by author: [-----------] |
Sorry, i was very unclear. I meant the last option "[x] by LGG", if this one is a dropdown selecion box. or a normal text box. |
it was a checkbox (and a joke) because LGG is the only modder, that have enough mods for inner search |
Okay, didn't get it...
I don't think there's workflow broken, and it would simplify the search. |
As a case study, GMail has a plain search box with a dropdown icon: If you click the dropdown, advanced options are revealed: That model could be nice for CKAN as well. I imagine the default "plain" search would search name, identifier, abstract, and description, and then in the dropdown we could have an author option and anything else that came up as desirable (host?). |
Continuing the case study, if I enter a bunch filters into that GMail popup/dropdown and click search, after it closes, the selections go into colon-prefixed strings in the main search box: We would need to do something like that as well, to give the user's search terms a persistent place to live. So we're effectively talking about creating a complete search syntax (which isn't too bad of an idea in itself). |
something like this for the Classic GUI: opened additional line: |
So if I try to search for mods for Linux, the list will be cluttered with all of linuxgurugamer's mods? This does not sound like an improvement. |
That's exactly how it already works. |
Big thumbs down on this. Users would not expect or like having to type "name:KER" to do a typical search. |
on v1.28.0 it is not. it's online sharing Main search field and detailed Name search field.
Typical search doesn't need any tags, and will have a little bit more results than before, and some of them could be desired. There is some chance, that the all-in-one search in the average will give much more results than I am expecting. Another option is adding new detailed search field with proposed results in the Gmail way. |
That's not correct. Try typing something in the other fields; it will show up in Search but not Name. |
@yalov, a suggestion: Focus on use cases rather than demanding specific features implemented in a specific way. What things would you like to do that you can't do today with the current UI? Then we can figure out 1.) whether those things are actually impossible, 2.) whether other users would benefit, and 3.) ways of addressing them that would actually work, rather than poking holes in a specific partial design suggestion. |
I want to write a word, and see all mods related to that word |
in addition to #2709 I propose to merge the search boxes to one, and to add checkboxes for backward ability to leave only one search type.
Search: [----------------] [x] by name [x] by author name [x] by description
The text was updated successfully, but these errors were encountered: