The calibredb command will write any out-of-date metadata.opf files, then exit. The files will be up to date when it finishes.Īdvanced idea: you might consider putting this command in a script that you use to start calibre so that the files written as soon as possible.

Run the calibre command line program 'calibredb backup_metadata'.

Leave calibre running until the metadata backup status says that it is finished.

You can avoid this problem by ensuring that calibre has finished writing the files in one of two ways:

You can see if calibre has finished by (in calibre) clicking the Library button, choosing 'Library Maintenance', then 'Library metadata backup status'. CC detects this possibility, notifies you, and then uses the possibly-incorrect values. If you exit calibre before it is finished writing the files then the values for the composite columns stored in old metadata.opf might not be correct.

Calibre writes these files while it is running at the rate of around 2 files per second. It is possible that the metadata.opf file is not up to date because when you change metadata for a book, calibre writes the metadata.opf files one-by-one. When you use the cloud connection to download a book or to look at a book's details, CC fetches the metadata.opf and reads the composite column values from that file. Because of this, CC cannot read these values from the database stored in the cloud.ĬC V5.0.3 and later: The values for composite columns are also stored by calibre in the 'metadata.opf' file saved with every book in the calibre library. Instead, calibre computes them when needed. The values for calibre custom columns 'built from other columns' ('composite' columns) are not stored in calibre's database.

Calibre companion app