When I select "article" on the locator bar in ESV and click the up/down arrows, I expect to jump from one pericope to the next. Instead, it jumps from one chapter to another (I can tell no difference in behavior from selecting chapter).
It's the way it's designed. "Article" is only really useful for non-Bibles, because in a Bible, each chapter is an article.
My question then, is why does it appear in the list in a Bible? I would love to see it replaced with "pericope" so that one could jump from pericope to pericope.
Another question related to this (in my situation), is: Is "heading text" or something similar not supposed to be available in the search fields? The only options available are "surface text," and "Words of Christ" (which appears even when limiting the search to an OT book).
More search fields are available when running a Basic Search
I think the difference may be due to different indexes used in the different searches but I am not sure - hopefully someone will be able to clarify.
Thanks Graham,
I knew I must be missing something totally obvious! [:$]
So this means that all these VERY USEFUL search fields are unavailable when one needs to search within a reference range?
A Bible Search only searches Bible text. There is no Bible text tagged with the "Heading" field, so it is automatically removed from the search UI (because it would always have zero results).
To search "Heading" text, you need to switch to a Basic Search.
There is no Bible text tagged with the "Heading" field
Makes perfect sense. Is there any possibility of adding reference ranges in Basic search whenever searching in a Bible?
No, because you can use the {Milestone} search modifier: love WITHIN {Milestone <Bible Jn 3>}
The reason they're available in Bible search is because the Bible search isn't designed to search Bibles, it's designed to search bible text. Heading text is not part of the Bible text, and therefore it's unavailable.
I know this is a bit late to reply to this again, but if this is really the way that it's supposed to work, then why is it present in any Bibles, seeing that the options are resource sensitive? My biggest punch against the "design" argument, however, is that the following bibles behave like one would expect, with "article" jumping from heading (pericope) to heading: NKJV, NET, NJB, CEV! I know I might be better off starting a new thread, but I hate multiple threads about the same issue! I'll start one though if I need to.
All Logos resources have "articles" (it's how the resource content is stored in the file). So you can't have a Bible without articles.
The choice of how articles is defined is up to the Content Production department. Standards have evolved over the years, so some Bibles were created with "article = chapter" and some with "article = pericope".
Unfortunately, we have to remain backwards compatible and can't change what an article means in an existing Bible, as that could cause your notes and highlights to be become misplaced.
We could hide the "next/prev Article" control in Bibles but I think some people find it useful.
I agree that some people would find it useful. Namely, those whose preferred Bible is NKJV, NET, NJB or CEV! [;)]
For everyone else, the "chapter" option functions identically AND is much more intuitive. My suggestion (request!) is to hide the "article" in Bibles and add a "pericope" option in those Bible which contain pericope headings. Is this reasonable, or am I off my rocker? [8-|]
BTW, an extension of the same argument would be to include a "heading" option in Journals and Monographs.
My suggestion (request!) is to hide the "article" in Bibles and add a "pericope" option in those Bible which contain pericope headings. Is this reasonable, or am I off my rocker?
It's a completely reasonable suggestion and makes perfect sense. If it were easy, we'd probably do it. [:)]
It's a completely reasonable suggestion and makes perfect sense. If it were easy, we'd probably do it.
Are you saying that Faithlife developers simply follow the path of least resistance?! [:P]
Is there any possibility of adding reference ranges in Basic search whenever searching in a Bible?
Yes: this was added in Logos 7.11.
