The "Prioritize This Series" Option Doesn't Work
When I select certain commentaries and try to "Prioritize This Series" (right click on resource from Library view), the series is not added to the list of prioritized resources. Some are added successfully, but most are not. Can you help me figure out why? I would like to make sure I don't overlook a commentary in research.
Note: I also downloaded the resources.
Comments
-
When I select certain commentaries and try to "Prioritize This Series" (right click on resource from Library view), the series is not added to the list of prioritized resources. Some are added successfully, but most are not. Can you help me figure out why?
I just tried to verify this, using the NAC commentary series - the "prioritize this series" button put the series into the prio-list for me, but at the bottom of the list. Which series don't work for you?
Have joy in the Lord!
0 -
Thanks for the help! I was successful with the EBC and PNTC commentary series, but not with WBC, HNTC, Pulpit, Lexham Geographic, or R.C. Sproul Exposition.
0 -
Thanks for the help! I was successful with the EBC and PNTC commentary series, but not with WBC
I tried WBC and it worked, i.e. put it at the bottom of the prio-list if it wasn't in there before. Actually I normally just drag a commentary into the list, since the series will automatically used when a commentary is part of a series. Does this workaround work for you?
Have joy in the Lord!
0 -
Interesting. Did it put the series into the list or just the single resource? I can add single resources, but the series functionality doesn't seem to work.
I wonder if Logos has not categorized these as 'commentaries.' In addition to the series not being added to the prio-list, I just realized these same resources are not showing up under 'parallel resources' or in the passage guide under the 'commentaries' section.
My goal is to get these to appear in parallel resources so that I can easily check which commentaries I have available; right now they're hidden until I search through my library.
0 -
I wonder if Logos has not categorized these as 'commentaries.' In addition to the series not being added to the prio-list, I just realized these same resources are not showing up under 'parallel resources' or in the passage guide under the 'commentaries' section.
This sounds very strange. To help us work out what is going on, please post a screeshot (use the paperclip icon in the forum editor) to show what you have in your library for the WBC series - use the filter "word biblical commentary"
0 -
-
You can see I was able to add one volume from WBC, but not the series (like the others in bold). Also odd is that only one volume from PNTC is included in that series on the prio-list (I have the full set in my library).
0 -
Interesting. Did it put the series into the list or just the single resource? I can add single resources, but the series functionality doesn't seem to work.
As series (bolded entry, number of resources). I support Graham's suggestion that you show a screenshot from your library - please include the column with the series field: if this was changed, the functionality can't work.
Have joy in the Lord!
0 -
-
I'm on Logos Desktop for Mac
It is possible that is relevant - I'm currently testing this on Windows and it works fine.
Your screenshots show that all the descriptive information seems to be correct - series name and type of resource.
What happens if, instead of using the right-click option, you simply drag one of the resources to the place where you want that series to appear on the prioritisation list? Does the individual resource get placed there or the series?
0 -
I've attached a couple more screenshots of my library with the 'Series' column (I haven't changed it on any of them). I'm on Logos Desktop for Mac, if that helps.
Strange - especially since as per your screenshot, Logos prioritized the Pillar series only with one volume. Can't speak to Mac functionality - but maybe http://wiki.logos.com/diagnostic_logging may help, if executing the command runs into some errors.
Have joy in the Lord!
0 -
Hm, dragging places only the individual resource, not the series.
I'm reading through the diagnostic logging stuff. Some of these are new (bought this morning with the Matchups sale), and I've already restarted Logos more than once but I haven't restarted my computer. Going to try that and will follow up shortly.
0 -
The issue is resolved now, though I still don't know exactly what caused it.
It seems like the workaround is to restart your computer after purchasing new resources, and then restart Logos after downloading them (or purchase and download, then restart your computer to kill two birds with one stone).
The resources can be added to prio-list after the computer is restarted, and the number in prio-list reflects the number of downloaded resources in the series when Logos is started (Logos restart is required to update the number if additional resources are downloaded).
Now the commentaries are showing up in parallel resources and in passage guide / commentaries, just like they should be. Everything seems to be working great.
Sorry for not mentioning the new purchases sooner; I didn't think that was the issue. The diagnostic logging suggestion "Tip: Some issues go away after restarting Mac" did the trick. Haha, so basic, but unexpected in this case.
Thank you both for your help today!
0 -
Glad it is working
And thanks for sharing what you found out.
0 -
Sure thing. One more observation is that you have to download at least one resource from a series before the series can be added to the prio-list.
0 -
Hm, dragging places only the individual resource, not the series.
I'm reading through the diagnostic logging stuff. Some of these are new (bought this morning with the Matchups sale), and I've already restarted Logos more than once but I haven't restarted my computer. Going to try that and will follow up shortly.
Hi Josiah,
I suspect that your library was still indexing. Also, there is a known issue that sometimes requires a restart of the application for the prioritization list to get updated. This bug was fixed in 9.12, so it should be fixed for you in the future.
0