Here's how I do it, although I'll admit my system is tailored to my workflow and may not be particularly good for yours.
First, I use one book per chapter rather than one book per volume in order to keep the file sizes down as well as track chapter titles. I previously used CBC files for each volume so I could have a table of contents, but CBC isn't widely supported and it took forever to open some of those big files in the Calibre viewer, so I changed how I'm doing it.
Title: Some Random Manga, Chapter 001
Series: Some Random Manga [1]
Path (Custom field): Manga.Some Random Manga.v001
Chapter Title (Custom field): Name of the chapter
Note that the Path field is hierarchical, so I can use the tag browser to navigate between the volumes.
Also note that I have the View Manager plugin set up with a "Path" view that's sorted on Path, Series, Title.
My method works fine if you're always going to use Calibre to read your manga (even if you use an external viewer), or use Save to Disk to export them into a hierarchical file system. I include the custom Path field in every one of my libraries for just that purpose.
It's not so good if you're going to Send to Device, most notably because the volume doesn't get its own field, making it more difficult to extract with a plugboard.
It also doesn't allow for a Volume title, although you could append one to the end of the Path field if you wanted.
For a volume-based system rather than a chapter-based system, the one proposed by theducks is probably much better.
|