View Single Post
Old 10-25-2020, 12:29 AM   #1967
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by NiLuJe View Post
@davidfor: Because I'm an idiot, I hadn't saved the mangled metadata.calibre file, so I had to resort to some creative manual mangling to replicate my original data set, and, yeah, it seems to behave now, thanks .

----

Random jq query I used to double-check the metadata sanity:

Code:
jq '[.[] | { Series: .series, Index: .series_index }] | group_by(.Series)[] | sort_by(.Index) | unique' < /run/media/niluje/KOBOeReader/metadata.calibre
The calibre.metadata file shouldn't be an issue here. It should all be working from the database on the device, and the metadata in the calibre library. And it was really about the the series number being null in the. There were a couple of reasons that could happen, and the code in the driver and plugin were not checking it properly.
davidfor is offline