Quote:
Originally Posted by ZodWallop
I likely left it the same way. I checked Extended, but not Tools.
But if I left it as *Any Device then I wouldn't have to reset it to match my reset Kobo, would I?
|
Sorry, but people are mixing things up. The configuration @DNSB referred to in the Kobo Utilities plugin has nothing to do with the driver. It is used purely within the plugin and is not used in any way by the two functions that have anything to do with collections. And those two functions are completely unrelated to any issues you are having with collections. @mathil's suggestion to use the Kobo Utilities to remove collections is completely wrong as there is no function in the plugin to do that.
Unfortunately, I haven't had time to discuss this due to work issues (I wish people would stop breaking things, blaming me and then being surprised when I demonstrate quite clearly that it was broken somewhere completely outside my control).
From what I can see, the suggestions made for handling this have either been pointless, or may make things worse. These include:
Running the "Update cached metadata on device". This is pointless. It is the same as the "Send metadata to device" job that is run when the device is connected, or you send a book to the device or you delete a book from the device. The only reason to run it is if you need to manually match books on the device to books in the library. After that you should run it as it will update the "metadata.calibre" file on the device for calibre to use later.
Deleting and sending books to the device is almost pointless. The collection management does not differentiate between books on the device and books being sent for the first time. It will act in the same way. If it is working, it is working. The only reason to consider it is if calibre has not matched the books on the device to books in the library. And then it is only going to be useful if the metadata in the books has changed significantly, or you want to change how the files are arranged on the drive.
Removing all collections and starting again. This is a problem because firstly, the only way to do it is to fiddle with your collection management configuration in calibre and let it do its thing, which apparently it isn't, or manually doing it on the device (after disabling collection management in calibre) or one of the apps and then syncing. After that you need to recreate the collections somehow. Which means putting the configuration back in calibre and letting it do its stuff.
From where I am sitting, this is hard to debug, because it is working for me. I have checked several of my devices and any changes I make in the collections via calibre are on the device when I look. That means new books appearing in collections, and books being moved between collections as intended.
Validating the calibre configuration is the first thing to do. Are the collection management options set in the driver? Do you have the correct driver configured? On the "Sending books to devices" page, is the "Metadata management" option set to automatic?
When connected, are the books showing as on the device?
On the device, can you add books to a collection? Does it survive a connection to the device and calibre? Does it survive a restart?
It shouldn't be a calibre issue, but, seeing a debug log from the connection would help to eliminate that. From it, I can see what happened and whether calibre thinks it did something or not. If you can produce one, either post it or upload it somewhere and PM me the link.