Thread: Aura Calibre resets new Collections created with the Kobo
View Single Post
Old 01-18-2018, 05:33 PM   #3
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 MicheleBS View Post
Dear Forum,

I usually make use of Calibre to manage my Kobo Aura One. I setted Calibre for it to be able to also create/delete/manage new Collections, associating them to the tags field. This is with lots of satisfaction.

But some days ago I created a new Collection in the Kobo, and I moved some of my .epubs there, from other old Collections already present. This was directly with the Kobo, not with Calibre: so, when I opened Calibre to manage my Library and add some books to Kobo, Calibre applied its own old Collection rules, and all went back to the previous state. The new Collection was deleted, and the books I added went back to the previous Collections.

How to make Calibre to accept new Collections created with Kobo, and not to force Kobo to the previous status?
All this is working as designed. The collection management done by the driver is pretty much an all or nothing thing. It works out what collections books should be in based on the calibre library and makes those changes. And that means that manual changes on the device will usually be lost. This is simple because there is no way (at least. no easy way) for the driver to know if the extra collection it finds on the device was created manually, or because the driver created it before but there have been changes in the library that mean the collection is no longer needed.

The driver does have an option to specify the names of collections that are to be ignored. This is a comma separated list of collections on the device that the driver is not to touch. If you do want a few manually managed collections, you need to add the names to this option.
davidfor is offline   Reply With Quote