|
I believe this is the expected behaviour. Calibre will always defer to the values found in the .opf file.
Personally I would like a way to disable that but I can see the arguments both ways. If you are restoring a corrupted database, then using the .opf file date sounds the "right" thing to do. There are probably other scenarios I haven't mentioned where it is seen as desirable.
If however you are moving stuff from one library to another for the purposes of a "fresh start" then it is unfortunately not what you want. Similarly if you are sharing your book with another family member's Calibre PC by preparing all the metadata, doing save to disk and letting them import it. They would rather have the date that *they* added it to their Calibre, not the date I added it to mine.
It doesn't just apply to date. It applies to custom column values as well. Say for instance I have a #read custom column, and I save to disk to share with my parents. I had to get them to rename their #read custom column to something else, because otherwise the data displayed for them is incorrect.
As I said I can see the behaviour being a blessing and a curse, it just would be nice to have an option for when adding books to ignore certain data. Yes I could just not export the opf file, but then my parents have to source all their metadata from scratch which is not desired.
|