BUG? Is this the intended behavior of Bible dictionaries in the Context menu?

MJ. Smith

Two questions:

1. I thought only 5 entries would appear in the Context Menu ... or at least no more than I had prioritized (line shows end of priorities and beginning of alpha order)
2. Why doesn't my 2nd priority Dictionary show? Am I mistaken in my belief that when a resource is released it is fully functional i.e. is there a delay while it is added to certain system datasets?

Dave Hooton

MJ. Smith said:

I thought only 5 entries would appear in the Context Menu

Person entries appear to be treated differently to Selection entries in the Context Menu.

MJ. Smith said:

Why doesn't my 2nd priority Dictionary show?

Assuming CBD has an entry for Aaron?

I find that ISBE (1915) isn't listed for Person Aaron but ISBE_Ages is. The prioritised ISBE (1915) is listed for Selection Aaron, though.

This suggests that Person lists prioritised LCV** resources whilst Selection lists your prioritised resources as expected.

 

** Logos Controlled Vocabulary uses a controlled set of resources for topics e.g. in Topic Guide

MJ. Smith

https://community.logos.com/discussion/comment/606545#Comment_606545

Thanks Dave, that makes sense even if I would still prefer a cutoff at 5.

fgh

Dave Hooton said:

MJ. Smith said:

I thought only 5 entries would appear in the Context Menu

Person entries appear to be treated differently to Selection entries in the Context Menu.

Odd.[:S]

Dave Hooton said:

I find that ISBE (1915) isn't listed for Person Aaron but ISBE_Ages is. The prioritised ISBE (1915) is listed for Selection Aaron, though.

This suggests that Person lists prioritised LCV** resources whilst Selection lists your prioritised resources as expected.

Also odd.[:S] Especially as you can't easily use Selection for names like Mary Magdalene. If you select Mary, Logos doesn't know which Mary to look up, and if you select Mary Magdalene, you don't get any dictionaries at all. I guess Magdalene might work -- as long as the translation hasn't chosen 'of' or 'from Magdala' instead (which the Swedish translations do).

And these two issues together result in unintentional deception: the more resources I see in the menu, the more convinced I become that all possible resources are indeed listed.

MJ. Smith said:

Am I mistaken in my belief that when a resource is released it is fully functional

It seems you are, though I'm not quite sure how you could believe that after all this time, and after all the errors you have reported.

I find it disrespectful (and I could use considerably stronger language) to demand full payment and not deliver a fully functional resource. The tagging should be done before we're charged, not after!

Sean Boisen

https://community.logos.com/discussion/comment/606718#Comment_606718

There are a few different things interacting here:

• When the key is selected text from a Bible that refers to a person, and you choose Person, that accesses the Bible Facts data for that person.
• The Bible Facts person then acts as the key to the LCV.

This is a case of "strong" reference: we have an actual identity for the person in question. The list of dictionaries here should be the same as the list in Bible Facts, and in the same order. But it only includes dictionaries with LCV alignment.

When there's selected text and you choose Selection, it's using that string and looking at the table of contents for various dictionaries. So this is "weak" reference: we don't actually know anything about the object, we're just doing string matching.

If you look at Ex 4:14, you can see the different behavior of Selection if the selected text is "Aaron" vs. "brother". But the behavior of Person is the same, because we know the referent of "brother" in this context is really Aaron the person.

We haven't completed LCV alignment for all dictionaries yet, especially some legacy cases (including CBD). Most new (to Logos) dictionaries should have that alignment done when we release them, though.

I have entries in both modern ISBE (LLS:14.0.24 on the Info page) and public domain ISBE (LLS:14.0.1001) for the string "Aaron", and both come up for the Bible Facts person Aaron. They're listed in my prioritized order.

MJ. Smith

https://community.logos.com/discussion/comment/606852#Comment_606852

Thanks Sean that makes sense ... except for one detail. The Catholic Bible Dictionary is a new release.

Dave Hooton

https://community.logos.com/discussion/comment/606852#Comment_606852

Sean Boisen said:

Most new (to Logos) dictionaries should have that alignment done when we release them, though.

I have entries in both modern ISBE (LLS:14.0.24 on the Info page) and public domain ISBE (LLS:14.0.1001) for the string "Aaron",

The 1915 version LLS:INTLBBLDICT1915 is a significant omission!

Sean Boisen

https://community.logos.com/discussion/comment/606899#Comment_606899

MJ. Smith said:

Thanks Sean that makes sense ... except for one detail. The Catholic Bible Dictionary is a new release.

That's why i included the weasel word: "Most new releases ...". This resource is definitely queued for LCV alignment, but it hasn't happened yet.

Sean Boisen

https://community.logos.com/discussion/comment/606905#Comment_606905

Dave Hooton said:

Sean Boisen said:

Most new (to Logos) dictionaries should have that alignment done when we release them, though.

I have entries in both modern ISBE (LLS:14.0.24 on the Info page) and public domain ISBE (LLS:14.0.1001) for the string "Aaron",

The 1915 version LLS:INTLBBLDICT1915 is a significant omission!

Dave, i'm checking on this.