Quote:
Originally Posted by June
I'm still curious about how the behavior of Calibre chnaged with 0.7.x - I've always used the tags field for organizing my collections via Calibre. And have never before encountered a case where it *overwrote* the existing collection (=tag) on the 505 without me changing the tag in Calibre library first and sending to device (or changing on the 505 via Calibre).
As far as I understand the explanation of the plugin behavior, the collections are created from specified locations (tag, series) if the book does *not* have a collection on the reader already.
All my books on the 505 were in collections, and had corresponding tags in the Calibre library, they'd been added via Calibre (0.6.5x). SO it shouldn't have overwritten the collections from the metadata, IMO. It did this immediately upon detecting the 505.
|
It is a bit hard to reconstruct the behavior of the earlier 0.7 versions, but here goes.
When calibre builds its metadata cache, it also builds collections using the specification in the device plugin. It gets this information from the books, not calibre's library, because it hasn't matched books to the library yet. Because of a bug, 0.7.1 ignored the device plugin specification and built collections for series and tags. This caused many people to have an explosion of collections.
If I remember correctly, the early versions of 0.7 (before 0.7.2) did not preserve or remember the hand-built collections. This exacerbated the problem with the collection explosion. Noticing and preserving hand-built collections was added to calibre, but because of the 1-character typo I mentioned in some post, people still couldn't edit them.
As of 0.7.4, people can edit the collections.
The situation today should be as follows:
- When a book is sent to the device. collections will be added for calibre metadata specified in the device plugin. Tags bracketed in [ ] characters will be ignored.
- User-defined collections, either from editing in calibre or somewhere else, are remembered.
- Collections are additive. Calibre will not delete a book from a collection. Assuming that collections are built from tags, changing the tags on a book and resending will add the book to collections built for any new tags, but will not delete the book from collections for tags that no longer are on the book.
- Calibre will not delete a collection unless all the books in the collection are deleted.
I see this behavior with my Sony 300.
After calibre has built its cache, collections will be built only for books added to the device. Again assuming collections built from tags, books already on the device and not sent again will not added to collections, even if they have the tags in calibre's db. The books on the device will not be scanned again unless the book is modified (the date on the book file changes).
I think collections now behave as expected. If someone disagrees, please let us know.