How to improve "Jump To" fuzzy search results?

> Fuzzy search is a killer feature for a knowledge-base application like
> Zim. What can be done to improve results?

What would help is a "blueprint" with a number of examples and rationales
followed by a list of rules that the search should follow.

If the rules are specific enough it becomes rather easy for me to turn them
into code.

Please put such a proposal in a"blueprint" page in the wiki:
https://github.com/jaap-karssenberg/zim-wiki/wiki

Thanks,

jaap

On Tue, Aug 18, 2015 at 1:12 PM, Ipsod <<email address hidden>
> wrote:

> Question #270468 on Zim changed:
> https://answers.launchpad.net/zim/+question/270468
>
> Description changed to:
> I'm experiencing the following behaviors with the "Jump To" function.
>
> First, it seemingly sorts results by the same order they appear in the
> index. Some sort of intelligence would be nice. For example, if I've
> got a folder named "zebra", it should come first in search results for
> "zebra", far above something like "Tasks:Go shop for zebras".
> Similarly, but less importantly, "Tasks: zebra my room" should show
> before "Tasks: go shop for zebras", unless, maybe, "go shop for zebras"
> is a very commonly/recently viewed task.
>
> Second, the search results don't seem to take into account the directory
> structure, so, for example, searching for "contact John Bridges" brings
> up no results, even though "contact:John Bridges" exists. Likewise,
> trying to jump to "contact: bridges" brings up no results.
>
> Fuzzy search is a killer feature for a knowledge-base application like
> Zim. What can be done to improve results?
>
> --
> You received this question notification because you are an answer
> contact for Zim.
>

Ok, I will work on a blueprint. Thank you.