Community
Participate
Working Groups
In the solution of bug 367883, we are throwing the "search not supported" message. We should support a pure client side search for that. I would like to call it advanced search. The advanced search will not only support file system like webDav but also orion project. The advanced search will start from a new page, where you can put in-the-page options like modified date range, etc. Once you start search, the search result will be rendered gradually and you can stop it at any time. There are some optional work flows to trigger the advanced page. 1. If you are searching on a file system that does not support search, it will transfer you to the advanced search page. 2. If you type nothing in the search box and hit enter, it will transfer to the advanced search. 3. We can think about a pop up menu while user is typing, something like "go to advanced search". 4. We can also think about adding the "advanced search" button on the right to the search box. There may be more UI potentials to trigger it but the target is to bring up a new page where you can put advanced options like modified date range ,etc. Once you start search, the search result will be rendered gradually and you can stop it at any time. I am not sure how "slow" this "client side search" will perform but I would like open discussions on it.
I understand the goal of a client side search for WebDAV, etc, but I would be curious to know if we have good reason to do it for our Orion file server. Lucene supports date ranges and many other kinds of queries that we currently don't expose on the client (fuzzy searches, auto-correcting typos in search terms, file size, etc).
(In reply to comment #1) > I understand the goal of a client side search for WebDAV, etc, but I would be > curious to know if we have good reason to do it for our Orion file server. > Lucene supports date ranges and many other kinds of queries that we currently > don't expose on the client (fuzzy searches, auto-correcting typos in search > terms, file size, etc). The start point from the UI perspective was to provide a new page for advanced search. Once you are in the page, you can input your options there and hit "search" in the page. For orion files, to correct what I've said before, we don't have to do client side search. We are just exposing the Lucene options and pass the query to it. But I have another question here: Lets say webDav plugin wants to implement search. Then we will assume it will support advanced search. We have to define the contract for both query rule and response json format. How are we going to define these contract?
We have search completion now. In 2.0M1 we can think about putting options in the completion UI.
Advanced search is already supported.
