Bug 6.11 Beta 3 Bible Grid Search - Missing Person ?
Bit puzzled by some empty Grid boxes in Bible search for:
(<Person Jesus> OR <Person God>) WITHIN {Speaker <Person Jesus>}
Expectation is all Grid boxes filled in along with appropriate words highlighted. Noticed 60 verses have empty Grid box(es) across 30 Bibles:
Exported Missing Person passage list
FYI: 60 out of 1,044 verses means 5.75 % of verses has something to investigate.
Keep Smiling [:)]
Comments
-
-
I was puzzled by Lk 5:13, too.
English word order can mess up WITHIN searching (which is why it's best to search the Greek text and then show additional versions), but that doesn't seem to be the problem here.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
I poked around some but I don't know what the issue is, either. Translation word order can confound WITHIN, and markup boundaries can also, because WITHIN requires the left hand expression to be completely contained within the right hand expression. I'll see if Bradley has any insight.
0 -
The best way to diagnose WITHIN searches is to run each half separately and compare them. In this case (Lk 5:13, ESV), "saying I will" is not WITHIN "I will; be clean".
"a WITHIN b" currently requires "a" to be completely contained within b, which is not the case here. We have discussed adding an "INTERSECT" operator or similar in a future release, which could help solve this problem.
0 -
There's also the question of whether "saying" and "I will" should be two separate hits for <Person Jesus>. They are probably tagged as separate referent instances in the underlying DB (I haven't checked) but the <Person> search currently joins together all contiguous results into one hit. I think we have a case to see if this can be improved in the future, too.
0 -
Thanks Bradley
Very helpful, Graham
0 -
"a WITHIN b" currently requires "a" to be completely contained within b, which is not the case here. We have discussed adding an "INTERSECT" operator or similar in a future release, which could help solve this problem.
+1 [Y] for adding an "INTERSECT" operator (or similar: e.g. Match setting)
Thanks for explanation plus diagnostic steps.
Keep Smiling [:)]
0 -
-
By using the INTERSECTS operator?
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
By using the INTERSECTS operator?
Yes. The original issue reported in this case is not "fixed" and will still return the same results. In 7.1 you can use the new INTERSECTS operator to get the desired search results.
0 -
There's also the question of whether "saying" and "I will" should be two separate hits for <Person Jesus>. They are probably tagged as separate referent instances in the underlying DB (I haven't checked) but the <Person> search currently joins together all contiguous results into one hit. I think we have a case to see if this can be improved in the future, too.
This has now been fixed in 7.9 Beta 1 (7.9.0.0003).
0