Comic/Manga Support

[CuddleBear92]

This is an overview issue for multiple things needed to better support: Comics like Batman and Spider-Man. Manga like Naruto and One Piece.

• [ ] Comicvine Metadata Scraper ala https://github.com/cbanack/comic-vine-scraper - API

• [ ] New Comic specific Archive Directory option New version of this

• [ ] A new way to view only doujinshi and only comics/manga. Button at the top of the library to switch between the two?

• [ ] User rights for accessing Comics and Doujins so admin can choose what users has access too.

• [ ] Series view and Publisher views? Would need a folder type navigation system like /comics/publisher/series (year)/issue For example: /comics/DC Comics/Batman (2011)/Batman (2011) - #01.cbz

Would these things require or need a separate database file and thumbnail folders? could maybe be smart to split it into two things so there is no crossover. It would be wanted to have these things split apart as a whole so users without rights to say adult content wouldn't see it.

Guess a workaround to most of these would be to just have a new instance of the server in a docker container or something that is separate.

EDIT: things to replace: https://vaemendis.net/ubooquity/

[Difegue]

Thanks for all this -- I'll just mention that there's already a OPDS endpoint built into the server, although it's a bit outdated and doesn't show categories atm.

[CuddleBear92]

sounds good. editing that out. just did a double take and looked over the setting for it. might have missed it or something i guess.

[IceBreeze]

I'm also using LRR to manage manga and comics, because of the restrictions imposed by other projects on the filesystem organization.

So I wrote a small metadata plugin that works by reading metadata from a specific file in a folder and applying them to all the files that I put in that folder. This allow me to simply add files in a folder, usually named like "CAP-xxx.cbz" and "VOL-xxx.cbz", to have them tagged and sorted in LRR. The meta-file is in YAML, because it's easy to read and write.

It also has a way to associate specific tags to single files, so that I can easily manage things like "collabs" and "crossovers" that are a pain to manage in a strict hierarchical manner.

Then I use the "categories" to manage the collections in LRR (and I'm looking forward to see if the "meta-archives" can improve the experience).

I never thought of proposing it because it doesn't seem to fit with the original philosophy of the project, but maybe in this case could be of some use. Let me know :)

[ghost]

I'm also using LRR to manage manga and comics, because of the restrictions imposed by other projects on the filesystem organization.

So I wrote a small metadata plugin that works by reading metadata from a specific file in a folder and applying them to all the files that I put in that folder. This allow me to simply add files in a folder, usually named like "CAP-xxx.cbz" and "VOL-xxx.cbz", to have them tagged and sorted in LRR. The meta-file is in YAML, because it's easy to read and write.

It also has a way to associate specific tags to single files, so that I can easily manage things like "collabs" and "crossovers" that are a pain to manage in a strict hierarchical manner.

Then I use the "categories" to manage the collections in LRR (and I'm looking forward to see if the "meta-archives" can improve the experience).

I never thought of proposing it because it doesn't seem to fit with the original philosophy of the project, but maybe in this case could be of some use. Let me know :)

I would be very interested in this, I'm also here because of restrictions imposed by Other Projects to the filesystem organization. Also because of poor performance with large archives from Other Other Projects. LRR chewed through my 50,000 file, multiple directory archive like it was nothing. Komga and Ubooquity would still be chugging or melted through the chassis by now. And Kavita, while performant, has the issue with organization.

I think allowing the user to modify the filesystem organization is a fine idea. Either through a config file like you've done here with the YAML, or through a user interface allowing on a per library basis to set the filesystem organization by keyword, folder name, file name, metadata, whatever they want.

Would you mind sharing your plugin and YAML configuration?

And to the Dev, thank you so much for your work, I've been watching this project but only now tried it. I'm super impressed with the performance and over-all polish of the tool. I'm glad to see its in active development still as well.

[IceBreeze]

@CDarwin7 sorry for the late reply. I've uploded the plugin here with a simple, I hope, readme. Check it to see if it's what you expected.

[vuhe]

Is there any new progress on this issue?

I noticed that there is currently an unreleased feature called tankoubon.

If there is a metadata plugin that converts a folder into a tank and sets metadata information based on the metadata file (such as comic-info.yml), it should be able to solve the problem of managing comics.

[EfronC]

I think Tanks are still on a very early stage of integration, so whether they help with the issue will still have to wait.

On another note, with the way Tanks were desingned, I see possible that someone makes a plugin to take a folder that starts with, lets say, [TANK], and then create a Tank and fill it with all the files inside of it, but again, it would have to wait for Tanks to be ready for someone to create a plugin like that.