Documentation of Search quirks

I know this is unlikely to get the response I want but ---

As I go testing the outer edges of the Search function, I am coming across forums posts telling me that the Search failed because search argument structure X is known to not work. Unfortunately, as I run across these posts, I have no way to telling if the problem has been resolved. Setting up a test case, finding a test case, or giving up on getting a good test case, then running the search to see if it is still a problem is a temporary, frustrating, stop gap solution.

Would it be possible to get a list of the problem reports on the search for correct syntax but incorrect or absent results? Then when I hit a problem, I can check if it is the fault of the search engine or me.

Find more posts tagged with

Desktop App

Comments

Dave Hooton

Would it be possible to get a list of the problem reports on the search for correct syntax but incorrect or absent results?

Unlikely! Sometimes the documentation is wrong/incomplete & you may learn it from Context Menu. Sometimes the latter is wrong and you get no results. But I don't report/document these unless I'm working on a user issue (I tend to work around such issues). The biggest issue is the out dated documentation, or documentation that doesn't easily lead you to the Search syntax e.g. "Lexham Figurative Language of the Bible Glossary" (2018) includes the Dataset Documentatio (FLD). The Category Hierarchy doesn't help with the Search syntax e.g. if you want Ontological Metaphor, the syntax is Metaphor, Ontological. The syntax for "Container Metaphor" is Metaphor, Ontological, Container and not Metaphor, Container i.e. hierarchical. You learn to work it out from the Context Menu.

The documentation would also lead you to use {Label Figurative Language WHERE Category ~ <FigurativeLanguageCategory Idiom>} rather than the much faster {Section <FigurativeLanguageCategory = Idiom>} from the Context Menu. Also, you have to learn that Meta, Ont, Cont can be used in place of Metaphor, Ontological, Container. Also, when do you use = vs. ~ ?

MJ. Smith

https://community.logos.com/discussion/comment/1170048#Comment_1170048

I understand what you mean but I was thinking more of the INTERSECTS limitation and other cases where Bradley says that the error in the search engine is known e.g.

Bradley Grainger (Faithlife) wrote:

“it's currently a known limitation of the search engine that "INTERSECTS" can't be used as the operand of a proximity operator. We have a case to fix this limitation.[1]”

SineNomine

Vote now: https://feedback.faithlife.com/boards/logos-desktop-app/posts/document-the-search-function-in-full

Phil Gons (Logos)

https://community.logos.com/discussion/comment/1170051#Comment_1170051

I understand what you mean but I was thinking more of the INTERSECTS limitation and other cases where Bradley says that the error in the search engine is known e.g.

Bradley Grainger (Faithlife) wrote:

“it's currently a known limitation of the search engine that "INTERSECTS" can't be used as the operand of a proximity operator. We have a case to fix this limitation.[1]"

This is no longer a limitation in Logos 10.