Add multiple search scopes for Bible search
Phil Gons (Logos)
Administrator, Logos Employee Posts: 3,799 
Please add a new option to set the search scope/document that multi-term queries need to be contained in to count as a result.
Currently, multi-term queries need to match in a single verse when running a Bible search. If you search a Bible using Basic search, your terms need to occur in the chapter.
It would be great to have multiple options in Bible (and inline) search to allow the user to specify in which unit of texts their terms need to occur.
Add reference based units (verse, chapter, book) and structural units (phrase, clause, sentence, paragraph, pericope).
Currently, multi-term queries need to match in a single verse when running a Bible search. If you search a Bible using Basic search, your terms need to occur in the chapter.
It would be great to have multiple options in Bible (and inline) search to allow the user to specify in which unit of texts their terms need to occur.
Add reference based units (verse, chapter, book) and structural units (phrase, clause, sentence, paragraph, pericope).
49
Comments
-
@mjespuiva-86 We've talked about more explicitly adding multiple search document options for Bibles: reference based units (verse, chapter, book) and structural units (phrase, clause, sentence, paragraph, pericope). Currently, we support verse through Bible search, chapter through Basic search, and clause through Clause search. Ideally, we'd support all from one search type and not requiring switching modes.
I'll probably create the broader suggestion and merge this one into that one.0 -
I agree completely. There should be a dropdown option WITHIN "verse, chapter, book, sentence, paragraph, pericope).0
-
In a Bible search there is no choice of unit - it is verse. However, in an Inline Search, a Bible search has three possible units: Verse, Paragraph, Pericope. Please add these options into the Search Panel Bible Search and, therefore, into the graphing of the Bible Search Results.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
1 -
Note that those aren't search units; they simply control the amount of context shown when the resource text is filtered by the inline search.
You probably want to vote for this suggestion instead: https://feedback.faithlife.com/boards/logos-desktop-app/posts/2440 -
@bradley-grainger I understand that. But I thought that the "amount of context" also controlled the "nnn occurrences" i.e. 54 occurrences in 4 pericopes and on a pericope xnnn. I want both the ability to define the scope and to search report units. The scope parameter would make the boundaries for complex search arguments logical rather than the arbitrary "verse".
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
I would love to see search results by paragraph/pericope; on certain kinds of searches it would greatly reduce the number of discrete results.0
-
When I search for {Section <Event Birth of Jesus>} in the ESV, Logos returns 21 results in 21 verses. BUT, there are only two pericopes, Matthew 1:25 and Luke 2:1-20. Logos offers to show me the results in a grid, as individual verses, with the results aligned, or a more complex analysis of the results. It would be nice if there was also a Pericope option, perhaps even "folded," so that contiguous verses were not separated, but part of a single unit.1
-
As Bible Search has already been compromised by the passage search with no explicit 'boundary' i.e. footnotes, and Clause has been suggested as a boundary (but not with the parameters from Clause Search) there appears to be a good case for combining Bible Search and Basic Search to facilitate this suggestion (you will have to select 'Bible Text' as a Search Field). But we should be aware that 'reference based units' are 'structural units' or boundaries wherein we want to find a match. It's just that some depend on the resource type and may be subjective/unsuitable for others e.g. phrase, clause, are more subjective than a literal sentence or paragraph. So these need to be suggested as available/sensible for the search. And I prefer them as options rather than search terms (simplifies the syntax).
It has my vote on this proviso (not restricted to Bibles).0 -
@phil-gons I have wanted this capability for many years and have used it in other Bible programs. You need both proximity (within so many words) and boundaries (clause, sentence, paragraph, pericope, verse, chapter). I would like this for Bible searches and Morphological searches. It is critical for the Morph Query Editor, because combinations of morphological features usually only are meaningful within either a clause or a sentence.0
-
Some Bible resources have verse numbering ranges (instead of numbering each verse individually) so pericope (paragraph) boundary Bible resources could be created as an alternative, which would work with existing Bible Search.0
-
Searching biblical text with parameters broader than, simply, verse seems to be a rather basic need for Bible software (e.g. when searching in @ccord@nce, specifying various parameters is a given). This addition would certainly be needed & welcomed. Thanks for taking it into consideration.0
-
@harryhahne An extremely hearty second to Dr. Hahne's comment. I would add that there are even usage cases for broader textual parameters, such as discourse & rhetorical units.0
-
Would love to see choices of ... some form of range of verses. Book, chapter, etc.
xn = Christan man=man -- Acts 11:26 "....and the disciples were first called Christians in Antioch".
Barney Fife is my hero! He only uses an abacus with 14 rows!
0 -
A number of feedback requests address the desire for AI search. Incorporating search scoping and AI-based search would be an improvement, as I still go to Google or ChatGPT, when Logos search doe not find what I know is in various texts.0
-
Adding my vote here! I think the "fuzzy" search especially feels limiting and often misses verses that to me seem obviously related to my query.
I came to the forum today looking for a way to overcome the limitations of a morph query search that might span a poorly placed chapter division (those areas where most modern translations do not put their section name / header at the beginning of a chapter because the chapter break actually interrupts the flow of the pericope).0
