Looking for insight into my EPUB -> KFX workflow + some questions

[Magic815]

So I think I'm starting to get close to a workflow that works for me, in my effort of collecting EPUB eBooks and getting them onto my Kindle (in the KFX format). However, I have a few sticking points that I have questions about.

Here is my current workflow:
1. I add the eBook to Calibre (usually a retail EPUB)
2. I make sure the new book is highlighted/selected in the library list
3. I double-check the EPUB's eISBN inside the file and make sure the IDs metadata field is set appropriately. I then manually search that ISBN on Goodreads.com and Amazon.com, and I collect the GR ID and Amazon ASIN. My IDs metadata field ends up looking like: "isbn:xxxxx, amazon:yyyyy, goodreads:zzzzz" when I'm done
4. I use the download metadata feature inside 'edit metadata' to get the cover image and the rest of the metadata all set to how I like it
5. I run the 'Count Pages' plugin to populate my #pages and #gfog custom columns
6. I convert the book to KFX, using the 'KFX Output' plugin (and it sources the page count from the #pages custom column)
7. I connect my Kindle to my PC via USB, and use the 'WordDumb' plugin to generate X-ray and Word wise data for the book, and then it sends it all to the device. (I have a metadata plugboard set that modifies the title to "{series}{series_index:0>2s| #| – }{title}" on the send - so that books in a series sort by their series name/number)
8. As a bonus, I then convert the EPUB a second time to MOBI - in case I ever want to have the option of sending a book via Kindle email - as it's not possible to send the KFX over that way

Steps 1-7 nets me a KFX file that shows up on my Kindle with goodreads integration, page count info, x-ray and word wise data, and has a naming convention that sorts nicely on my Kindle. And step 8 gives me a back up MOBI file.


However, I have some questions:
1. If I have all my metadata, my cover picture, and my custom column information exactly how I want it and have no intention of changing it - I assume I can use the 'embed metadata' button to formally write all those changes that I made into the file itself?
2. If I run that 'embed metadata' command, it looks like it can apply to all three formats in my case (EPUB, KFX, and MOBI). Are all three formats able to actually hold all that adjusted metadata in the file? (I.e. everything on the 'basic metadata page - including the cover picture, and everything on the custom metadata page?)
3. Or would it be important for me to run the 'embed metadata' button BEFORE step 6 in my above workflow? I.e. Before I start making any other formats off of the original EPUB one?
4. Does the metadata plugboard come into play at all with the 'embed metadata' command? Or is the plugboard still only used when sending to device (or in my workflow, using 'WordDumb' to send to device)?

[jhowell]

Originally Posted by Magic815

8. As a bonus, I then convert the EPUB a second time to MOBI - in case I ever want to have the option of sending a book via Kindle email - as it's not possible to send the KFX over that way

The ability to send MOBI files via email is going to be removed by Amazon in August. You can now email EPUB instead.

Originally Posted by Magic815

1. If I have all my metadata, my cover picture, and my custom column information exactly how I want it and have no intention of changing it - I assume I can use the 'embed metadata' button to formally write all those changes that I made into the file itself?

Different ebook formats have varying support for metadata. For KFX the supported fields are: title, author, language, publisher, publication date, description, cover, and ASIN.

Originally Posted by Magic815

2. If I run that 'embed metadata' command, it looks like it can apply to all three formats in my case (EPUB, KFX, and MOBI). Are all three formats able to actually hold all that adjusted metadata in the file? (I.e. everything on the 'basic metadata page - including the cover picture, and everything on the custom metadata page?)

EPUB will hold the most metadata using extensions that are proprietary to calibre. KFX and MOBI are more limited.

Originally Posted by Magic815

3. Or would it be important for me to run the 'embed metadata' button BEFORE step 6 in my above workflow? I.e. Before I start making any other formats off of the original EPUB one?

It shouldn't make any difference.

Originally Posted by Magic815

4. Does the metadata plugboard come into play at all with the 'embed metadata' command? Or is the plugboard still only used when sending to device (or in my workflow, using 'WordDumb' to send to device)?

Embed metadata does not allow for transformation of the metadata. Metadata plugboards only apply when sending to a device or saving to disk.

[Magic815]

Originally Posted by jhowell

The ability to send MOBI files via email is going to be removed by Amazon in August. You can now email EPUB instead.

Different ebook formats have varying support for metadata. For KFX the supported fields are: title, author, language, publisher, publication date, description, cover, and ASIN.

EPUB will hold the most metadata using extensions that are proprietary to calibre. KFX and MOBI are more limited.

It shouldn't make any difference.

Embed metadata does not allow for transformation of the metadata. Metadata plugboards only apply when sending to a device or saving to disk.

Man, you've been helping me out all over this forum. Much appreciated!

Yea, I knew the MOBI thing was going away - but didn't realize EPUB was already here and working. It looks like amazon just converts it from EPUB to AZW3, when doing the email-to-Kindle method?

Thanks again for your help and insight.

[jhowell]

Originally Posted by Magic815

It looks like amazon just converts it from EPUB to AZW3, when doing the email-to-Kindle method?

Amazon uses their kindlegen app to generate both MOBI and KF8 (azw3). Most devices will receive the KF8 version, but those that do not support it get MOBI instead.

Glad I can help.