Suggestion: Morph Query Builder clause and sentence boundary

I appreciate having the Morph Query Builder, because it lets me do some searches that were much easier to set up in the older Gramcord Bible Software. However, one major thing that seems to be missing is the ability to limit the search to clause or sentence boundaries. Gramcord has the option of limiting the search to one or more clauses (delimited by a minor stop - comma or dash) or sentences (delimited by a major stop - period, semi-colon or question mark). This capability is essential for grammatical searches. For many searches, the search term must be within the same clause or sentence. Delimiting the search boundary to a verse, as the Morph Query Builder presently does, will find many false hits and may miss legitimate instances where a sentence crosses a verse boundary.

If this feature exists, I may have overlooked it. If it is not yet implemented, I think it is a critical to include it when the Morph Query Builder is officially released. Until it is included, I am afraid I will continue to use Gramcord for most grammatical searches.

Find more posts tagged with

Comments

Dave Hooton

Morph Query is not a clause/sentence search; for that we have Clause Search and Syntax Search.

Delimiting the search boundary to a verse, as the Morph Query Builder presently does, will find many false hits

The Search Span is flexible and can be set to multiple Hebrew segments, multiple Greek words or multiple verses. So the search boundary is not limited to a verse.

Harry Hahne

https://community.logos.com/discussion/comment/896851#Comment_896851

My biggest problem with the Syntax search is that it is very time consuming to set up and search design is very error prone. The Morph Query Editor is quick and simple to set up.

It would be a simple matter to add a delimiter based on punctuation marks, as Gramcord does. If the number of words in the "search span" was not reached, but a full stop was reached, then the search would end. Gramcord offers the option of ending the search at a major or minor stop or the end of a verse. This design does not require any analysis of the meaning to create the database, as is necessary for the databases set up for the Syntax search. A Syntax search is always limited by the subjectivity of the classifications of clauses and word relations when the Bible was tagged.

It is frustrating to have a tool like MQE that almost does what I need. Logos could occupy the role of Gramcord with only a few refinements. In the meantime, I will keep a Virtual Machine running Windows XP on my computers, so I can continue to use Gramcord. Either that or I will

Dave Hooton

https://community.logos.com/discussion/comment/896883#Comment_896883

It would be a simple matter to add a delimiter based on punctuation marks, as Gramcord does. If the number of words in the "search span" was not reached, but a full stop was reached, then the search would end.

To be clear, the "Search Span" would be a Sentence (with Full Stop as the delimiter). In addition you can specify Proximity via Add relation, which is labelled as a "Span" and functions much the same way as text search proximity. So if you wanted two words to be separated by no more than one intervening word, your "Span" would be 3 words (counting first result, last result and the word in between). The minimum "Span" is thus 2 Words. If you specify "Search Span" as one Sentence, then both results have to occur within a sentence.

SBLGNT has full stops, so it is possible...

Harry Hahne

https://community.logos.com/discussion/comment/896928#Comment_896928

If you specify "Search Span" as one Sentence, then both results have to occur within a sentence.

That is what I am looking for. I assume you are clarifying what I am asking for. Currently there is no option to specify "Search Span" as a number of Sentences. The only options are words and verses.

Dave Hooton

https://community.logos.com/discussion/comment/896972#Comment_896972

That is what I am looking for. I assume you are clarifying what I am asking for.

I was clarifying your statement "If the number of words in the "search span" was not reached, but a full stop was reached, then the search would end." by stating that the search span required would be a "sentence"; and that it would not be expressed as a "number of words".