Quote:
Originally Posted by jhowell
KFX format as produced by Amazon has only a limited set of metadata. Kindles do not need anything else.
I am reluctant to define my own new metadata fields for KFX beyond what Amazon uses. I cannot be sure how Kindles would react to that unexpected data. Even if it appeared to work for now, Amazon is always making changes to KFX and something might break later.
|
I see, fair enough. So if I have a metadata plugboard that writes the series and series_index fields into the file's title when sending to device - I'm guessing Calibre uses it's dB to complete the plugboard, since the KFX file itself does not contain that info directly?
In my scenario, I'm hosting my library via calibre-web so that I can grab my files remotely, if needed. Initially, I was thinking I would just grab the KFX files, since all the work in generating it was already done on my local Calibre install. But I'm realizing that if I intend to make use of a metadata plugboard like that on the remote machine, I'd have to first bring over an EPUB file with full metadata embedded, right? (Or find some other way to have the complete metadata in that remote Calibre dB?)
Side question (and sorry for hitting you with all these, but you've been super helpful): What happens if I bring an EPUB file with it's metadata embedded (including custom metadata: #pages, #gfog) into a new Calibre library instance on another machine that doesn't have those custom columns set up? Is the #page and #gfog data still safe and maintained? Is there an easy way to have Calibre add-back missing columns in a new instance, based on custom file metadata?