Bug: 4.3 Beta 7: Prioritized commentary collection has "0 volumes"

I just noticed this today, but it must have been this way for some time. I've had Believer's Church Bible Commentary in my Library for several years, and it has been prioritized (as a whole set) in my Library for almost as long as I've had Logos 4. Today I noticed that the label for it in my prioritization list says "0 volumes" even though I have all 19 volumes of it and they're prioritized as a series (title is boldfaced in Prioritization pane):

And indeed it doesn't come up in my passage guides. I can fix it by deleting this entry and re-prioritizing it, but a bug exists somewhere -- how did it get into this situation in the first place? Unfortunately I don't have logs of everything I've been doing since I prioritized that series. And perhaps today's log won't show enough to let you track down the problem, but I felt obligated to report it anyway in case you can figure out this puzzle.

Log file: 6136.Logos4.log

Find more posts tagged with

Comments

NetworkGeek

Interesting! Just checked my prioritized commentary collections, and they are all ok.

Jack Caviness

Today I noticed that the label for it in my prioritization list says "0 volumes" even though I have all 19 volumes of it and they're prioritized as a series (title is boldfaced in Prioritization pane):

Mine shows 19 volumes, but I had not prioritized the series prior to reading your question. I'll see what it looks like in a few days.

Graham Criddle

https://community.logos.com/discussion/comment/258058#Comment_258058

Mine has been prioritised for some time and shows all 19 volumes

Martin Folley

I had this happen back in November 2009. At the time, Phil Spitzer replied that

"I've had this happen before too. I believe it was because I changed one of the resource names in the series. A beta release was do out the same day so I waited for the release before reporting it. I thought I tested to see if it had been fixed but maybe I hadn't. At any rate, adding the series back fixed it for me"

It seemed to relate to the series meta data being changes at some point after the resource was prioritised resulting in the breaking of the link between the priority list and the actual resources.

Dragging the resource/series across again into the priority list cured it.

Todd Phillips

And indeed it doesn't come up in my passage guides. I can fix it by deleting this entry and re-prioritizing it, but a bug exists somewhere -- how did it get into this situation in the first place?

This happened to me in the past when a metadata update changed the Series title. If you could show the Series column in your library, I bet it's different from the entry in the prioritization list. I noticed the titles of those volumes has "Believers" without an apostrophe, whereas the entry in the list has an apostrophe. I wonder if the Series column now agrees with the titles.

EDIT: I see in my library there is no apostrophe in the Series name. So you must have priorizited it before it was changed.

Rosie Perera

https://community.logos.com/discussion/comment/258082#Comment_258082

And indeed it doesn't come up in my passage guides. I can fix it by deleting this entry and re-prioritizing it, but a bug exists somewhere -- how did it get into this situation in the first place?

This happened to me in the past when a metadata update changed the Series title. If you could show the Series column in your library, I bet it's different from the entry in the prioritization list. I noticed the titles of those volumes has "Believers" without an apostrophe, whereas the entry in the list has an apostrophe. I wonder if the Series column now agrees with the titles.

EDIT: I see in my library there is no apostrophe in the Series name. So you must have priorizited it before it was changed.

Aha, that is the culprit. Thanks guys for helping me track this bug down. Yes, the series name has no apostrophe, but the name in my prioritization list has the apostrophe. That still is something that shouldn't happen. I'm surprised that the prioritization list keeps track of what's in it by textual means. Usually they have unchanging internal IDs for everything, so if the name of the series changes with a metadata update, the name should get automatically updated in my prioritization list without me having to remove and replace that series. I would submit that this is the essence of the bug.