31–38 of 38 posts
Any comparison data with https://github.com/nextapps-de/flexsearch ? Also what player are using to play/pause gif in your readme?
I should probably post the code for my n-gram fuzzy search with an inverted index. Without tests, the entire code fits on a single screen (I love ClojureScript). It works on the backend (JVM) and the frontend (Javascript) and has been in production use for the last [checks notes] 8 years.
Please do, that would be awesome.
Earlier quoted context omitted.
It's subjective, I have to admit. I would say a search is accurate if most people find what they are looking for in their dataset in the first try. Distance definitions such as the Levenshtein and Damerau-Levenshtein distances provide a solid basis for discussions on accuracy. However, they are costly to compute and hence not widely adopted in fuzzy search libraries. I started by using the known filter equation for t…
> It's subjective, I have to admit. I would say a search is accurate if most people find what they are looking for in their dataset in the first try. I'd say a search is accurate if it finds what most closely matches the query, for some definition of "matches". A search is useful if most people can find what they are looking for on the first try. That is, a search being accurate doesn't necessarily translate to usefu…
So, in the end, I believe it's worthwhile to try different implementations and share our subjective experiences.
Earlier quoted context omitted.
> It's subjective, I have to admit. I would say a search is accurate if most people find what they are looking for in their dataset in the first try. I'd say a search is accurate if it finds what most closely matches the query, for some definition of "matches". A search is useful if most people can find what they are looking for on the first try. That is, a search being accurate doesn't necessarily translate to usefu…
Thank you for your explanation, I get your point. Regarding your last suggestion: I think it would be great to measure how often the correct result is near the top. However, don't we face the same issue as before? What is the correct result? Is it the term the user has in mind when writing the query? But what if they make a typo, and the term with the typo also exists in the dataset? Or they just type half of the ter…
oh very cool. would love to see the comparison/benchmark against the library I've used in projects for years (Fuse - https://github.com/krisk/Fuse ). Keep up the great work!
i will add it to the uFuzzy benchmarks :)