Bug: Fuzzy search ignores limits

It may always have been thus ... I have not used fuzzy search much before ... but it certainly looks wrong to me!

To be honest, the hits that it has found seem to reflect the order of the words in the paraphrase rather than reflecting a closest match.

Am I missing something?

Find more posts tagged with

Comments

Bradley Grainger (Logos)

It may always have been thus ...

This is a known issue in Fuzzy Bible Search; see https://community.logos.com/forums/p/148370/922009.aspx#922009 for a previous discussion.

Martin Folley

https://community.logos.com/discussion/comment/1012264#Comment_1012264

Thanks Bradley.

I notice that Andrew created a case over a year ago now ... any news on this?

Mark Barnes

https://community.logos.com/discussion/comment/1012264#Comment_1012264

This is a known issue in Fuzzy Bible Search

I've always assumed that was a feature, not a bug. After all, if I was sure where the verse was, I wouldn't be using fuzzy search.

Martin Folley

https://community.logos.com/discussion/comment/1012288#Comment_1012288

I wondered that ... both then the ranking of the hits seems to be a little awry ... I would expect that hits within a range would be prioritised over hits outside of the range, which might come under 'more ...' unless there are no hits whatsoever. Added to the words that are highlighted yellow in the screen shots ... it does not appear to be optimised.

Andrew Batishko

https://community.logos.com/discussion/comment/1012329#Comment_1012329

I've always assumed that was a feature, not a bug.

It was certainly intentionally implemented the way it is. That's not to say we didn't recognize at the time that it would be ideal to filter the range. There just have been other priorities.

the ranking of the hits seems to be a little awry ... I would expect that hits within a range would be prioritised over hits outside of the range, which might come under 'more ...' unless there are no hits whatsoever. Added to the words that are highlighted yellow in the screen shots ... it does not appear to be optimised.

Given that we ignore the selected range, I wouldn't expect it to prioritize hits within that range.

You should completely ignore the highlighting when it comes to prioritization of the results. The results are shown in the text of your preferred Bible, and the hits are merely places where the text directly matches your search string. This may have little to nothing to do with why the hit was highly ranked. For comparison, you can change your preferred Bible to something significantly different (such as The Message) and still see the same order of results.

The order of results is based on the strength of matches across all of the Bibles in our system, plus a number of additional data sources (such as referent data).

Rosie Perera

https://community.logos.com/discussion/comment/1012288#Comment_1012288

This is a known issue in Fuzzy Bible Search

I've always assumed that was a feature, not a bug. After all, if I was sure where the verse was, I wouldn't be using fuzzy search.

If I didn't know where the verse was, I wouldn't have intentionally limited the search to only New Testament. If it's a very common word or combination of words, it would be in my interest to limit the search range as best I could to the best of my memory of where the verse I'm looking for is.