5.1 Beta 6: Internal links in open resource jump to other edition of that book

I just downloaded McNeill's edition of Calvin's Institutes. Was very excited to try out the indexes. Clicked on a link, and it opened the Henry Beveridge translation to the corresponding location. Very disappointing. I know I can work around this by prioritizing McNeill, but...

If a link within a book is to a location in that same book, the default prioritization should be the very same edition you have open; this should trump the normal default prioritization (alphabetical) if neither edition is explicitly prioritized.

Find more posts tagged with

Comments

Bradley Grainger (Logos)

I know I can work around this by prioritizing McNeill, but...

You can also work around it by selecting "Send hyperlinks here" on the McNeill resource panel menu.

Rosie Perera

https://community.logos.com/discussion/comment/488856#Comment_488856

I know I can work around this by prioritizing McNeill, but...

You can also work around it by selecting "Send hyperlinks here" on the McNeill resource panel menu.

OK, but will you concede that hyperlinks that refer to a book by datatype, if the currently open book matches that datatype, should jump to the current book, rather than the default prioritized edition of that book? (Sure, if I had the Beveridge edition prioritized and not the McNeill/Battles edition it would make sense to jump to Beveridge on a hyperlink. But there's no sense to the present default behavior. A book's index should jump to itself when you click on a location in it.)

We shouldn't have to work around poor product design. I'm glad there's a workaround for now (I prefer prioritizing McNeill as my workaround, because then I don't have to remember to do it each time I open the book.) But this ought to be fixed.

Will you put this on the internal list of things to fix at some point?

Mark Barnes

https://community.logos.com/discussion/comment/488861#Comment_488861

We shouldn't have to work around poor product design. I'm glad there's a workaround for now (I prefer prioritizing McNeill as my workaround, because then I don't have to remember to do it each time I open the book.) But this ought to be fixed.

If you prioritize McNeil, then internal links in Beveridge will then be 'wrong'.

ut there's no sense to the present default behavior. A book's index should jump to itself when you click on a location in it.

Bradley, Rosie is right. We shouldn't have to do this:

Mark Barnes

https://community.logos.com/discussion/comment/488856#Comment_488856

You can also work around it by selecting "Send hyperlinks here" on the McNeill resource panel menu.

That doesn't help with pop-ups though.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/488861#Comment_488861

OK, but will you concede that hyperlinks that refer to a book by datatype, if the currently open book matches that datatype, should jump to the current book, rather than the default prioritized edition of that book?

So Bible references in a commentary should jump to that commentary (since "the currently open book matches that datatype"), not to your preferred Bible?

The proposed change would affect Bibles & commentaries, the Apostolic Fathers, the Iliad in Greek and English, and any other resources that have multiple translations/editions, so we'd have to thoroughly think through the consequences of that change before making it.

Mark Barnes

https://community.logos.com/discussion/comment/488996#Comment_488996

The proposed change would affect Bibles & commentaries, the Apostolic Fathers, the Iliad in Greek and English, and any other resources that have multiple translations/editions, so we'd have to thoroughly think through the consequences of that change before making it.

That's a fair point. It's certainly useful to be able to prioritize an English edition over a Latin edition, so that I can see English pop-ups instead of Latin ones, even if I happen to be in a Latin resource. But the English Bibles problem I posted about above is a real pain. There's not an easy solution, I fear.

Todd Phillips

https://community.logos.com/discussion/comment/489002#Comment_489002

It would be nice if there was a switchable option in each resource that would cause it to automatically prioritize itself for all datatypes that it handles. Picking the default setting would be tricky.

Rosie Perera

https://community.logos.com/discussion/comment/488996#Comment_488996

OK, but will you concede that hyperlinks that refer to a book by datatype, if the currently open book matches that datatype, should jump to the current book, rather than the default prioritized edition of that book?

So Bible references in a commentary should jump to that commentary (since "the currently open book matches that datatype"), not to your preferred Bible?

The proposed change would affect Bibles & commentaries, the Apostolic Fathers, the Iliad in Greek and English, and any other resources that have multiple translations/editions, so we'd have to thoroughly think through the consequences of that change before making it.

Hmm, I see the dilemma. How about applying my proposed change only to Monographs. Chances are you'd have your Bibles and Commentaries prioritized anyway. My proposed change would not override a user's prioritizations, only the "default" prioritization which Todd told me was alphabetical. Chances are if you're reading one edition of the Iliad and there happens to be a link within it to another location within the Iliad, you'd be fine opening it within the same edition you have open. That's no more likely to be the wrong decision than opening it (rather randomly, I might add) to the "default" edition/translation.

Todd Phillips

https://community.logos.com/discussion/comment/489021#Comment_489021

My proposed change would not override a user's prioritizations, only the "default" prioritization which Todd told me was alphabetical.

Which is true only if Logos hasn't set up some other prioritization, as Mark corrected me on here: http://community.logos.com/forums/p/42471/488985.aspx#488985

Dave Hooton

https://community.logos.com/discussion/comment/488996#Comment_488996

The proposed change would affect Bibles & commentaries, the Apostolic Fathers, the Iliad in Greek and English, and any other resources that have multiple translations/editions, so we'd have to thoroughly think through the consequences of that change before making it.

I agree. The proposed change will also affect Lexicons with multiple indices e.g. DBL Greek/Hebrew with indices for TDNT, TWOT, Greek & Hebrew Strong's Numbers. The most common problem when DBL is prioritized above TDNT, TWOT, & ESL is preventing those links (in DBL) from referring to the same article in DBL! So you need four(4) lots of Advanced Prioritization to ensure those datatypes open the "native" resources.

Rosie Perera

https://community.logos.com/discussion/comment/489029#Comment_489029

The proposed change would affect Bibles & commentaries, the Apostolic Fathers, the Iliad in Greek and English, and any other resources that have multiple translations/editions, so we'd have to thoroughly think through the consequences of that change before making it.

I agree. The proposed change will also affect Lexicons with multiple indices e.g. DBL Greek/Hebrew with indices for TDNT, TWOT, Greek & Hebrew Strong's Numbers. The most common problem when DBL is prioritized above TDNT, TWOT, & ESL is preventing those links (in DBL) from referring to the same article in DBL! So you need four(4) lots of Advanced Prioritization to ensure those datatypes open the "native" resources.

The proposed change is just code. They could code it so it doesn't affect Lexicons at all if that would mess things up even further than they are already messed up.

Dave Hooton

https://community.logos.com/discussion/comment/489032#Comment_489032

The proposed change is just code. They could code it so it doesn't affect Lexicons at all if that would mess things up even further

That's an over-simplification because the proposed change can't be restricted to specific data types and/or resource types because of the mix of resources (including Personal Books) between the libraries of users. At one stage some internal links were hard coded in the resource, but that had its limitations and datatypes were created. So with respect to what Mark illustrated above it is his choice to display, or jump to, bible references (from footnotes) in the same bible as opposed to the preferred bible (ESV in this case).

Advanced Prioritization caters for your situation and it can't be regarded as a special case.

Rosie Perera

https://community.logos.com/discussion/comment/489096#Comment_489096

The proposed change is just code. They could code it so it doesn't affect Lexicons at all if that would mess things up even further

That's an over-simplification because the proposed change can't be restricted to specific data types and/or resource types because of the mix of resources (including Personal Books) between the libraries of users.

That's a non sequitur. It's immaterial what the resource type of the link is; what matters is the resource type of the resource containing the link.

Here's pseudo code to avoid having my proposed change affect Lexicons, Bibles, Commentaries:

if (current resource is a Monograph AND link datatype == current resource's datatype AND no other resource with the same datatype is prioritized)

interpret the link as jumping within the current resource

else

do whatever the existing Logos code does