Ok, so let me see if I have the workflow correct:
- I click and drag my epub(s) over Kepubify.
- I copy it over to my Kobo reader.
- I disconnect the device and let it scan.
- I reconnect the device and run seriesmeta.
Is that correct?
Questions:
- If I just want to update the books that don't have the series data set (i.e. it's set to NULL in the database), I'd use the 'n' switch, right? Mainly asking because I have some books converted by the previous version of kepubify on the reader that I haven't updated series data for yet.
- Does seriesmeta populate other fields too like ISBN (if present) and author? I use Calibre to manage my collection but Kepubify to do the conversion (because it's faster on the netbook I now use exclusively to house my collection) but I'm finding that if a book has multiple authors, the Kobo sometimes only picks up one of the authors, or if I delete some of the authors (ex. Calibre pulls down someone who writes a foreword or is an illustrator as an additional author), the Kobo will still pick up the deleted author and sometimes use it as the sole author instead (which means I have no idea where it's pulling it from; that data is supposed to be gone). It'd just be nice to not have to re-edit author data after the fact too.
- Can seriesmeta (and covergen) only target one book (or a few) if I give a path(s), or does it have to scan the entire reader? I do have a really large collection, so not having it scan the entire collection each time I add just a couple of books or need to correct/change the cover for one book because it didn't scan correctly would be nice and save a lot of time. It's why I just edit the database manually (but also to correct the author issue above so it'd need to be done anyway; although it just hit me: maybe the whole author thing is an epub3 issue? I haven't been paying attention to book format).
- Am I interpreting this right: any new books converted with the new version of kepubify no longer need to have seriesmeta run on it anymore? Let me guess: SQL triggers or something like that? If so, that's really cool.

Feature request: Since covergen is doing transformations on the image already, any chance for it to have the option to convert to greyscale too, just to save a bit of space?
Anyways, I love kepubify; thanks for making it!