Search Bug & Other Search Issues

Clark Bradley
Clark Bradley Member Posts: 30 ✭✭
edited November 20 in English Forum

I'm experiencing the following in a Bible search. My "Top Bibles" are ESV, NASB95 & NIV. My active resources is ESV. Indexing was complete (yesterday). I'm using Beta 5.

1) when my active resource is a Bible, and I click on Search, I expect the search dialog to default to Bible (like L3), but it doesn't.

2) I created a custom search range "Paul's Letters" = Romans-Philemon, and looked in "Top Bibles"

3) I entered the following search "prize and call" (w/o the quotes). I tried this search in both L3 & L4.  L3 was substantially faster. It returned Phil 3:14 (in all three Bibles). When I searched on the standard "New Testament" search range, the result was far worse. L4 took about 5x longer, and it consumed many more processor cycles than L3 (based on Task Manager).

4) BUG: L4 returned NO hits--not in any of the three Bibles.

 

Tagged:

Comments

  • Clark Bradley
    Clark Bradley Member Posts: 30 ✭✭

    Also, my custom range "Paul's Letters" doesn't give the books in the range (like all the standard search ranges do), i.e. Romans-Philemon

  • Rich DeRuiter
    Rich DeRuiter MVP Posts: 6,729

    I entered the following search "prize and call"

    In L4 search modifiers must be all upper case. In other words "prize AND call." (In my top Bibles I only get Phil 3:14.)

    BTW "prize AND call" is the same as entering "prize call" (prize [space] call).

    I don't know if it solves your custom search range, but give it a try and see what happens.

     Help links: WIKI;  Logos 6 FAQ. (Phil. 2:14, NIV)

  • Clark Bradley
    Clark Bradley Member Posts: 30 ✭✭
    https://community.logos.com/discussion/comment/17744#Comment_17744

    Thanks Richard, it works now.

  • Dave Hooton
    Dave Hooton MVP Posts: 35,674
    https://community.logos.com/discussion/comment/17730#Comment_17730

    Also, my custom range "Paul's Letters" doesn't give the books in the range (like all the standard search ranges do), i.e. Romans-Philemon

    I agree, it should show your custom range.

    Dave
    ===

    Windows 11 & Android 13

  • Dave Hooton
    Dave Hooton MVP Posts: 35,674

    When I searched on the standard "New Testament" search range, the result was far worse. L4 took about 5x longer, and it consumed many more processor cycles than L3 (based on Task Manager).

    Bible book ranges are inefficient to search compared to L3 but Logos say there will be an improvement in Beta 6.

    Dave
    ===

    Windows 11 & Android 13

  • Clark Bradley
    Clark Bradley Member Posts: 30 ✭✭
    https://community.logos.com/discussion/comment/17899#Comment_17899

    Bible book ranges are inefficient to search compared to L3 but Logos say there will be an improvement in Beta 6.

    I hope so. I was shocked by how much slower L4 was. I thought that the pain of waiting for indexing would pay off with searches.

Categories