Question/Suggestion about Milestone searches

Page 1 of 1 (5 items)
This post has 4 Replies | 2 Followers

Posts 13420
Mark Barnes | Forum Activity | Posted: Sun, Nov 22 2015 1:17 AM

I was looking at possibility that John 19:30 included the idea of rest. I wanted to see what commentaries discussed this idea, so I used the following search:

(Sabbath, rest) WITHIN {Milestone <John 19:30>}

Unfortunately that returned several results where rest/Sabbath were discussed in John 19:31, but were returned because they were part of a larger milestone such as John 19:17-37.

I therefore tried to make my search more accurate by adding an equals as you can with standard searches for references, but it had no effect. Either I'm doing something wrong, or that feature isn't built yet.

Can anyone help?

Posts 25222
Forum MVP
Graham Criddle | Forum Activity | Replied: Sun, Nov 22 2015 1:38 AM

I see what you mean - my guess is it isn't built yet

Posts 816
LogosEmployee
Eli Evans (Faithlife) | Forum Activity | Replied: Mon, Nov 30 2015 12:30 PM

I think you should be able to use all of the same reference operators in the Milestone extension that you can in a standard search for references, so:

  • <Bible Jn 3:16> or <Bible ~ Jn 3:16> -- match this reference and references that contain it within the same chapter, so John 3:1-24 but not John 3-4.
  • <Bible = Jn 3:16> -- match only exactly John 3:16 and not John 3:1-24 or John 3.
  • <Bible intersect Jn 3:16-21> -- match any reference that intersects with verses 16-21, so John 3:1-24 or John 3-4 but not John 3:1-15.
  • <Bible superset Jn 3:16-21> -- match any reference that includes verses 16-21, so John 3 or John 3:1-24 but not John 3:17.
  • <Bible subset Jn 3:16-21> -- match any reference included within verse 16-21, so John 3:16 or John 3:16-21 but not John 3.

However, I confirm that it's not working like that currently. No matter what operator I use, I also get the same set of results. I'll file it as a case, and/or ping Bradley.

Posts 816
LogosEmployee
Eli Evans (Faithlife) | Forum Activity | Replied: Mon, Nov 30 2015 2:12 PM

Talked to Bradley. Operators weren't implemented for the {Milestone ...} extension, probably because of some amenities the search index has that the milestone index has heretofore never needed to have. So I added a case.

Posts 13420
Mark Barnes | Forum Activity | Replied: Mon, Nov 30 2015 2:16 PM

Thanks, Eli.

Page 1 of 1 (5 items) | RSS