Quote:
Originally Posted by otta56
Thank you for the advice. I did manage to get the books in separate folders on the device but all of the metadata is still stored in the "metadata.calibre" file at the root of the device rather than in the separate book folders as a "metadata.opf" file.
Is the creation of the "metadata.opf" file controlled by any of the template scripting language? I was not able to find a term or syntax in the "send to device" template.
|
As the others have said, the ereader apps or devices should be getting the metadata from the actual books. The "metadata.opf" is put there by calibre for its own use. It is there to make it quicker for calibre when connecting to the device the next time. I know that KOReader can use "metadata.opf" as the source of the metadata, but, it knows how to parse the file. I don't know of any other app or device that uses it.
And for the record, the "metadata.opf" is in JSON format. The attribute names are names used by calibre. Generally, they match the lookup name used in calibre. The custom columns are a more complex as they include the definition for calibre to load them.