Unable to replicate visual filter for BDAG

Hey guys, I've been watching a training video on Searching Lexicons but have been unable to replicate the visual filter created for BDAG in the video. Discussion on the visual filter runs from about 3:20-5:00, but the basic idea is to colour code text labeled according to their specific search fields within BDAG (what fields are in use is accessed via BDAG -> Information -> Search Fields). See an example from the video below.

So far I can create a visual filter document for a book, specified as BDAG, with all text being searched. Search fields are entered as lemma:* and formalequivalent:* respectively, with the * indicating wildcards so that any and all lemmas or formalequivalent text is highlighted. BDAG recognizes that there is a visual filter there, but that's about it - nothing is highlighted, and I can't select a specific visual filter in a drop down menu. Help would be appreciated, any idea where I might be going wrong?

For bonus points, I also haven't been able to replicate the inline search of BDAG described from 10:20min onwards...but figured one issue at a time. Stick out tongue

Find more posts tagged with

Desktop App

Comments

Dave Hooton

So far I can create a visual filter document for a book, specified as BDAG, with all text being searched. Search fields are entered as lemma:* and formalequivalent:* respectively, with the * indicating wildcards so that any and all lemmas or formalequivalent text is highlighted. BDAG recognizes that there is a visual filter there, but that's about it - nothing is highlighted,

It takes a long time to generate wildcard entries in the book, and the VF itself may not be listed when you initially load the book.

You need field.lemma:* in the VF for it to be recognised.

Mal Walker

https://community.logos.com/discussion/comment/1279750#Comment_1279750

Had a bit more of a play around and still haven't been able to figure it out. I've tried field.lemma:* as well to no avail. I'm not sure that it's required though, the demonstration in the video doesn't use field.lemma:*

Morgan

https://community.logos.com/discussion/comment/1279954#Comment_1279954

field.lemma:* is working, but something to consider is how long it takes for this filter to kick in.I have an embarrassingly impressive machine to run Logos and it took nearly 4 minutes (3:38) for the filter to finish displaying. I don't have the patience to test it on my slower laptop.

You might just need to wait longer to see it work.

Mal Walker

https://community.logos.com/discussion/comment/1279975#Comment_1279975

Our Lord clearly thinks I still need to grow in patience. Thanks Morgan, I'll give it another go!

Mal Walker

https://community.logos.com/discussion/comment/1280043#Comment_1280043

Looks like I needed to wait a between 5-10min for the visual filter to populate throughout BDAG. Thanks Dave and Morgan for your help. For posterity's sake, I ended up using:

field.lemma/content:*

field.formeq/content:*

field.extdef/content:*

field.transeq/content:*

Graham Criddle

https://community.logos.com/discussion/comment/1280209#Comment_1280209

Looks like I needed to wait a between 5-10min for the visual filter to populate throughout BDAG. Thanks Dave and Morgan for your help. For posterity's sake, I ended up using:

field.lemma/content:*

field.formeq/content:*

field.extdef/content:*

field.transeq/content:*

Please be aware that these will run each time you start Logos - and will take that time to become visible.

Mal Walker

https://community.logos.com/discussion/comment/1280216#Comment_1280216

Yes, you are correct Graham, I've discovered that. It works well when I open Logos at the start of the day and use/keep open BDAG the whole time, but for quick opens and closes it's useless. Would be nice if we could make visual filters persist/save through open/closes for instances such as this, colour coding BDAG has been very helpful for me.

Dave Hooton

https://community.logos.com/discussion/comment/1280209#Comment_1280209

field.lemma/content:*

field.formeq/content:*

field.extdef/content:*

field.transeq/content:*

content applies to the original text of a non-bible (e.g. Ancient Manuscript) and does not apply to lexicons. It probably will not affect performance, but removing /content will avoid possible confusion.