Inconsistant Bibliography Data in Pop-Up

Maybe I am missing something here. Not sure where to post this as I am running the latest beta.

Though a resource is in my library, half the time when I click on one it behaves as if I do not have the resource. In the two screen shots I have both resources with same dates of editions but one pop-up gives me a link to the resource while the other does not. I have tried this in multiple resources to the same end. Additionally, one does not provide a link to send to one of my bibliographies, which is quite helpful. Am I missing something? Thanks for any help.

Find more posts tagged with

Comments

JT (alabama24)

Not sure where to post this as I am running the latest beta.

The beta forum is the right place. Good job. [:)]

Maybe I am missing something here.

I have never done what you are doing... so I only have a guess.

The links to other resources don't "magically" appear... they have to be manually tagged. My <guess> is that the second screen shot shows a resource (Bock) which had NOT been added to the Logos catalog at the time. Since there wasn't a resource to link to, you don't see an active link. Once the resource gets tagging updates, you would then see the link.

NB.Mick

https://community.logos.com/discussion/comment/642146#Comment_642146

I think I remember that there is a longstanding bug in Logos getting the "below the line"-reference right in this kind of 'newfangled' references ('new' since introduced only some years back in Logos and IIRC not rolled out to the majority of all of its 40+k total resources). There was a thread - I think with Mark Barnes and myself involved - where Logos conceded as much, but I haven's seen any mentioning of it in any Release Notes, so they either are working on it, gave it up or put it on the backburner, maybe onto the list of "all the things we're going to fix once the 64bit engine runs smoothlessly".

EDIT: Google helped me: the thread I had in my mind is from summer 2013: https://community.logos.com/forums/t/73301.aspx and in Dec 2013 there was another thread where the bug was ackknowledged "without ETA". I think it has come up some rare times in between.