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

[Bug]:Series grouping is case-sensitive — identical names with different letter case are treated as separate series. #2748

New Issue
Open
opened 2026-04-25 00:10:11 +02:00 by adam · 1 comment
adam commented 2026-04-25 00:10:11 +02:00
Owner
Copy Link
Copy Source

Originally created by @Ar4ius on GitHub (May 3, 2025).

What happened?

Audiobooks with identical series names that differ only in letter casing (e.g., Harry Potter vs harry potter) are not grouped together. This results in duplicate series entries in the library UI.

What did you expect to happen?

Books with series names that differ only by case should be grouped together under one series entry. Comparison should be case-insensitive. For example, Harry Potter and harry potter should be treated as the same series.

Steps to reproduce the issue

  1. Import two audiobooks with identical series names that differ only by case (e.g., Harry Potter and harry potter).
  2. Open the library and view the series list.
  3. Observe that the books are not grouped under the same series.

Audiobookshelf version

2.21.0

How are you running audiobookshelf?

Docker

What OS is your Audiobookshelf server hosted from?

Linux

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

Chrome

Logs

Additional Notes

This causes confusion and disorganization in larger libraries where metadata inconsistencies are common. Making the grouping logic case-insensitive would greatly improve usability.

Originally created by @Ar4ius on GitHub (May 3, 2025). ### What happened? Audiobooks with identical series names that differ only in letter casing (e.g., Harry Potter vs harry potter) are not grouped together. This results in duplicate series entries in the library UI. ### What did you expect to happen? Books with series names that differ only by case should be grouped together under one series entry. Comparison should be case-insensitive. For example, Harry Potter and harry potter should be treated as the same series. ### Steps to reproduce the issue 1. Import two audiobooks with identical series names that differ only by case (e.g., Harry Potter and harry potter). 2. Open the library and view the series list. 3. Observe that the books are not grouped under the same series. ### Audiobookshelf version 2.21.0 ### How are you running audiobookshelf? Docker ### What OS is your Audiobookshelf server hosted from? Linux ### If the issue is being seen in the UI, what browsers are you seeing the problem on? Chrome ### Logs ```shell ``` ### Additional Notes This causes confusion and disorganization in larger libraries where metadata inconsistencies are common. Making the grouping logic case-insensitive would greatly improve usability.
adam added the bug label 2026-04-25 00:10:11 +02:00
adam commented 2026-04-25 00:10:11 +02:00
Author
Owner
Copy Link
Copy Source

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

Related to https://github.com/advplyr/audiobookshelf/issues/4033

@nichwall commented on GitHub (May 3, 2025): Related to https://github.com/advplyr/audiobookshelf/issues/4033
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 bug
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#2748
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?