Precise Books Search: Unexpected results (32.0 Beta 1 32.0.12, WIN 11)

I was expecting the Precise Books search to work exactly like the old Books search, but I am finding that it has some of the "Smart" AI function built into it.

Findings based on the search depicted in the image below (Search on the right, results on the left):

I was pleasantly surprised to see the "Summarize" option in the results of the Precise search.

I like this. Thank you.

The first result (from "John: Verse by Verse") did not find the exact text I was looking for ("Romans 3:24"). Instead it considered my text as a Bible reference and found "Rom 3:24" as an equivalent.

Maybe this is how it worked in previous versions, but I don't have an older version of Logos to check.
In any case, I think the search engine should distinguish between a Bible reference (without the quote marks, maybe with the prefix "Bible:") and a string text (within quote marks).

The second result (from "The Reformation Study Bible") was unexpected and curious. I was looking for the exact text "Romans 3:24" but instead it gave me a text string within an article that does not match the string text "Romans 3:24" nor refer to the Bible reference Romans 3:24.

Maybe the AI engine is smarter than I thought, and I just don't see the connection.

Find more posts tagged with

Comments

Graham Criddle

The first result (from "John: Verse by Verse") did not find the exact text I was looking for ("Romans 3:24"). Instead it considered my text as a Bible reference and found "Rom 3:24" as an equivalent.

Maybe this is how it worked in previous versions, but I don't have an older version of Logos to check.

I've just checked and it does work this way in Logos 31.1

The second result (from "The Reformation Study Bible") was unexpected and curious. I was looking for the exact text "Romans 3:24" but instead it gave me a text string within an article that does not match the string text "Romans 3:24" nor refer to the Bible reference Romans 3:24.

That is strange - and is not returned as a result in Logos 31.1

The article that is returned does contain a reference to Rom 3:22-24 which presumably is causing the search hit. But I don't believe it should.

Tim Hensler

https://community.logos.com/discussion/comment/1284649#Comment_1284649

The article that is returned does contain a reference to Rom 3:22-24 which presumably is causing the search hit. But I don't believe it should.

Looks like we got different results:

Your hit was in "The Reformation Study Bible: English Standard Version" (reference page 858) which I have in my library, but was not included in the results of my search. (LLS:ESVREFSTBBL; 2014-10-03T23:17:05Z; ESVREFSTBBL.logos4)
My hit was in "The Reformation Study Bible" (Reference John 3:16). (LLS:2.0.4; 2019-10-10T22:49:48Z; NGSTBIB.logos4)

See image below: I just noticed that hovering over the text that is highlighted as a result of my search presents a pop-up of the same article your search found in the RSB-ESV. Clicking on the highlighted text opens a bigger pop-up of the article which does not seem to be available as a separate article in the RSB (only the RSB-ESV).

The search apparently found the RSB article since the pop-up in that article has the reference I was looking for.

Now the question is, why did my search hit on the RSB and not the RSB-ESV (I have both resources in my library)?

Andrew Batishko

https://community.logos.com/discussion/comment/1284674#Comment_1284674

Now the question is, why did my search hit on the RSB and not the RSB-ESV (I have both resources in my library)?

In RSB, the link is a footnote whose content is part of the resource, and like all footnotes in resources, there isn't any other way to view that content. That's why the search hit shows up there. This is why clicking opens the text in a popup.

In RSB-ESV, the link is to another article in the resource, not a footnote. When you click it, it navigates to that article in the resource. Search hits show on the actual article in the resource, rather than in references to that article.

Dave Hooton

https://community.logos.com/discussion/comment/1284694#Comment_1284694

In RSB-ESV, the link is to another article in the resource, not a footnote. When you click it, it navigates to that article in the resource. Search hits show on the actual article in the resource, rather than in references to that article.

But the reference is IN Ps 136 rather than IN Jn 3:16 as required by the query!?

Andrew Batishko

https://community.logos.com/discussion/comment/1284709#Comment_1284709

In RSB, the Romans reference isn't in Ps 136. It's in a footnote that is in the John 3:16 article. It behaves like any other footnote containing a Bible reference.

In RSB:ESV, rather than a footnote, it's a link to another article in the resource. Therefore there is no hit, because the Romans 3:24 reference isn't in the John 3:16 milestone.

Dave Hooton

In any case, I think the search engine should distinguish between a Bible reference (without the quote marks, maybe with the prefix "Bible:") and a string text (within quote marks).

Unfortunately, a bible reference is parsed as a bible reference whether or not it is enclosed by quote marks. But I think there is a good case for quote marks forcing the reference to be parsed as text.

The second result (from "The Reformation Study Bible") was unexpected and curious. I was looking for the exact text "Romans 3:24" but instead it gave me a text string within an article that does not match the string text "Romans 3:24" nor refer to the Bible reference Romans 3:24.

As noted above, the highlighted text is a footnote that contains "Rom. 3:22-24". That result would be excluded by bible:="Romans 3:24" IN milestone:bible:="John 3:16".

Tim Hensler

https://community.logos.com/discussion/comment/1284711#Comment_1284711

Thank you, Dave and Andrew, for your explanations.

Dave Hooton

https://community.logos.com/discussion/comment/1284710#Comment_1284710

In RSB:ESV, rather than a footnote, it's a link to another article in the resource. Therefore there is no hit, because the Romans 3:24 reference isn't in the John 3:16 milestone.

I misunderstood your initial description, especially not having the resource.

Andrew Batishko

https://community.logos.com/discussion/comment/1284867#Comment_1284867

I misunderstood your initial description, especially not having the resource.

Sorry about that. I had some difficulty figuring out how to explain it.