Syntax Search

Currently the clause is only highlighted in the clause visualization resource that corresponds to the database you searched (opentext.org clause analysis etc.).

Robert Pavich

https://community.logos.com/discussion/comment/22712#Comment_22712

Linking results to the OpenText GNT as in v3.

thanks for the explanation Dave...and now I agree also.

Dave Hooton

https://community.logos.com/discussion/comment/22713#Comment_22713

Currently the clause is only highlighted in the clause visualization resource that corresponds to the database you searched (opentext.org clause analysis etc.).

David, there is a real lack of information with the currently linked resource - Clause Analysis. No node info, no word definition nor morphology. This was all available in v3 + a link to OpenText GNT.

Robert Pavich

https://community.logos.com/discussion/comment/22718#Comment_22718

I use OpenText A LOT...more than any other type of search sometimes and it seems like this resource is getting neglected... [:(]

davidphillips

https://community.logos.com/discussion/comment/22727#Comment_22727

Dave and Robert,

I agree. Hopefully this is something that will get fixed prior to the launch day. Currently, the clause analysis gives the lexical form of a word as well as the LN number, but that's it. But strangely, the opentext GNT gives morphology as well and also has a pop-up information window that gives LN info (at least on my system). The opentext.org GNT also has hover-over pop-up info for the syntax tags. So all that information is there and readily available. This makes me hopeful that it is a simple fix to get it to appear with the clause-analysis as well!

Cameron Watters (Faithlife)

But after running a syntax search, neither the clause nor the word is highlighted in the parallel english/interlinear resource.

This is a must have feature when working with syntax.

This feature is on our list, but I can't speak to a specific timeline for when it will be added. The issue affects parallel results views for both Syntax and Bible searches.

Rick Brannan (Logos)

https://community.logos.com/discussion/comment/22731#Comment_22731

Currently, the clause analysis gives the lexical form of a word as well as the LN number, but that's it. But strangely, the opentext GNT gives morphology as well and also has a pop-up information window that gives LN info (at least on my system). The opentext.org GNT also has hover-over pop-up info for the syntax tags. So all that information is there and readily available. This makes me hopeful that it is a simple fix to get it to appear with the clause-analysis as well!

Hi David.

We finally tracked this one down today. There are two issues here:

1: morph info in bottom-left popup while hovering "word" in OpenText.org clause analysis

2: glossary info on hover of clause or word group nodes

On item 1, we've rebuilt the resource to do this, though it will likely not be in the next resource download (done too late).

On item 2, it is not an issue with the resource but with the code that displays it, this will make it into a future release as well.

Thanks for the information and your patience with us while we tracked it down. This (item 2) was not an easy one to find.

davidphillips

https://community.logos.com/discussion/comment/23009#Comment_23009

Cameron and Rick,

Thanks for all the great work you guys are doing with these resources! It is greatly appreciated [:)]

Dave Hooton

https://community.logos.com/discussion/comment/23009#Comment_23009

We finally tracked this one down today. There are two issues here:

1: morph info in bottom-left popup while hovering "word" in OpenText.org clause analysis

2: glossary info on hover of clause or word group nodes

Rick, thanks for your efforts in resolving these issues.

If you have some time, I'd appreciate your insights on our discussions at http://community.logos.com/forums/t/3045.aspx and

http://community.logos.com/forums/p/2913/23025.aspx#23025

thanks,

Rick Brannan (Logos)

https://community.logos.com/discussion/comment/23078#Comment_23078

If you have some time, I'd appreciate your insights on our discussions at http://community.logos.com/forums/t/3045.aspx and

http://community.logos.com/forums/p/2913/23025.aspx#23025

Hi Dave.

I've been following the 'gap' discussion, I haven't responded because gaps are complex and I haven't been able to take the necessary time to respond properly. That, and my understanding of them isn't as comprehensive as folks would like to think [:D].

The basic issue is that 'gap' is a property of the underlying search technology, not of the databases. The gap object, which looks, smells and seems to act like the other search objects for each database, was simply the best way we could come up with to access the functionality of using gaps in searches in the LDLS3/Logos4 interfaces.

So gaps aren't marked in the same way that, say, subjects are marked, but the way queries are structured in our implementation almost suggests they are, which is where some confusion may occur. In order to really understand gaps, I'll have to dig back into the documentation of the underlying technology (Emdros) to remember everything. If you go here: http://emdros.org/MQL-Query-Guide.pdf and dig starting at page 9, you may be able to discern some principles. Note that the documentation discusses some functionality that may or may not be currently supported in the Logos implementation, and the query language used is not directly supported in Logos either. I'm pointing there for basic principles, not for copy-n-paste examples.

Thanks for asking and wanting to understand gaps better. And thanks for helping to put syntax searching through its paces!

davidphillips

https://community.logos.com/discussion/comment/23089#Comment_23089

That, and my understanding of them isn't as comprehensive as folks would like to think .

[:'(]

Thanks for the feedback, Rick. I'm hesitant to glance at the emdros stuff, but maybe I'll take a look. Your explanation answers some questions though and makes sense.