starred/audiobookshelf
1
0
Fork 0
mirror of https://github.com/advplyr/audiobookshelf.git synced 2026-05-30 23:40:40 +02:00
Code Issues 1.0k Packages Projects Releases 10 Wiki Activity

[Enhancement]: RSS Audiobook list order management #2091

New Issue
Closed
opened 2026-04-25 00:03:23 +02:00 by adam · 3 comments
adam commented 2026-04-25 00:03:23 +02:00
Owner
Copy Link
Copy Source

Originally created by @noahkiss on GitHub (Jul 8, 2024).

Type of Enhancement

Server Backend

Describe the Feature/Enhancement

Currently, Audiobook RSS feeds sort based on the date/time the book was added to ABS. ABS correctly sorts the books by order when creating the RSS feed, but most clients use pubDate to sort items. This means that users are unable to edit the order of their RSS feeds, as "Date Added" is not exposed as an editable field in the client.

Instead, collection/series order should be used by default, where the first item in a collection/series is assigned the oldest pubDate (so that new additions are added as the newest episodes). The easiest way to accomplish this would be to assign fake sequential dates to sort the RSS feeds.

The date should probably also leave room for adding mid-series books without needing to change the already existing items' dates, ex. always start at year 2020 and use increments of 10 days for the series to allow for numbers like series #4.5 (gets assigned the 45th day in 2020).

A further enhancement could be a "sort" drop-down when opening a feed, then using the pubDate to sort based on the criteria the user selects.

Why would this be helpful?

This would allow users to have control over the sorting of RSS feeds and more easily find the next book in a series or collection.

Future Implementation (Screenshot)

Screenshot 2024-07-08 at 11 59 11 AM

Audiobookshelf Server Version

v2.11.0

Current Implementation (Screenshot)

No response

Originally created by @noahkiss on GitHub (Jul 8, 2024). ### Type of Enhancement Server Backend ### Describe the Feature/Enhancement Currently, Audiobook RSS feeds sort based on the date/time the book was added to ABS. ABS correctly sorts the books by order when creating the RSS feed, but most clients use pubDate to sort items. This means that users are unable to edit the order of their RSS feeds, as "Date Added" is not exposed as an editable field in the client. Instead, collection/series order should be used by default, where the first item in a collection/series is assigned the oldest pubDate (so that new additions are added as the newest episodes). The easiest way to accomplish this would be to assign fake sequential dates to sort the RSS feeds. The date should probably also leave room for adding mid-series books without needing to change the already existing items' dates, ex. always start at year 2020 and use increments of 10 days for the series to allow for numbers like `series #4.5` (gets assigned the 45th day in 2020). A further enhancement could be a "sort" drop-down when opening a feed, then using the pubDate to sort based on the criteria the user selects. ### Why would this be helpful? This would allow users to have control over the sorting of RSS feeds and more easily find the next book in a series or collection. ### Future Implementation (Screenshot) <img width="858" alt="Screenshot 2024-07-08 at 11 59 11 AM" src="https://github.com/advplyr/audiobookshelf/assets/22437387/f19f15b2-1f05-46cd-9139-92a37aaf1f05"> ### Audiobookshelf Server Version v2.11.0 ### Current Implementation (Screenshot) _No response_
adam added the enhancement label 2026-04-25 00:03:23 +02:00
adam closed this issue 2026-04-25 00:03:23 +02:00
adam commented 2026-04-25 00:03:23 +02:00
Author
Owner
Copy Link
Copy Source

@advplyr commented on GitHub (Jul 8, 2024):

I'm not entirely sure I understand everything you are suggesting but I can see how to fix the collection and series RSS feeds so that they are in order.
I can update it so that it uses the earliest book added at date as the starting point then add a day for each book.
If a new book is added, or if the order of the series/collection is changed, then it will update the RSS feed.

@advplyr commented on GitHub (Jul 8, 2024): I'm not entirely sure I understand everything you are suggesting but I can see how to fix the collection and series RSS feeds so that they are in order. I can update it so that it uses the earliest book added at date as the starting point then add a day for each book. If a new book is added, or if the order of the series/collection is changed, then it will update the RSS feed.
adam commented 2026-04-25 00:03:24 +02:00
Author
Owner
Copy Link
Copy Source

@noahkiss commented on GitHub (Jul 8, 2024):

That would be great!

It sounds like you took the important parts from my ramblings, so it's probably not important that you try to make sense of the rest 😛

Appreciate the reply & your work!

@noahkiss commented on GitHub (Jul 8, 2024): That would be great! It sounds like you took the important parts from my ramblings, so it's probably not important that you try to make sense of the rest 😛 Appreciate the reply & your work!
adam commented 2026-04-25 00:03:24 +02:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Aug 5, 2024):

Fixed in v2.12.0.

@github-actions[bot] commented on GitHub (Aug 5, 2024): Fixed in [v2.12.0](https://github.com/advplyr/audiobookshelf/releases/tag/v2.12.0).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
authentication
backlog
bug
chapter editor
config-issue
ebooks
encoding/embedding
enhancement
help wanted
listening sessions & progress
planned
possible plugin
progress sync
pull-request
Mirrored from GitHub Pull Request
 sorting/filtering/searching
unable to reproduce
upload
users & permissions
waiting
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam (Adam Melkus)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#2091
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?