Quote:
Originally Posted by jackie_w
Because I was specifically looking at user columns on the Details page I did spot one other anomaly. I used to have a user column called 'Test' which I removed from calibre a few months ago. However this column is still displaying for some books in CC. Can you explain why this column would still exist in CC? I see no sign of the column in the metadata.opf file for these books in calibre.
|
Quote:
Originally Posted by Purple Lady
I now have all my books on my new Nexus 7 LTE. I wanted all the same books that I had on my old Nexus 7 so I created a custom yes/no column and valued it as yes for all books on the old Nexus. I added all these books on my new Nexus using the wireless connection and it only took a few minutes for 400 books. I then went and updated the custom column to "no" so all the books had the last_mod date updated and then deleted the custom column. I then connected wirelessly to update the metadata, but the custom yes/no column is still in my book details. Is there a way to remove this? I have Calibre 1.2 and CC 3.1.1c
|
And again, thanks to both of you for persevering.
There is a bug in the calibre side that has been there for at least 2 years. In some cases the metadata sent to a device was the union (merge) of the correct metadata stored in calibre and the metadata already on the device. In this case, because the deleted columns were in the metadata coming from the device, calibre merged them back into the metadata that was sent back to the device, again and again. And they rode forever 'neath the streets of Boston ...
This will be fixed in calibre 1.4. (It is in the source now.) Correcting the metadata in CC will require that calibre send the book's metadata to CC, which will require that the last_mod times be updated.
The only other way I can think of to fix it is to resend the book. That should send new, correct, metadata to CC without the incorrect merge step being applied.