Bug: Fuzzy search ignores limits

Page 1 of 1 (7 items)
This post has 6 Replies | 1 Follower

Posts 1063
Martin Folley | Forum Activity | Posted: Sun, Nov 11 2018 9:13 PM

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?

2010 17" MBP with High Sierra, iPad4 with iOS10.

Posts 7895
LogosEmployee

Martin Folley:
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.

Posts 1063
Martin Folley | Forum Activity | Replied: Sun, Nov 11 2018 11:38 PM

Thanks Bradley.

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

2010 17" MBP with High Sierra, iPad4 with iOS10.

Posts 13063
Forum MVP
Mark Barnes | Forum Activity | Replied: Mon, Nov 12 2018 1:05 AM

Bradley Grainger (Faithlife):
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.

Posts 1063
Martin Folley | Forum Activity | Replied: Mon, Nov 12 2018 5:23 AM

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.

2010 17" MBP with High Sierra, iPad4 with iOS10.

Posts 2003
LogosEmployee

Mark Barnes:

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.

Martin Folley:
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).

Posts 18494
Rosie Perera | Forum Activity | Replied: Wed, Jan 9 2019 1:07 PM

Mark Barnes:

Bradley Grainger (Faithlife):
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.

Page 1 of 1 (7 items) | RSS