AudibleApi VS jellyfin-plugin-bookshelf

Thanks for including me :) I actually broke out Libation's Audible API into its own repo: https://github.com/rmcrackan/AudibleApi . You're welcome to use it yourself if you'd find it helpful. It's in nuget as AudibleApi . I collaborated heavily over the years with mkb79 who in my mind has the gold standard in audible api reverse engineering.

My local set up is a solution which references the projects from all 3 repos (1, 2, 3). I don't want to do nuget because debugging is a nightmare. I tried and failed to use submodules because I suck at git.

In case any value of the opf file is not parsed, you could create an issue about it here: https://github.com/jellyfin/jellyfin-plugin-bookshelf

You may want to create an issue about the title sort being ignored here. Thought I can't find anything related to a sort title in the specification. Is it perhaps something Calibre or some other tagging software added? Do you know how it looks like?

I haven't tried it out yet, but apparently Jellyfin has a book plugin that does books, comics, and audiobooks: https://github.com/jellyfin/jellyfin-plugin-bookshelf

E.g. metadata for books is handled in the bookshelf plugin (C#). You could look at already existing implementations (e.g. ComicBookInfo or the Epub provider for some easy things) and then implement your own. There are some open issues about missing book providers, but I would start with a file based provider first as look easier than online metadata providers.