View Single Post
Old 06-16-2022, 02:52 AM   #30
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by BetterRed View Post
I can't see a last_modified date element in the book metadata,opf file. So, what is the database last_modified value compared against to trigger the write of a fresh book data metadata.opf file?

I added 'calibre' as a tag to the Quick Start Guide at 2022-06-16 15:05:54, but I can't see anything like that date in the .opf.

Attachment 194397

Its not the file system date_modified either. I changed that to 2022-07-16, and then added another tag - and a fresh opf file was written.

Attachment 194398

BR
I have never looked for the last modified date in the OPF. And with the way calibre handles it, it would make no sense. If you needed to use these to rebuild your library, the last modified date would be set to the current time. Or when the book was added to the rebuild library.

But, that wasn't really what I was meaning. Triggering writing of the OPF is done when the metadata is change. The data gets marked as "dirty", the modified time is updated and then the book is put into the queue for the backup. If you do a lot of changes quickly, such as changing a common tag, you can see the the last thing happening in the "Library metadata backup status" under "Library Maintenance". That shows how many are to be written.
davidfor is offline   Reply With Quote