Prioritizing "current resource"

I imagine this has been asked and answered. I just don't recall what the answer is or if it's an answer that I'd like.

Is there a way to "prioritize" the "current resource." I put those words in double quotes because I don't care so much how to get the effect I want as to get the effect. Here's my current situation...

My #1 prioritized Bible is the ESV. At present, I'm reading the NET Bible First Edition Notes. Each set of notes on a verse is preceded by a heading: "Notes for <chapter>:<verse>." And the chapter/verse references are links, as they should be. When I hover over those links, the text of the verse is displayed. Unfortunately, though, it's the ESV text, not the NET text. This is a very obvious situation where the only thing that makes sense to display is the NET Bible's text, because the notes are specific to why the translators chose certain words or phrases to translate the underlying text.

So, is there a way to make those links refer to the NET Bible's text instead of to the ESV, while still leaving the ESV as my #1 prioritized Bible? The software guy in me thinks I should be able to prioritize a logical item, "Current Resource," which would be checked first when hovering / linking within a resource.

Thanks,

Donnie

Find more posts tagged with

Comments

MJ. Smith

Yes, this is a case for advanced prioritization - prioritize the Net Bible for the Net Notes. I have requested a generic ability to set the advanced priority to the top translation used in a resource - a change that would require additional metadata but would resolve you situation. I have gotten very little support.

Mike Binks

I think this is the sort of thing you need?

Dave Hooton

So, is there a way to make those links refer to the NET Bible's text instead of to the ESV, while still leaving the ESV as my #1 prioritized Bible?

This is what you want

ESV is still #1 even though you have to prioritize NET (for a specific purpose) ahead of it.

Note: the NLT is restricted to the Bible datatype else its Bible Verse Finder will be my #1 Bible Dictionary, ahead of The Harper Collins Bible Dictionary!

John Fidel

https://community.logos.com/discussion/comment/804541#Comment_804541

Dave,

Thanks for the note on the NLT. I actually removed it from my prioritization due the english word lookup issue.

GregW

A less permanent way of doing it would be to open the NLT, click on the image on the top left-hand corner of the tab, and select "Send hyperlinks here". You could presumably also save that as a layout to use when you're working through the NLT notes.

Donnie Hale

https://community.logos.com/discussion/comment/804501#Comment_804501

Thanks for all the replies. I'm aware of advanced prioritization, but I think I've only used it once; and I did that 4-5 years ago.

I have gotten very little support.

You / we probably need a way to explain the benefits of such a feature versus how it might be implemented. As libraries expand, the need for such prioritization grows. Having to do it one resource at a time makes the horrific prioritization interface even more obvious. Intuitively, it seems to me that resources such as the one I referenced ought to behave this way without any explicit settings whatsoever (whether resource by resource or a one-time generics setting).

Donnie

Dave Hooton

https://community.logos.com/discussion/comment/804943#Comment_804943

I've needed advanced prioritization as an exception on 6 occasions; mainly to correct prorities for lexicons that have multiple indexes e.g. to prevent the 3x DBL lexicons being #1 for Greek and Hebrew Strong's numbers! This could be allayed by applying a default, but it would be difficult to meet every need. My NLT prioritization is relatively safe as a default!