Local folder hierarchy optimization
Describe your suggested feature
The current directory structure is /local/the series title/chapter/image. If there are nested folders within it, recognition will fail. For example, /local/the series title/folder /chapter/image will not be recognized, which is very unfriendly for classification. It is hoped that local image sources can freely access the folder hierarchy until they find the directory where the image is located.
Other details
No response
Acknowledgements
- [x] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
- [x] I have written a short but informative title.
- [x] I have updated the app to version 0.19.1.
- [x] I will fill out all of the requested information in this form.
If you're unsure how Local Source resolution works, here is our guide on the structure required: https://mihon.app/docs/guides/local-source/
如果您不确定本地源解析如何工作,请参阅我们关于所需结构的指南:https://mihon.app/docs/guides/local-source/
I've read this guide. My question isn't about how local source resolution works, but rather that it only supports /local/the series title/chapter/, which is inconvenient. If there are folders under /chapter, I'd like them to still be accessible, rather than displaying a missing image. I'm using translation software, so I apologize for any inaccuracies in my interpretation.
What do you need folders inside a chapter for? Mihon currently supports a structure like this:
Mihon/local/series title/chapter 123/[images here]
What use would folders inside the chapter folder be for you?
章节里需要文件夹做什么?Mihon 目前支持如下结构:
Mihon/local/series title/chapter 123/[images here]章节文件夹内的文件夹对您有什么用处?
First, it's better for categorization. "/local/author name/series title/chapter/image" allows you to keep all the works by the same author in one folder. If you have a lot of works, /local would be very cluttered. Second, it improves the reading experience. Some of the images I download are stored in a chaotic manner, so the /chapter folder might contain images, folders, and compressed files. If I want to read in mihon, I have to spend a lot of time adjusting the format.
Quick way to spiral out of control, next someone will want
local
|- Marvel
|- Crossover Arc
|- Hero A
|- chapters
|- Hero B
|- chapters
to show up as Crossover Arc because that makes sense for this specific organization they like. How should the app know which parts to ignore and which ones are the relevant Entry name and Chapters?
Quick way to spiral out of control, next someone will want
local |- Marvel |- Crossover Arc |- Hero A |- chapters |- Hero B |- chaptersto show up as Crossover Arc because that makes sense for this specific organization they like. How should the app know which parts to ignore and which ones are the relevant Entry name and Chapters?
Okay, I understand what you mean. My initial expectation was for users to be able to select a specific directory level for reading, much like a file manager. But that's obviously not feasible. The current mihon parsing logic is indeed simpler and clearer. Thank you for your response.
those are your files and folders, boss. you need to organize them, that is what file manager apps are made for and why one is pre-installed on the phone.
老板,这些都是您的文件和文件夹。您需要组织它们,这就是文件管理器应用程序的用途,也是为什么手机上预装了该文件管理器应用程序。
You misunderstood me. It's not that I don't know how to organize files. I just hope not to be limited to the third-level directory, because when I organize and classify, I may organize fourth-level and fifth-level folders. I hope to be able to access deeper folders in Mihon, that's all. However, they have answered clearly. This will make it easier for Mihon to identify projects. I understand very well. I will reorganize the file directory to adapt to Mihon.
While we can adapt our way to organize local folder around how Mihon works, I agree with @EtherealShen that at least another layer of folder will be nice. Since downloads folder has layer of source before series layer after all.
In my case I have hundreads of oneshots and a few dozen big series in my local folder. I would love to hae those two separate into two folders.
for one shots, one way i did is to combine the pages from its chapters into one .cbz as title for its filename, then the author as folder name to group them under. you can even add another layer, like year, to the folder, like toriyama (1980), toriyama (1990), etc.
Hello, there is a valid, in my opinion, use case to allow one level of nested folder: volumes.
I have some series where the structure is as follow:
Series title
cover.jpg
Volume 01 - vol 1 name
chapter_1.zip
chapter_2.zip
chapter_3.zip
Volume 02 - vol 2 name
chapter_4.zip
chapter_5.zip
chapter_6.zip
I'd like to keep that structure, especially for series that are several hundreds chapters long.
There's no need for Mihon to display the names of the volume folders in the app, just having Mihon be able to go one level deeper and display the chapters as if they were all at the top level would be enough.
If there's some interest in that feature, I'm willing to pull the code and see if I can send a pull request.
Thanks.