Open lramirez925 opened 9 months ago
Definitely a good idea! Komga would definitely work this way too, but Kavita is a bit weird in regards to Folder-structure and Filenames. https://wiki.kavitareader.com/en/guides/managing-your-files/scanner#file-layout https://wiki.kavitareader.com/en/guides/managing-your-files/manga
Yea I definitely have my troubles with kavitas system for how it needs organized at the file system level. But I do prefer to keep my files a bit more organized with more sub folders. I appreciate the acceptance of the feature
I think the API side is already ready for custom save locations and I plan to implement this on the website side soon(TM) so at the very least this could be done manually, but I agree it would be a little tiresome to do for each manga. One potential roadblock I see is that not all sites have a publisher/scanlation so there would need to be some sort of fallback if one of the fields can't be determined.
Can you point to documentation for the api to do this? I am already writing my own UI to encompass a bunch of things I need to do with my collection that the various tools fall short of. And was planning to just include job info on my front end vs using the tranga site itself.
Sorry for the late reply, there isn't any documentation as such but if you find the piece of code that relates to adding a new manga to your library for the first time, there is a field which let's you specify the folder. Glax has done a good job keeping all the code readable so while even I'm not familiar with C# I can figure out what stuff does most of the time.
Probably gonna be related: #220
Anyway we can do custom naming schemas? Would really like to organize files into a sub folder. Instead of {mangaFolder}/{manganame}/{generated name}.cbz
Would be nice to use some of the metadata available to put them into a sub folder such as {mangaFolder}/{provider}/{publisher/scanlation}/{mangaName}/{fileNamedByTemplate}.cbz