starred/audiobookshelf

Fork 0

mirror of https://github.com/advplyr/audiobookshelf.git synced 2026-03-02 22:46:56 -05:00

[Enhancement]: When sorting in "Date Added Desc Order" included Series "added date" should be the date the last book was added to Series #2946

New issue

Open

opened 2026-02-20 03:03:12 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-20 03:03:12 -05:00

Owner

Originally created by @classicspam on GitHub (May 13, 2025).

Type of Enhancement

None

Describe the Feature/Enhancement

When sorting by added date desc the series date should be the date the last book was added to the series.

Also I am not sure if this is a front end thing or a backend thing and if the Mobile app would be separate from this request (i.e. if it is a backend api request ordering thing then the mobile app may "inherit" the changes)

Why would this be helpful?

So that books added to Series do not get "Lost" when sorting the book list by date added in desc order (with collapse series toggle on) (or even the recently added series list on the homepage) . By "Lost" I mean that if a book was added to the series then the Series should be considered as recently added to and thus the series "date" should be the date of the last book added to the series if you sort the series in any desc order by date.

Future Implementation (Screenshot)

Book Screen:

collapse series off:

collapse series on:

Home Screen:

Audiobookshelf Server Version

v2.21.0

Current Implementation (Screenshot)

No response

Originally created by @classicspam on GitHub (May 13, 2025). ### Type of Enhancement None ### Describe the Feature/Enhancement When sorting by added date desc the series date should be the date the last book was added to the series. Also I am not sure if this is a front end thing or a backend thing and if the Mobile app would be separate from this request (i.e. if it is a backend api request ordering thing then the mobile app may "inherit" the changes) ### Why would this be helpful? So that books added to Series do not get "Lost" when sorting the book list by date added in desc order (with collapse series toggle on) (or even the recently added series list on the homepage) . By "Lost" I mean that if a book was added to the series then the Series should be considered as recently added to and thus the series "date" should be the date of the last book added to the series if you sort the series in any desc order by date. ### Future Implementation (Screenshot) Book Screen: collapse series off: ![Image](https://github.com/user-attachments/assets/85cfe6ec-aefe-41b9-af69-05f109e27aeb) collapse series on: ![Image](https://github.com/user-attachments/assets/3ddfba71-d1dc-4460-8a53-f6f378984d17) Home Screen: ![Image](https://github.com/user-attachments/assets/d655f96e-0227-405f-aca1-25ec078f2a49) ### Audiobookshelf Server Version v2.21.0 ### Current Implementation (Screenshot) _No response_

deekerman added the

enhancement

label

2026-02-20 03:03:12 -05:00

deekerman commented

2026-02-20 03:03:13 -05:00

Author

Owner

@advplyr commented on GitHub (May 13, 2025):

I think collapse series and recently added series on the home page are different.

With collapse series I can see the case for using the added at date of the most recently added book.
However, I never liked how collapse series is handled because we are showing the first book in the series cover image, so to see that book cover image but see data from another book underneath it doesn't seem right.

There are a bunch of open issues on handling collapse series sorting. With the way the data model is structured collapse series is difficult to work with. Early on when I implemented collapse series everything was loaded in memory on server init and the sorting was easy, but now we have to write sqlite queries that pull all the information sorted/filtered and paginated.

@advplyr commented on GitHub (May 13, 2025): I think collapse series and recently added series on the home page are different. With collapse series I can see the case for using the added at date of the most recently added book. However, I never liked how collapse series is handled because we are showing the first book in the series cover image, so to see that book cover image but see data from another book underneath it doesn't seem right. There are a bunch of open issues on handling collapse series sorting. With the way the data model is structured collapse series is difficult to work with. Early on when I implemented collapse series everything was loaded in memory on server init and the sorting was easy, but now we have to write sqlite queries that pull all the information sorted/filtered and paginated.

deekerman commented

2026-02-20 03:03:14 -05:00

Author

Owner

@advplyr commented on GitHub (May 13, 2025):

Some related issues #1592 #1074 #3432 #957

There are a bunch of other collapse series related issues. It probably deserves its own tag.

@advplyr commented on GitHub (May 13, 2025): Some related issues #1592 #1074 #3432 #957 There are a bunch of other collapse series related issues. It probably deserves its own tag.

deekerman commented

2026-02-20 03:03:14 -05:00

Author

Owner

@classicspam commented on GitHub (May 13, 2025):

Yeah the two probably are different and the original intent of the request was the book date added sorting screen, however as I was writing it I thought about the home screen recent series and sort of just piggy backed it on the request...

@classicspam commented on GitHub (May 13, 2025): Yeah the two probably are different and the original intent of the request was the book date added sorting screen, however as I was writing it I thought about the home screen recent series and sort of just piggy backed it on the request...