-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Unified search - search in current app by default #24056
Comments
I must say that I rarely (next to never) need or want "unified search". If I need to search for a contact, I go to the contacts app (and don't want to see files or events). If I search for an event in my calendar, I naturally open the calendar app and search for it (and don't want to see files, contacts, tasks or whatever). |
After all, the aim of the search feature is to give the user what they're searching for, as fast as possible. So, if the user already knows what they're searching for, it is unreasonable to ignore this fact. It may be a good option being able to broaden the search later, if the searched item is not found. But starting with the broadest search possible is mostly not helpful. |
cc @nextcloud/designers is this feasible and does it make sense? |
Actually, the the proposal was issued trying to make unified search usable again without dropping it rightaway, while I completely agree with @ruedigerkupper : I can't recall any incident that I ever wanted to use unified search in my life, neither on NC nor on Windows or MacOS. So I could live with dedicated search tools only quite fine as well. If they exist. |
See #23835 why I need to disable filesearch completely. I can't let this up to the user. |
Sounds like a good proposal to me 👍 |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
The file search still performs a full table scan, which isn't going to work on big databases. I can allow searches in the current directory only (which already may contain some thousand files/directories). |
22.1 doesn't multiply queries by shares any more, which is a good thing. Still, it's unified search, when only local search is needed. |
@jospoortvliet in my case i'm using the fulltextsearch app which provides a much quicker way to search for files and integrates in unified search, too. Of course you also need a lot more infrastructure but i think the admins who also installed this app would be happy to disable at least the files searchprovider. So if it's a desireable feature to disable/enable searchproviders globally i'd volunteer to create a pull requests for this 👍 |
Hey @juliushaertl and @ChristophWurst I'd like to tackle this. Could you please give me some code pointers where this needs to be implemented? Thanks! :) |
@szaimen take into account that possibly you'd better contact @Aeredren because he could be working on the same thing. For reference #29614 and https://help.nextcloud.com/t/looking-forward-to-develop-sorts-files-visualisation-improvement-and-filters/128314 . |
@Aeredren how far did you get with this until now? Is this issue (searchnng in the current app by default) something that you've already implemented in the planned enhancements? |
Hi @szaimen , I did not tackle the issue of "unified search" vs "search in current app", because I was focusing on search modal (filters) for files. (which does not use search provider but |
Thanks! Will see what I can do. |
@szaimen Is it up for grabs? |
yes it is. Feel free to work on it :) |
dropping this since it would be worked on here: #39162 |
The new unified search in NC 28 (see #39162) is a HUGE improvement! However, it still searches ALL apps by default as opposed to the current app. I agree that searching current app would still be the preferred option. The reddit example in the comment above is a good example, as is GitHub: For the new unified search, I think it would look something like what was originally posted by marcoambrosini here: #39162 (comment) |
There was a PR by @marcoambrosini which would be a big improvement IMO :) |
As covered in #23835, searching for files may take a very long time, making file search quite unusable. But it also has the side effect, that searching for something else will create collateral damage by overwhelming the database with unnecessary, very expensive queries, which stack up with every new keystroke. While the tests in #23835 where performed with my test user, who has 4 shares to a very big storage, other users have an average of 25 shares, with 55 shares max. If that user types 5 keys in the search box, he will trigger 4x55 queries running 1.2s each...
As a quick fix, I removed SearchProvider registration for the files app.
Each search provider should be configurable (at least enable/disable systemwide)
The text was updated successfully, but these errors were encountered: