Bugs: Searches affceted by footnotes or non-Surface text

Dave Hooton
Dave Hooton MVP Posts: 35,761
edited November 21 in English Forum

1. Phrases affected by footnotes

Do a Books Search of Emphasized Bible for:

  • "famine in"  -->   6 results in 5 articles
  • famine THEN in  --> 6 results in 5 articles
  • famine BEFORE 1-1 WORDS  in  --->  26 results in 11 articles  (13 results if normalized as per the above operators).

The extra results for BEFORE come from  phrases like "famine､ in" or "famine|| in" where the special character is a footnote. I would also expect the Phrase search to ignore footnotes (and punctuation) and it is unexpected that THEN has the same behaviour when it is defined as BEFORE 1-1 WORDS. A search of Surface Text is a clue as it provides the expected results for the Phrase and THEN and does not affect BEFORE.

Similar behaviour can be found with  "famine in" AND land  and term:("famine in" AND land), where TERM coding provides the missing results.

.

2. Term results count affected by non-surface text :

A Books Search for he-ass OR "he ass"  produces 300 results whilst the individual words produce 150 results.

But term:(he-ass OR "he ass") produces 247 results instead of the expected 150.

This seems to be caused by:

  • BHS SESB2 (LLS:1.0.204) which has 96 results in Gloss Text, and
  • "Commentary on the Old Testament" (LLS:29.2.11) which has 1 result in Footnote Text.

The combined footnote contribution is 97 and this is added to the term count instead of being normalized i.e. 150+97 = 247.

This also affects Logos 9  with ("he ass", he-ass)

Results in Surface Text behave as expected.



Dave
===

Windows 11 & Android 13

Tagged:

Comments

  • Bradley Grainger (Logos)
    Bradley Grainger (Logos) Administrator, Logos Employee Posts: 11,969

    Dave Hooton said:

    Phrases affected by footnotes

    This is a known bug (that's also present in L9).

    (Technical details: it's a bug only in the native search engine, not the original search engine. If you use a query that can't be processed by the native search engine (so that the original search engine is used), you get the results you're looking for. One way is to use L9's comma operator, or the equivalent L10 syntax: term:("famine in" OR "famine in") .)

  • Dave Hooton
    Dave Hooton MVP Posts: 35,761
    https://community.logos.com/discussion/comment/1229848#Comment_1229848

    Bradley Grainger (Faithlife) said:

    This is a known bug (that's also present in L9).

    I know. It is very old.

    Bradley Grainger (Faithlife) said:

    (Technical details: it's a bug only in the native search engine, not the original search engine. If you use a query that can't be processed by the native search engine (so that the original search engine is used), you get the results you're looking for. One way is to use L9's comma operator, or the equivalent L10 syntax: term:("famine in" OR "famine in") .)

    This is unacceptable for a new Search as new operators like THEN should function as described in all scenarios. It is time for the footnote bugs** to be fixed rather then expect, or warn, users that they should use verbose workarounds or accept incomplete results.

    ** I include the word IN bible:ref bug (implicit milestone).

    Dave
    ===

    Windows 11 & Android 13

  • Rodney Clark (Faithlife)
    Rodney Clark (Faithlife) Member, Logos Employee Posts: 28
    https://community.logos.com/discussion/comment/1230131#Comment_1230131

    Dave, 

    We have resolved this bug and completed internal testing. The fix will be made available on Logos version 23.0.131. Please let us know of any other questions. 

  • Dave Hooton
    Dave Hooton MVP Posts: 35,761
    https://community.logos.com/discussion/comment/1242077#Comment_1242077

    Rodney Clark (Faithlife) said:

    We have resolved this bug and completed internal testing. The fix will be made available on Logos version 23.0.131

    Thank you. I'm looking forward to that beta release.

    Dave
    ===

    Windows 11 & Android 13

  • Dave Hooton
    Dave Hooton MVP Posts: 35,761
    https://community.logos.com/discussion/comment/1242077#Comment_1242077

    Rodney Clark (Faithlife) said:

    Dave, 

    We have resolved this bug and completed internal testing. The fix will be made available on Logos version 23.0.131. Please let us know of any other questions. 

    Thank you. The 1. Phrases affected by footnotes bug is fixed in v23 Beta 3.

    The second bug is still unresolved i.e.

    Dave Hooton said:

    2. Term results count affected by non-surface text :

    A Books Search for he-ass OR "he ass"  produces 300 results whilst the individual words produce 150 results.

    But term:(he-ass OR "he ass") produces 247 results instead of the expected 150.

    This seems to be caused by:

    • BHS SESB2 (LLS:1.0.204) which has 96 results in Gloss Text, and
    • "Commentary on the Old Testament" (LLS:29.2.11) which has 1 result in Footnote Text.

    The above two resources have 97 results for "he ass"  but term:(he-ass OR "he ass") has 194 results instead of being normalized as 97.

    Dave
    ===

    Windows 11 & Android 13

  • Dave Hooton
    Dave Hooton MVP Posts: 35,761
    https://community.logos.com/discussion/comment/1245821#Comment_1245821

    Dave Hooton said:

    The second bug is still unresolved i.e.

    Dave Hooton said:

    2. Term results count affected by non-surface text :

    term:(he-ass OR "he ass")

    • BHS SESB2 (LLS:1.0.204) still has 192 results in Gloss Text instead of 96
    • "Commentary on the Old Testament" (LLS:29.2.11) still has 2 results in Footnote Text instead of 1.

    Dave
    ===

    Windows 11 & Android 13

  • Dave Hooton
    Dave Hooton MVP Posts: 35,761
    https://community.logos.com/discussion/comment/1265986#Comment_1265986

    Bump for FL response

    Dave
    ===

    Windows 11 & Android 13

Categories