Bug: Advanced Prioritization of Louw-Nida

Advanced prioritization of LN for Greek headwords for internal reference to LN previously double click on headwords within LN took the reader to volume 2. Now the functionality has been changed; double click has no result. In order to get to vol 2, one must search LN and select headword for vol 2 from the list of results. Please restore previous behavior, It was simple and efficient; I'm not sure when this was changed or why.

Find more posts tagged with

Comments

Keep Smiling 4 Jesus :)

Support Info shows revision on 21 Sep 2017:

LLS:46.30.4
2017-09-21T01:21:22Z
LOUWNIDA.logos4

Volume 1 now has Greek Headword indexing (along with Louw Nida number and page) that is found before Volume 2

When a Greek headword has more than one Louw-Nida number, the first Louw-Nida number is now found: e.g. ψυχή headword opens LN 9.20 (found LN 4.1 idiom has "ψυχὴ ζωῆς" for Greek Headword index that does not match ψυχή).

Please restore previous behavior, It was simple and efficient; I'm not sure when this was changed or why.

+1 [Y] for removing Greek Headword indexing from Volume 1

Keep Smiling [:)]

https://community.logos.com/discussion/comment/932971#Comment_932971

Volume 1 now has Greek Headword indexing (along with Louw Nida number and page) that is found before Volume 2

KS4J,

I take no issue with how LN functions for Greek headwords referencing vol1. My issue is that advanced prioritization has been nullified. I must manually page to vol 2 or search resource to access vol 2 whereas before this was achieved with a double click. Are you satisfied with this new behavior and if so why? If FL were to allow access to vol 2 from the drop down menu in vol 1 I would be satisfied.

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/932986#Comment_932986

I must manually page to vol 2 or search resource to access vol 2 whereas before this was achieved with a double click.

Double click selects word followed by looking up that word using Greek headword index, which has the first index search result in volume 1. Hence, search is needed to find Volume 2 headword (OR manually select Volume 2 entry). One way to "restore" double click into Volume 2 is removal of Greek headword tagging from Volume 1.

If FL were to allow access to vol 2 from the drop down menu in vol 1 I would be satisfied.

Faithlife developers may be able to provide another way to access Volume 2.

Concur Volume 2 is useful, especially with Power Lookup showing range of semantic usage (with links to Volume 1)

Keep Smiling [:)]

https://community.logos.com/discussion/comment/933009#Comment_933009

I personally like the change to headwords especially when I have multiple resources open. I can now go directly to the intended meaning without going to the index. I also understand your preference and its importance. I was wondering if if was possible in advanced prioritization to select the page numbers so that only volume 2 is selected?

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/933011#Comment_933011

I can now go directly to the intended meaning without going to the index.

Clicking "bearing" in Hebrews 13:13 (1984 NIV) changes LN position to 90.64 (Bible and Lexicon linked) with headword φέρω (9) so suspect LN number was used (Right Click on bearing lacks (9) suffix). Double clicking φέρω changes LN position to LN 13.35 (send hyperlinks here) that is the first occurrence of φέρω (headword is in Volume 1 and Volume 2)

I was wondering if if was possible in advanced prioritization to select the page numbers so that only volume 2 is selected?

Advanced Prioritization allows filtering to Greek (headwords in resource), but does not allow passage specification: e.g. Volume 2.

Keep Smiling [:)]

https://community.logos.com/discussion/comment/933009#Comment_933009

Concur Volume 2 is useful, especially with Power Lookup showing range of semantic usage (with links to Volume 1)

Contemplating this issue and its implications lead me to conclude that the best way to call attention to this matter is to classify this iteration as a bug.

https://community.logos.com/discussion/comment/933029#Comment_933029

he best way to call attention to this matter is to classify this iteration as a bug.

I would agree

https://community.logos.com/discussion/comment/933049#Comment_933049

I would agree

bump to Philana Crouch

https://community.logos.com/discussion/comment/933229#Comment_933229

Pay attention FL. Let's hear from you!

Adam Borries (Logos)

https://community.logos.com/discussion/comment/933496#Comment_933496

We'll look into it. Can you provide a screenshot of your advanced prioritization settings for LN? Thanks.

https://community.logos.com/discussion/comment/933498#Comment_933498

Thanks, Adam that was quick! Here it is; sorry I had to break it up.

Lankford Oxendine

https://community.logos.com/discussion/comment/933503#Comment_933503

What's the status on this bug? Did FL ever acknowledge? The current behavior with Louw-Nida is infuriating.

Philana R. Crouch

https://community.logos.com/discussion/comment/947578#Comment_947578

What's the status on this bug? Did FL ever acknowledge? The current behavior with Louw-Nida is infuriating.

This is an issue with how the resource is tagged and we do have an open case for it.

Lankford Oxendine

https://community.logos.com/discussion/comment/947683#Comment_947683

Thank you for the response!

https://community.logos.com/discussion/comment/947683#Comment_947683

What's the status on this bug? Did FL ever acknowledge? The current behavior with Louw-Nida is infuriating.

This is an issue with how the resource is tagged and we do have an open case for it.

Word, Philana?

https://community.logos.com/discussion/comment/984830#Comment_984830

bump

Philana R. Crouch

https://community.logos.com/discussion/comment/985172#Comment_985172

bump

Hi Beloved,

I don't have any updates. I'll check into it.

Kyle G. Anderson

https://community.logos.com/discussion/comment/985243#Comment_985243

Beloved

I have a plan for a resource update that will make it easier for you to use. It will probably be a couple of months before I'm able to get it out the door though.

Lankford Oxendine

https://community.logos.com/discussion/comment/985327#Comment_985327

Thank you Beloved for keeping this issue "alive". I am patiently awaiting an update.

https://community.logos.com/discussion/comment/985327#Comment_985327

Beloved

I have a plan for a resource update that will make it easier for you to use. It will probably be a couple of months before I'm able to get it out the door though.

Thank you Kyle, I hope it addresses easy access to vol. 2 from headword, in anticipation. Also, thank you for your reply Philana.

https://community.logos.com/discussion/comment/985328#Comment_985328

Thank you Beloved for keeping this issue "alive". I am patiently awaiting an update.

Happy to see that I'm not alone in seeing this as an important issue.

https://community.logos.com/discussion/comment/985327#Comment_985327

It will probably be a couple of months before I'm able to get it out the door

Hi Kyle,

Any ETA on this release now that we're closer to 2mos.?

Kyle G. Anderson

https://community.logos.com/discussion/comment/992362#Comment_992362

It will probably be a couple of months before I'm able to get it out the door

Hi Kyle,

Any ETA on this release now that we're closer to 2mos.?

Beloved,

There have been other projects ahead of it in line that I've been working on but I'm hoping to start in the next couple of weeks. Thankfully I don't anticipate it being a too time intensive project.

https://community.logos.com/discussion/comment/992372#Comment_992372

Thanks, Kyle

I look forward to seeing this happen soon. Much appreciated.

https://community.logos.com/discussion/comment/992372#Comment_992372

Beloved,

There have been other projects ahead of it in line that I've been working on but I'm hoping to start in the next couple of weeks. Thankfully I don't anticipate it being a too time intensive project.

I know your busy with the Tov book corrections, but you still have yet to release the fix for Louw-Nida. I would appreciate a rough estimate of the release date for this fix, please. My interest in the Tov book corrections is with the hope that the author will reconsider his decision to stop the sale of his important work in Logos format.

Kyle G. Anderson

https://community.logos.com/discussion/comment/1010611#Comment_1010611

Beloved,

There have been other projects ahead of it in line that I've been working on but I'm hoping to start in the next couple of weeks. Thankfully I don't anticipate it being a too time intensive project.

I know your busy with the Tov book corrections, but you still have yet to release the fix for Louw-Nida. I would appreciate a rough estimate of the release date for this fix, please. My interest in the Tov book corrections is with the hope that the author will reconsider his decision to stop the sale of his important work in Logos format.

I apologize for the delay in communication. Unfortunately due to other projects and the nature of the work that will need to be done that creates a solution that will work for the greatest number of people it is going to take longer than I hoped and won't be finished until late-February.

As for Tov: I'm not involved in those discussions so I don't have anything to add beyond "we are too."

https://community.logos.com/discussion/comment/1010621#Comment_1010621

due to other projects and the nature of the work that will need to be done that creates a solution that will work for the greatest number of people it is going to take longer than I hoped and won't be finished until late-February.

Hi Kyle,

Is this a good time to check on your progress? This still remains an issue. Thanks.

Kyle G. Anderson

https://community.logos.com/discussion/comment/1036084#Comment_1036084

due to other projects and the nature of the work that will need to be done that creates a solution that will work for the greatest number of people it is going to take longer than I hoped and won't be finished until late-February.

Hi Kyle,

Is this a good time to check on your progress? This still remains an issue. Thanks.

It's being worked on right now. Best case it gets pushed out on Monday with the next batch of resource updates but three weeks feels more likely.

https://community.logos.com/discussion/comment/1036093#Comment_1036093

Thanks Kyle, you inspire faith. Looking forward to the fix!

https://community.logos.com/discussion/comment/1036136#Comment_1036136

I just want to add my voice to this thread - I too have run into this problem and have been frustrated by it. I finally started researching why this didn't work as it used to (very frustrating) and found this thread. Please prioritize!

And thank you as always for such a useful product!

https://community.logos.com/discussion/comment/1037355#Comment_1037355

Kyle,

So happy with the fix for this issue.Thanks [8-|]

Lankford Oxendine

https://community.logos.com/discussion/comment/1042332#Comment_1042332

I'm still showing the old behavior. This issue has been fixed?

Kyle G. Anderson

https://community.logos.com/discussion/comment/1042332#Comment_1042332

Kyle,

So happy with the fix for this issue.Thanks

I'm so glad to hear that. I hadn't heard from you and I was getting worried. I was hopeful that it was a fix that would make everyone happier.

Kyle G. Anderson

https://community.logos.com/discussion/comment/1042336#Comment_1042336

I'm still showing the old behavior. This issue has been fixed?

Could you check your resource version for me? It's possible you're looking at the old version still.

Lankford Oxendine

https://community.logos.com/discussion/comment/1042342#Comment_1042342

Is this it?

LLS:46.30.4
2019-03-11T22:10:28Z
LOUWNIDA.logos4

https://community.logos.com/discussion/comment/1042343#Comment_1042343

Is this it?

LLS:46.30.4
2019-03-11T22:10:28Z
LOUWNIDA.logos4

That's up to date. Perhaps you are not familiar with how it has changed. Now if you hover over the superscript a popup will appear if you click on the superscript when the popup is in view it will take you to volume B. Neat huh?!

Lankford Oxendine

https://community.logos.com/discussion/comment/1042360#Comment_1042360

Oh, I got it. Thanks Beloved. I was double clicking on the headword with no success. Thanks for the quick tutorial. How did you know about the change? I obviously missed something.

https://community.logos.com/discussion/comment/1042362#Comment_1042362

How did you know about the change?

When I opened Logos to do some housekeeping on some new resources it was first in my list of updated resources.

Quick Links