starred/audiobookshelf

Fork 0

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

[Bug]: Series Sequence Issue #2965

New issue

Open

opened 2026-02-20 03:03:47 -05:00 by deekerman · 6 comments

deekerman commented

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

Owner

Originally created by @GinSoakedBoy on GitHub (May 19, 2025).

What happened?

Adding something other than just a number to a series Sequence causes ABS to change the series.

For example The Uriel Ventris Chronicles One and Two are both a collection of novels and short stories. Goodreads has them listed in the Ultramarines Series as "BOOK 1-3 + SHORT STORIES" and "BOOK 4-6 + SHORT STORIES".

ABS changes the series to "Ultramarines #1-3 & short stories" and "Ultramarines #4-6 & short stories"

What did you expect to happen?

Ideally the series would be "Ultramarines"with the sequence being "1-3 & short stories" and "4-6 & short stories".

Steps to reproduce the issue

Change the "Sequence" of a book within a Series to something with multiple words e.g. Short Story

Audiobookshelf version

v2.23.0

How are you running audiobookshelf?

Docker

What OS is your Audiobookshelf server hosted from?

Other (list in "Additional Notes" box)

If the issue is being seen in the UI, what browsers are you seeing the problem on?

None

Logs

Additional Notes

Running in a Portainer docker container on a TrueNAS server.

Originally created by @GinSoakedBoy on GitHub (May 19, 2025). ### What happened? Adding something other than just a number to a series Sequence causes ABS to change the series. For example The Uriel Ventris Chronicles One and Two are both a collection of novels and short stories. Goodreads has them listed in the Ultramarines Series as "BOOK 1-3 + SHORT STORIES" and "BOOK 4-6 + SHORT STORIES". ABS changes the series to "Ultramarines #1-3 & short stories" and "Ultramarines #4-6 & short stories" <img width="513" alt="Image" src="https://github.com/user-attachments/assets/ca254899-dbd7-4e6c-aa2c-6cf8df9f088a" /> ### What did you expect to happen? Ideally the series would be "Ultramarines"with the sequence being "1-3 & short stories" and "4-6 & short stories". ### Steps to reproduce the issue 1. Change the "Sequence" of a book within a Series to something with multiple words e.g. Short Story ### Audiobookshelf version v2.23.0 ### How are you running audiobookshelf? Docker ### What OS is your Audiobookshelf server hosted from? Other (list in "Additional Notes" box) ### If the issue is being seen in the UI, what browsers are you seeing the problem on? None ### Logs ```shell ``` ### Additional Notes Running in a Portainer docker container on a TrueNAS server.

deekerman added the

bug

label

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

deekerman commented

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

Author

Owner

@nichwall commented on GitHub (May 19, 2025):

How was this set? Importing from the file system, manually setting it in the UI, or matching against an online provider?

@nichwall commented on GitHub (May 19, 2025): How was this set? Importing from the file system, manually setting it in the UI, or matching against an online provider?

deekerman commented

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

Author

Owner

@GinSoakedBoy commented on GitHub (May 19, 2025):

Setting manually within the UI, and matching with GoodReads using abs-tract.

@GinSoakedBoy commented on GitHub (May 19, 2025): Setting manually within the UI, and matching with GoodReads using [abs-tract](https://github.com/ahobsonsayers/abs-tract).

deekerman commented

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

Author

Owner

@Vito0912 commented on GitHub (May 19, 2025):

I somewhat experienced the same behaviour.

I am not sure what caused it, because I am not sure when I noticed it, but I think enconding an item with a series with multiple words leads to the exact same behaviour (but not tested, but same symptoms)

@Vito0912 commented on GitHub (May 19, 2025): I somewhat experienced the same behaviour. I am not sure what caused it, because I am not sure when I noticed it, but I think enconding an item with a series with multiple words leads to the exact same behaviour (but not tested, but same symptoms)

deekerman commented

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

Author

Owner

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

This is because you are storing json metadata with the item and those series are saved as "Series name #1".

  "series": [
    "Test #1-3 & short stories"
  ],

Then those get parsed here:
github.com/advplyr/audiobookshelf@0772730336/server/utils/parsers/parseSeriesString.js (L1-L27)

There is an open bug report for this already I'm pretty sure.

That json should just be updated to store an object instead of a string

@advplyr commented on GitHub (May 19, 2025): This is because you are storing json metadata with the item and those series are saved as "Series name #1". ```json "series": [ "Test #1-3 & short stories" ], ``` Then those get parsed here: https://github.com/advplyr/audiobookshelf/blob/077273033657da2345494084dc7a1f399cc1a7ba/server/utils/parsers/parseSeriesString.js#L1-L27 There is an open bug report for this already I'm pretty sure. That json should just be updated to store an object instead of a string

deekerman commented

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

Author

Owner

@GinSoakedBoy commented on GitHub (May 19, 2025):

Is this something that can be fixed, or do we need to avoid spaces in series sequences?

@GinSoakedBoy commented on GitHub (May 19, 2025): Is this something that can be fixed, or do we need to avoid spaces in series sequences?

deekerman commented

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

Author

Owner

@nichwall commented on GitHub (May 19, 2025):

Is this something that can be fixed, or do we need to avoid spaces in series sequences?

It would probably be best to just avoid spaces in series sequences. Currently the series sequence is a string (so can contain numbers and letters), but the hope is to eventually only support numbers so SQL queries are easier to handle. Unfortunately, a lot of users were already using alphanumeric series sequence (such as 1.a) before Audiobookshelf migrated to SQLite.

@nichwall commented on GitHub (May 19, 2025): > Is this something that can be fixed, or do we need to avoid spaces in series sequences? It would probably be best to just avoid spaces in series sequences. Currently the series sequence is a string (so can contain numbers and letters), but the hope is to eventually only support numbers so SQL queries are easier to handle. Unfortunately, a lot of users were already using alphanumeric series sequence (such as `1.a`) before Audiobookshelf migrated to SQLite.