View Single Post
Old 09-16-2016, 10:45 AM   #10
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 jiembe View Post
About "The second time you connect the Kobo to Calibre, Calibre automatically sends the series information, you don't need to do anything or force the update of the metadata of the book". This doesn't happened in my case.
In that case, you probably don't have the "Metadata management" set to automatic on the "Sending books to devices" page of the calibre preferences. Or you haven't selected the "Set Series information" in the driver configuration. If you have both set and it isn't updating the series info when you connect, then something is wrong. Running in debug mode and posting the debug log as I suggested before would let me try and work out what is wrong.
Quote:
But since my first post I found a workaround using the Calibre's plugin Kobo Utilities. This plugin allows to update the metadata you to choose for one or more books lying in the Kobo without touching the composition of the collections.
Personally, I don't consider that to be a workaround. It is an alternate way of achieving the same result. Plus a lot more.

And if calibre is touching with your collections on the device, it is either because you have configured the driver to do so, or there is a bug. I there is any chance of the latter, I need a debug log to look at to fix it.
davidfor is offline   Reply With Quote