BUG: Milestone Search - Why does searching in Rev 12:1-18 vs. Rev 12 give different results?

I'm trying to understand milestone searching. If Revelation 12 has 18 verses (in the NRSV and some other bibles; 17 in others), why would the following searches give me different results?

(Leviathan OR Rahab) IN milestone:bible:"Revelation 12:1–18": gives 59 results in 31 articles in 20 resources

(Leviathan OR Rahab) IN milestone:bible:"Revelation 12": gives 63 results in 33 articles in 21 resources

The additional resource was the Interpretation commentary on Revelation. The milestone for the search result in this commentary is Revelation 12:1–13:18. Of course this includes Rev 12:1-18, so why doesn't the first search include this resource? How is it that the second search is able to include it? Is this a bug or deliberate design? How can I best do milestone searches to make sure I get the most accurate results? Why is milestone searching so fickle?

Find more posts tagged with

Desktop App

Comments

Beloved Amodeo

The results are unexpectedly at variance I would account this as a bug for the first search range.

Edit:Although I have no explanation for this behavior, it may be by design; as I tested it with another search and divergence of results persists.

Kiyah

https://community.logos.com/discussion/comment/1252893#Comment_1252893

I updated the thread title.

MJ. Smith

https://community.logos.com/discussion/comment/1252898#Comment_1252898

From the wiki:

[quote]

There are many other datatypes and you can find how to search for them in the same way. But there is a general format that applies to all datatypes and their values i.e. datatype:[Op]value where Op can be:

= —> exact match e.g. bible:=”Jn 3:16” will only find Jn 3:16
<< —> result wholly included in value, or value with any dependents e.g. Jn 3:16 with Jn 3:16b
>> —> result includes the whole value, or value with any ancestors e.g. Jn 3:16 with Jn 2:23-3:31, 3:16-17
~ —> broad intersection, or value with all its dependents and ancestors i.e. << with >>
—> narrow intersection when no Op is specified e.g. Jn 3:16 with Jn 3:16b, 3:16-17
- it finds any bible reference within a range of verses in the same chapter.
- same as << with other datatypes.

Note that value requires quotes if it contains spaces.

It appears that one invokes the narrow intersection when one would expect them both to. I'd play with the operator to figure out what the defaults actually are. I'd also explore the span of book searches to see if it plays into the difference. Fortunately, I can count on Dave to have done the exploration for me.

Dave Hooton

The additional resource was the Interpretation commentary on Revelation. The milestone for the search result in this commentary is Revelation 12:1–13:18.

The Rev 12:1-18 search will only look at verses belonging to chapter 12. So it will ignore milestones covering a range of chapters, including chapter 12 with no verses! The Rev 12 search will look for any milestones that contain that chapter.

You will notice an even greater discrepancy if you search for (Leviathan OR dragon) .

Kiyah

https://community.logos.com/discussion/comment/1252903#Comment_1252903

The Rev 12:1-18 search will only look at verses belonging to chapter 12. So it will ignore milestones covering a range of chapters, including chapter 12 with no verses! The Rev 12 search will look for any milestones that contain that chapter.

So to get the most inclusive results I should search chapters and not verse ranges?

I think it would be better if milestone searches could find verses/verse ranges regardless of how the milestone is styled in the commentary. That would be more intuitive to the user.

Dave Hooton

https://community.logos.com/discussion/comment/1252907#Comment_1252907

So to get the most inclusive results I should search chapters and not verse ranges?

Yes.

I think it would be better if milestone searches could find verses/verse ranges regardless of how the milestone is styled in the commentary.

You would only specify a verse range if that was your intention. So would you really expect a result for Rev 12:3 from a commentary that does not specify verse milestones in chapter 12? Admittedly, you might well specify bible:="Rev 12:3" for an exact match, otherwise your result will come from any range that includes that verse.

So, if you want a result from anywhere in a chapter then specify a chapter milestone (and avoid the trap of 17 verses vs. 18 verses in different translations).