[Enhancement]: Series numbers should optionally support part numbers e.g. Elantris #1pt2 #3290

Open
opened 2026-02-20 03:06:59 -05:00 by deekerman · 9 comments
Owner

Originally created by @saltedlolly on GitHub (Nov 23, 2025).

Type of Enhancement

None

Describe the Feature/Enhancement

Some audiobooks are split into parts. An obvious example is GraphicAudio adaptations of books. You might also have audiobooks which contain several several books from an authors work where it is helpful to split them into separate parts.

It would be very helpful if the current series numbering could support part numbers - e.g. #3part1, #1.5pt2,

(I suggest allowing for the workd 'part' or simply the abbreviation 'pt' in the # makes sense)

Meta tag example (CONTENTGROUP/WORK/SERIES):

Elantris [GraphicAudio] #1part3; The Cosmere [GraphicAudio]
Elantris [GraphicAudio] #01pt3; The Cosmere [GraphicAudio]
Elantris [GraphicAudio] #1pt03; The Cosmere [GraphicAudio]

Folder name examples:

/Brandon Sanderson/Elantris [GraphicAudio]/Vol 1pt3 - Elantris - Part 3 of 3 [GraphicAudio]
/Brandon Sanderson/Elantris [GraphicAudio]/Vol 01part3 - Elantris - Part 3 of 3 [GraphicAudio]
/Brandon Sanderson/Elantris [GraphicAudio]/Vol 1 part 3 - Elantris - Part 3 of 3 [GraphicAudio]

Why would this be helpful?

Currently if you have the GraphicAudio adaption of a book and the original book, you end up needing to use different numbering for each. Allowing for part numbers would allow the overall book number to remain consistent.

Right now if all parts use the same the #1 then there is no guarantee tha the parts appear in the correct order within the series.

A flawed workaround it to use #1.1, #1.2, #1.3 etc. but decimals are currently already used to indicate short stories and novellas. This messes the numbering sequence.

Future Implementation (Screenshot)

Explained above.

Audiobookshelf Server Version

v2.30.0

Current Implementation (Screenshot)

No response

Originally created by @saltedlolly on GitHub (Nov 23, 2025). ### Type of Enhancement None ### Describe the Feature/Enhancement Some audiobooks are split into parts. An obvious example is GraphicAudio adaptations of books. You might also have audiobooks which contain several several books from an authors work where it is helpful to split them into separate parts. It would be very helpful if the current series numbering could support part numbers - e.g. #3part1, #1.5pt2, (I suggest allowing for the workd 'part' or simply the abbreviation 'pt' in the # makes sense) Meta tag example (CONTENTGROUP/WORK/SERIES): Elantris [GraphicAudio] #1part3; The Cosmere [GraphicAudio] Elantris [GraphicAudio] #01pt3; The Cosmere [GraphicAudio] Elantris [GraphicAudio] #1pt03; The Cosmere [GraphicAudio] Folder name examples: /Brandon Sanderson/Elantris [GraphicAudio]/Vol 1pt3 - Elantris - Part 3 of 3 [GraphicAudio] /Brandon Sanderson/Elantris [GraphicAudio]/Vol 01part3 - Elantris - Part 3 of 3 [GraphicAudio] /Brandon Sanderson/Elantris [GraphicAudio]/Vol 1 part 3 - Elantris - Part 3 of 3 [GraphicAudio] ### Why would this be helpful? Currently if you have the GraphicAudio adaption of a book and the original book, you end up needing to use different numbering for each. Allowing for part numbers would allow the overall book number to remain consistent. Right now if all parts use the same the #1 then there is no guarantee tha the parts appear in the correct order within the series. A flawed workaround it to use #1.1, #1.2, #1.3 etc. but decimals are currently already used to indicate short stories and novellas. This messes the numbering sequence. ### Future Implementation (Screenshot) Explained above. ### Audiobookshelf Server Version v2.30.0 ### Current Implementation (Screenshot) _No response_
Author
Owner

@advplyr commented on GitHub (Nov 23, 2025):

Since sqlite doesn't support natural sorting this is unlikely to be supported. I'm pretty sure Audible series sequence are integers also and I'm not aware of any other metadata provider that includes non-numeric series sequence.
We can continue to support decimals.
I know this has been brought up a few times but I couldn't find an exact duplicate.
Related to the sorting issue https://github.com/advplyr/audiobookshelf/issues/3792 https://github.com/advplyr/audiobookshelf/issues/2281

@advplyr commented on GitHub (Nov 23, 2025): Since sqlite doesn't support natural sorting this is unlikely to be supported. I'm pretty sure Audible series sequence are integers also and I'm not aware of any other metadata provider that includes non-numeric series sequence. We can continue to support decimals. I know this has been brought up a few times but I couldn't find an exact duplicate. Related to the sorting issue https://github.com/advplyr/audiobookshelf/issues/3792 https://github.com/advplyr/audiobookshelf/issues/2281
Author
Owner

@Vito0912 commented on GitHub (Nov 23, 2025):

I'm not aware of any other metadata provider that includes non-numeric series sequence.

Iirc there are non interger series. Let me check my db

@Vito0912 commented on GitHub (Nov 23, 2025): > I'm not aware of any other metadata provider that includes non-numeric series sequence. Iirc there are non interger series. Let me check my db
Author
Owner

@Vito0912 commented on GitHub (Nov 23, 2025):

Yes. See:

B01K4DFYJO,B01KA38NRI,1.1-1.13
B0BZJSW1MJ,B00JMI26LM,"6, Part 1 Dramatized Adaptation"

and many more (around ~6% have a non integer and double value)

position !~ '^\d+(\.\d+)?$';

@Vito0912 commented on GitHub (Nov 23, 2025): Yes. See: ``` B01K4DFYJO,B01KA38NRI,1.1-1.13 B0BZJSW1MJ,B00JMI26LM,"6, Part 1 Dramatized Adaptation" ``` and many more (around ~6% have a non integer and double value) `position !~ '^\d+(\.\d+)?$';`
Author
Owner

@saltedlolly commented on GitHub (Nov 23, 2025):

Hmmm... on the basis that a series number can only be a integer/decimal, when listing a series, would it be possible to sort the books by:

  1. Series number
  2. Book title
  3. Book subtitle

This way, you can make the the series number the same for all parts of the same book, but then if you put the part number in the title, or even the subtitle, they will get sorted in the correct order. Currently there is no guarantee that they appear in alphanumeric order if the number is in the title or subtitle.

Examples

If you have two parts of a book entered like so:

Series: Mistborn #3
Title: The Hero of Ages
Subtitle: Part 1 of 3 [GraphicAudio]

Series: Mistborn #3
Title: The Hero of Ages
Subtitle: Part 2 of 3 [GraphicAudio]

This way if the only thing that changes between the two books in the series is the number in the subtitle, they still get listed in the correct order, as they are sorted first by series number (3), second by title (also the same both parts), and lastly by subtitle which actually ensures they end up in the correct order.

This way if you put the part number in the title or the subtitle you can be sure they will be sorted in the correct order in the series view.

@saltedlolly commented on GitHub (Nov 23, 2025): Hmmm... on the basis that a series number can only be a integer/decimal, when listing a series, would it be possible to sort the books by: 1. Series number 2. Book title 3. Book subtitle This way, you can make the the series number the same for all parts of the same book, but then if you put the part number in the title, or even the subtitle, they will get sorted in the correct order. Currently there is no guarantee that they appear in alphanumeric order if the number is in the title or subtitle. Examples If you have two parts of a book entered like so: Series: Mistborn #3 Title: The Hero of Ages Subtitle: Part 1 of 3 [GraphicAudio] Series: Mistborn #3 Title: The Hero of Ages Subtitle: Part 2 of 3 [GraphicAudio] This way if the only thing that changes between the two books in the series is the number in the subtitle, they still get listed in the correct order, as they are sorted first by series number (3), second by title (also the same both parts), and lastly by subtitle which actually ensures they end up in the correct order. This way if you put the part number in the title or the subtitle you can be sure they will be sorted in the correct order in the series view.
Author
Owner

@nichwall commented on GitHub (Nov 24, 2025):

This way, you can make the the series number the same for all parts of the same book, but then if you put the part number in the title, or even the subtitle, they will get sorted in the correct order. Currently there is no guarantee that they appear in alphanumeric order if the number is in the title or subtitle.

Is there a reason you can't do 3.0 and 3.1 or something? I realize there are novelas that use the x.1 or x.5, but this sorting is already supported. You could even do 3.01 or something to make it clear that it is not a novella or short story and is instead a part of the same book.

@nichwall commented on GitHub (Nov 24, 2025): > This way, you can make the the series number the same for all parts of the same book, but then if you put the part number in the title, or even the subtitle, they will get sorted in the correct order. Currently there is no guarantee that they appear in alphanumeric order if the number is in the title or subtitle. Is there a reason you can't do `3.0` and `3.1` or something? I realize there are novelas that use the `x.1` or `x.5`, but this sorting is already supported. You could even do `3.01` or something to make it clear that it is not a novella or short story and is instead a part of the same book.
Author
Owner

@advplyr commented on GitHub (Nov 24, 2025):

Yes. See:

B01K4DFYJO,B01KA38NRI,1.1-1.13
B0BZJSW1MJ,B00JMI26LM,"6, Part 1 Dramatized Adaptation"

and many more (around ~6% have a non integer and double value)

position !~ '^\d+(\.\d+)?$';

These are from the audible API?

@advplyr commented on GitHub (Nov 24, 2025): > Yes. See: > > ``` > B01K4DFYJO,B01KA38NRI,1.1-1.13 > B0BZJSW1MJ,B00JMI26LM,"6, Part 1 Dramatized Adaptation" > ``` > > and many more (around ~6% have a non integer and double value) > > `position !~ '^\d+(\.\d+)?$';` These are from the audible API?
Author
Owner

@saltedlolly commented on GitHub (Nov 24, 2025):

This way, you can make the the series number the same for all parts of the same book, but then if you put the part number in the title, or even the subtitle, they will get sorted in the correct order. Currently there is no guarantee that they appear in alphanumeric order if the number is in the title or subtitle.

Is there a reason you can't do 3.0 and 3.1 or something? I realize there are novelas that use the x.1 or x.5, but this sorting is already supported. You could even do 3.01 or something to make it clear that it is not a novella or short story and is instead a part of the same book.

Doing 3.1, 3.2. 3.3 etc. is what i tried to do originally but this created problems when you have a novella or short story that also uses decimals. It had not occurred to me to do 3.01, 3.02. 3.03 for Parts 1,2 and 3 of book 3 in a series, but that is actually a pretty good workaround for now, at least until a better solution comes along. Thanks for the suggestion.

Assuming you can't put the part in the series number itself, I think the best solution would be for book series to sort first by series number, second by title, third by subtitle. This would solve it pretty elegantly, and ensure that if you put the title as "Elantris - Part x of 3" (or something similar as the subtitle), they get sorted into the correct order, regardless if the series number is the same for all three parts.

@saltedlolly commented on GitHub (Nov 24, 2025): > > This way, you can make the the series number the same for all parts of the same book, but then if you put the part number in the title, or even the subtitle, they will get sorted in the correct order. Currently there is no guarantee that they appear in alphanumeric order if the number is in the title or subtitle. > > Is there a reason you can't do `3.0` and `3.1` or something? I realize there are novelas that use the `x.1` or `x.5`, but this sorting is already supported. You could even do `3.01` or something to make it clear that it is not a novella or short story and is instead a part of the same book. Doing 3.1, 3.2. 3.3 etc. is what i tried to do originally but this created problems when you have a novella or short story that also uses decimals. It had not occurred to me to do 3.01, 3.02. 3.03 for Parts 1,2 and 3 of book 3 in a series, but that is actually a pretty good workaround for now, at least until a better solution comes along. Thanks for the suggestion. Assuming you can't put the part in the series number itself, I think the best solution would be for book series to sort first by series number, second by title, third by subtitle. This would solve it pretty elegantly, and ensure that if you put the title as "Elantris - Part x of 3" (or something similar as the subtitle), they get sorted into the correct order, regardless if the series number is the same for all three parts.
Author
Owner

@Vito0912 commented on GitHub (Nov 24, 2025):

Yes. See:

B01K4DFYJO,B01KA38NRI,1.1-1.13
B0BZJSW1MJ,B00JMI26LM,"6, Part 1 Dramatized Adaptation"

and many more (around ~6% have a non integer and double value)
position !~ '^\d+(\.\d+)?$';

These are from the audible API?

Yes. It's raw data from the Audible API. You can search for B0BZJSW1MJ. It has this as the priamry series

ABS just drops everything. Indeed 6% of all books that have a series have a non integer series part attached

@Vito0912 commented on GitHub (Nov 24, 2025): > > Yes. See: > > ``` > > B01K4DFYJO,B01KA38NRI,1.1-1.13 > > B0BZJSW1MJ,B00JMI26LM,"6, Part 1 Dramatized Adaptation" > > ``` > > > > > > > > > > > > > > > > > > > > > > > > and many more (around ~6% have a non integer and double value) > > `position !~ '^\d+(\.\d+)?$';` > > These are from the audible API? Yes. It's raw data from the Audible API. You can search for `B0BZJSW1MJ`. It has this as the priamry series ABS just drops everything. Indeed 6% of all books that have a series have a non integer series part attached
Author
Owner

@advplyr commented on GitHub (Nov 24, 2025):

Ah okay thanks. I even wrote the function to clean the sequence github.com/advplyr/audiobookshelf@b5e255a384

Example for future ref:
https://api.audible.com/1.0/catalog/products/B0BZJSW1MJ?response_groups=product_details,series

@advplyr commented on GitHub (Nov 24, 2025): Ah okay thanks. I even wrote the function to clean the sequence https://github.com/advplyr/audiobookshelf/commit/b5e255a3848637c636f92dd1110010fbdcb69e6c Example for future ref: https://api.audible.com/1.0/catalog/products/B0BZJSW1MJ?response_groups=product_details,series
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/audiobookshelf#3290
No description provided.