Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multi-Level Collections #1390

Closed
4 tasks done
KalbazJarak opened this issue Jan 10, 2024 · 5 comments
Closed
4 tasks done

Multi-Level Collections #1390

KalbazJarak opened this issue Jan 10, 2024 · 5 comments
Labels
consider Not sure yet if this makes sense or not

Comments

@KalbazJarak
Copy link

Describe your suggested feature

It would be useful to be able to define multi-level collections as a way to organise comics in a more granular way, something usually done without Komga using nested folders.

For example you could have collections like this:

  • Star Wars
    • Legends
      • New Republic
      • Movie Era
      • Post-Movies
    • Canon
      • Old Republic
      • New Republic
      • Movie Era
  • Hellboy Universe
    • Hellboy
      • Mainline
      • Short Stories
    • BPRD
      • Mainline
      • Historical
    • Witchfinder

For large libraries this allows more structured organisation without having to change the existing series folder reading logic to accommodate multi-level folder structures, though SQLite doesn't allow nested tables and I'm not great with databases so not sure what the best solution here would be.

Other details

No response

Acknowledgements

  • I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
  • I have written a short but informative title.
  • I have updated the app to the latest version.
  • I will fill out all of the requested information in this form.
@gotson
Copy link
Owner

gotson commented Jan 11, 2024

Just add that in the name ?

@gotson gotson added consider Not sure yet if this makes sense or not and removed triage labels Jan 11, 2024
@KalbazJarak
Copy link
Author

While that does technically categorise stuff it doesn't really work as effective navigation. Rather than having 20 top-line collections say on 1 page that you can narrow down by clicking through you just end up with 500 spread across 25 pages.

Maybe if you can remember everything you have in a giant library it sort of works but if you're sharing your library with multiple users it's not great UX.

@gotson
Copy link
Owner

gotson commented Jan 11, 2024

Maybe if you can remember everything you have in a giant library it sort of works but if you're sharing your library with multiple users it's not great UX.

that's where the search comes in handy :)

@KalbazJarak
Copy link
Author

But that's still making the assumption they roughly know what they want, that doesn't help if they're just browsing to look for new things. Sure if they're familiar with superheroes they can search Batman but publishers like Image or Boom put out loads of different stuff, so in that case you could make multi-level collections that go Publisher -> Genre, or the other way around, or sub-genres for them to flick through.

@Cantello
Copy link

Could be probably done with smart lists, tags & volumes, see #200.

Repository owner locked and limited conversation to collaborators Jun 4, 2024
@gotson gotson converted this issue into discussion #1544 Jun 4, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
consider Not sure yet if this makes sense or not
Projects
None yet
Development

No branches or pull requests

3 participants