Quote:
Originally Posted by NiLuJe
@jangell2: CM's import will *never* delete a collection, so, if you ran the import after each tweak, that would explain the book in two collections thing.
As for the the other one, the exact metadata involved would help pinpoint the issue. But I'd expect it's the same kind of thing than the first one, a remnant of the first bogus sync, and since CM never deletes collections, you've just noticed the stray 'broken' one.
|
The CM import never deletes a collection? If on Calibre I were to zero out the customs collections column for a particular collection, generate the collections via the plug-in, and than import using CM, would I have a collection with zero books in it? If I were to change the custom collection column for a book to another collections and than repeat the above process, would the book be moved to the other collection?
I'm thinking what I have to do is to delete both of these problem collections using CM, then create the collections using the plug-in, then import using CM. Does that sound like something that will fix the problem.
BTW, when deleting a collecting using CM, that only deletes the collections and not the books in it?