Support for Read Lists

[thatdanguy10]

Describe the solution you'd like
I see there's already been a feature request for Collections like Komga has, but could there also be a function added for read lists? Have it simply give the ability to add a single or multiple books to a new or existing read list and be able to sort items within the list. A lot of times I follow a specific reading order while reading comics that requires jumping around a bunch of different volumes, so being able to pre-add them to a single list would do wonders.

Given there's a lot of unofficial reading orders out there as well, being able to export/import reading lists would also be amazing so these types of reading orders can be shared.

Additional context
More details of the Komga functionality can be found here: https://komga.org/docs/guides/readlists

[Casvt]

Given there's a lot of unofficial reading orders out there as well, being able to export/import reading lists would also be amazing so these types of reading orders can be shared.

Is issue #215 exactly referring to the importing part of the feature that you're requesting? If so, that issue can be closed as it then falls under this larger request.

In general, how does a reading list differ from a collection? They're both groupings of issues (and potentially entire volumes) in a certain order with the idea that you read them in that order to cover a complete storyline/storyarc. So except for exporting to an apparent '.cbl' file instead of setting the SeriesGroup metadata field, what's the difference?

Additionally, we have the Story Arc feature (adding ComicVine story arcs and downloading them just like volumes). So we (will) have CV story arcs, collections and reading lists. These all sound like practically the same thing with massive overlap in functionality. Can't we just combine them all? A collection is just an ordered grouping of issues. A CV story arc can just be treated as a collection where we keep the contents in sync with what's on CV. An .cbl import is similar to adding a CV story arc except for Kapowarr keeping the cbl file in sync. And we can export the collection to either a cbl file or by setting the metadata field.

[thatdanguy10]

Now that I think about it, I guess having collections separate from reading lists are probably really only critical for a program that also acts as a reader. To me, I would think in that situation, a collection would be something permanent that wouldn't change once set whereas reading lists would be temporary and dynamically change as you're reading the files (i.e., tracking). But provided everything you stated in your post it does seem like the intent may already be captured.