mirror of
https://github.com/advplyr/audiobookshelf.git
synced 2026-05-30 23:40:40 +02:00
[Bug]: ePub books, in unique folders combined into single entry #2425
Assignees
adam (Adam Melkus)
Clear assignees
adam (Adam Melkus)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/audiobookshelf#2425
Reference in New Issue
Block a user
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?
Originally created by @andrewlow on GitHub (Dec 15, 2024).
What happened?
I'm primarily using audiobookshelf to manage ePub books.
I recently grabbed the Humble Bundle of John Scalzi books - 21 of them.
They initially came with not very friendly names.
Ok - so I don't expect the matching to work nicely here - so of course I took the time to rename all of the files to a sensible "directory" per book.
I will note - Starter Villain was already in my library ..
Now, I also got here via iteration - I first tested the Redshirts would work ok - and it did. So I had a Library with Redshirts and Starter Villain
However, after copying the nicely named directories into the location that audiobookshelf is watching.. I got this
What did you expect to happen?
I expected to see my library have all 21 new books listed individually.
This has worked for other authors - but I have a small library, and limited test cases.
Steps to reproduce the issue
{Book name as folder name}/{Book name} - {Author name}.epubAudiobookshelf version
2.17.5
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?
Firefox
Logs
No response
Additional Notes
No response
@andrewlow commented on GitHub (Dec 15, 2024):
Exploring the 'multi entry' version of Starter Villain, I can see that it has somehow combined many epubs into a single entry
@andrewlow commented on GitHub (Dec 15, 2024):
I did find an old bug (close) like this - https://github.com/advplyr/audiobookshelf/issues/834 but it wasn't helpful.
@andrewlow commented on GitHub (Dec 15, 2024):
I can't seem to find the 'Book Scanner' settings in the web app https://www.audiobookshelf.org/guides/book-scanner
Did this go away (and the doc is old?) - or am I just not finding it?
@nichwall commented on GitHub (Dec 15, 2024):
This can happen if you have the watcher enabled and the book is created/updated in the database automatically. If you scroll through all of the files in the table in ABS, do you see any books which are not in a folder correctly? Once the files are attached to the book, there isn't really a good way to remove them from the book due to ABS alerting users of "missing files" in case something gets deleted on accident.
To force the database to fix the library item, you can delete the problem book from ABS (make sure the checkbox is unmarked to not delete the files from your file system) and scan the library again.
The "metadata order of precedence" is in the settings for the library. Settings -> Libraries -> Edit -> Scanner tab.
@andrewlow commented on GitHub (Dec 15, 2024):
Thanks for the reply.
I do have the watcher enabled.
I'm do not understand this comment.
I know exactly what the filesystem looks like - every book is a single .epub file, and each of those .epub files are in a unique directory (one per book).
Selecting the 2nd copy of 'Starter Villain' which was the messed up entry - and NOT allowing the deletion of the files - then deleting the entry. Then manually re-scanning the library resulted in all of the 'new' books being found and added correctly. [This fixed my problem]
I've disabled the watcher - as it seems like it was my root problem here. I can live with manually scanning to find new books, I rarely add them.
Thank you for pointing this out. I was able to find this.
It is unclear if this is a bug with the "Watcher" or if I'm doing things in a weird way. If there is more data I can gather to help identify the issue I'm willing to dig around, otherwise we can close this as my problem is solved.
@advplyr commented on GitHub (Dec 21, 2024):
If I'm understanding this correctly the steps you mentioned to reproduce the issue is missing the most important step.
Let me know if this is incorrect.
When you first added those epubs in your file system they were all under a single subfolder.
The watcher will scan those in as a single book.
Then you moved the epubs into separate folders.
The watcher will detect the file path changed on those files and update the file paths.
Does that sound right?
@andrewlow commented on GitHub (Dec 23, 2024):
Darn - I did initially have them all as a single sub-folder.. but with different names.
When I moved them to unique sub-folders - I changed the names of each of them. Yes - it was a
mvoperation to movebut yes - if the system was able to identify the file by something other than the name.. it could have all been a single ebook...
@advplyr commented on GitHub (Dec 23, 2024):
Abs uses the filesystems inode value so that if you rename the file Abs knows it is the same file.
This case is specific to the ebooks already being in a subfolder and already being scanned into the system. Since you can have a book in a folder that has subfolders like "CD01" to break out the files Abs allows you to move ebook/audio files into subfolders of the existing book.
I'm not sure if that makes sense. We don't necessarily want to remove the existing book that was scanned in and create separate books anytime an ebook/audio file is moved into a subfolder
@andrewlow commented on GitHub (Dec 23, 2024):
Well - if it's using the inode, yeah - renaming the file doesn't change that. I clearly just got confused initially when I bulk added the files - then didn't 'reset' things by deleting them - and re-creating them as a new thing.
Let's close this issue.