> There's no good reason for any folder structure to hobble a media browsing frontend. Sure, but what I'm saying is that it was a price I was willing to pay. I

> There's no good reason for any folder structure to hobble a media browsing frontend. Sure, but what I'm saying is that it was a price I was willing to pay. I tried a lot of other media browsing software and they just didn't meet my needs like Jellyfin did. Could Jellyfin be more flexible? Sure. Does it need to be for me? Not at the moment. I'm getting the benefit right away, and might stand to get more benefit in future if it becomes more flexible on path/filename parsing. > a number of those frontends have an option that's basically one book per folder Jellyfin already supports that, but currently only for movies. Seems entirely possible it could do that for books or TV episodes too, if someone volunteers the time to land the server and UI changes for it. > When the Jellyfin UI reflects those nested folders, I can tell it to only rescan a specific subfolder when I add a movie, rather than checking the whole library for new content. Jellyfin supports realtime monitoring with inotify so it can see new/updated files as you add them, but this depends on the filesystem supporting it, and also I think it still has a bug where doesn't work on library directory paths that are symlinks. Jellyfin supports nested folders (Books, Music Videos and Other library types support a folder view), but their limitations are apparent: no homogenous filtering/sorting display, and for Music Videos and Other, no metadata collection.