LC Classification not showing any books for top two levels
Talk Bug Collectors
Join LibraryThing to post.
1timcarlson
When I sort by LC Classification in "Your books" or in the Zeitgeist, it shows for the top two levels of Classification (ie: for G and GV, but not for GV1-1860) an error message such as ""G" is an invalid Library of Congress Classification" and does not display the books for it (see links below). In "Your books" when sorting by LC Classification and clicking on one of the letters, even if said letter should have hundreds of books in my collection that will display when clicking on it, it will say "No books found." This also applies for the top two levels.
I have tried accessing these pages on a different browser, device, day, and network, as well as logged out, and have verified that the issue persists across everything I have tried for the past week or so. I had previously assumed this was a validation issue in the LCC related to the processing occurring for bug 376317 since 12/30 and thought it would be resolved on its own or reported by someone else, but I am now reporting it here just in case this issue was not previously known about internally.
Links that show this issue in Zeitgeist:
https://www.librarything.com/lcc/G
https://www.librarything.com/lcc/GV
Links that do not:
https://www.librarything.com/lcc/GV1-1860
I have tried accessing these pages on a different browser, device, day, and network, as well as logged out, and have verified that the issue persists across everything I have tried for the past week or so. I had previously assumed this was a validation issue in the LCC related to the processing occurring for bug 376317 since 12/30 and thought it would be resolved on its own or reported by someone else, but I am now reporting it here just in case this issue was not previously known about internally.
Links that show this issue in Zeitgeist:
https://www.librarything.com/lcc/G
https://www.librarything.com/lcc/GV
Links that do not:
https://www.librarything.com/lcc/GV1-1860
2Nevov
Some supplementary things could do with a fix too: the Invalid LCC error message on the above links, states "Found out more." as a link, which would want to be "Find out more.", and at the minute doesn't lead to anywhere helpful in any case.
3kristilabrie
Verified, and letting the developers know about this one. (I think this is for @timspalding, but double-checking.)
4AbigailAdams26
I've received a report via email from another member, regarding the LC sub-page in Your books, with the same results mentioned by the OP. I have confirmed this in my own catalog as well. Clicking on any of the levels of classification, whether Top or Secondary, results in a blank page within the catalog, and the message that "No books are found."
5tidybookshelf
I am still seeing this issue, it's been about 5 weeks now.
6kristilabrie
I've reminded @timspalding about this one, thanks for your patience.
7mzonderm
I got the same message today when trying to get into the Js. "Found out more" goes nowhere.
On the other hand, going directly to https://www.librarything.com/lcc/JC348-497 worked.
On the other hand, going directly to https://www.librarything.com/lcc/JC348-497 worked.
8kristilabrie
Thanks for the reminder, pinging @timspalding about this one.
9tidybookshelf
I'm still seeing this issue, I've got screenshots I can share if that helps!
10timspalding
Fixed.
11LeslieWx
>10 timspalding: Hooray, Hooray! Thank you 😄
12Nevov
The invalid LCC error message/"Found out more" could still use a bit of a fix.
For example visible at: https://www.librarything.com/lcc/1860
"1860" is an invalid Library of Congress Classification. Found out more. (link doesn't lead to anywhere helpful)
Can submit as a separate report if you'd prefer.
For example visible at: https://www.librarything.com/lcc/1860
"1860" is an invalid Library of Congress Classification. Found out more. (link doesn't lead to anywhere helpful)
Can submit as a separate report if you'd prefer.
13kristilabrie
>12 Nevov: If you could add a new report, I think that would be helpful. Thank you!
15kristilabrie
Thanks!
16tidybookshelf
Unfortunately this is still not fixed on my end - here are some screenshots showing what's been happening since December!
17kristilabrie
>16 tidybookshelf: Ah, okay, we should draw up a separate bug report for that use case. I'll do that shortly and reference it here.

