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: Logging - Summary numbers for the scanner on the log page #81

New Issue
Open
opened 2026-04-24 22:57:53 +02:00 by adam · 3 comments
adam commented 2026-04-24 22:57:53 +02:00
Owner
Copy Link
Copy Source

Originally created by @jarrodCoombes on GitHub (Oct 27, 2021).

Something like:

Library has:
xxxx Folders that appear to be books (ie last folder in the chain)
xxxx Folders that do not appear to be books and/or have audio book content in them (also last folder in the chain).
Last Books updated (list about 10).
Last Errors in the log (list the last few, maybe 5 - 10, with dates)

Then maybe an expandable list that allows you to look at the the folder names, especially the non-book folders. Makes it much easier to see if there are any books not coming up as books, especially in larger libraries.

The reason this came to mind for me is that AudiobookLibrary reports I have 935 books, but I have absolutely not way of confirming that unless I go through each author manually. And based on the weird issue I had with a defective MP3, it is conceivable I have an entire folder or two that has bad MP3s in it, I'd never know.

Originally created by @jarrodCoombes on GitHub (Oct 27, 2021). Something like: > Library has: > xxxx Folders that appear to be books (ie last folder in the chain) > xxxx Folders that do not appear to be books and/or have audio book content in them (also last folder in the chain). > Last Books updated (list about 10). > Last Errors in the log (list the last few, maybe 5 - 10, with dates) Then maybe an expandable list that allows you to look at the the folder names, especially the non-book folders. Makes it much easier to see if there are any books not coming up as books, especially in larger libraries. The reason this came to mind for me is that AudiobookLibrary reports I have 935 books, but I have absolutely not way of confirming that unless I go through each author manually. And based on the weird issue I had with a defective MP3, it is conceivable I have an entire folder or two that has bad MP3s in it, I'd never know.
adam commented 2026-04-24 22:57:54 +02:00
Author
Owner
Copy Link
Copy Source

@advplyr commented on GitHub (Oct 29, 2021):

Agree, a "scan log" is needed at this point, I'm just not sure where to put it.
I'm thinking either a new page in /config with a row for each scan that you can click in to.
or possibly update the log page to show a list of scan logs

@advplyr commented on GitHub (Oct 29, 2021): Agree, a "scan log" is needed at this point, I'm just not sure where to put it. I'm thinking either a new page in /config with a row for each scan that you can click in to. or possibly update the log page to show a list of scan logs
adam commented 2026-04-24 22:57:54 +02:00
Author
Owner
Copy Link
Copy Source

@jarrodCoombes commented on GitHub (Oct 29, 2021):

I'd suggest just adding it to the log page in settings. Put it at the top, with the real time logger under it.

@jarrodCoombes commented on GitHub (Oct 29, 2021): I'd suggest just adding it to the log page in settings. Put it at the top, with the real time logger under it.
adam commented 2026-04-24 22:57:55 +02:00
Author
Owner
Copy Link
Copy Source

@DDriggs00 commented on GitHub (Jul 16, 2024):

This would be a very useful feature when debugging. As for when/where, I'd recommend just putting scan results in the main log, with levels following the standard log levels. Maybe put "Scan completed and found x items (y new, z changed)" as info, and the rest (new/existing/unchanged Item x found and added/changed/is unchanged) as debug? As for a specialized scan log, I don't think that it needs its own setting, and could be controlled by the log verbosity setting.

@DDriggs00 commented on GitHub (Jul 16, 2024): This would be a very useful feature when debugging. As for when/where, I'd recommend just putting scan results in the main log, with levels following the standard log levels. Maybe put "Scan completed and found x items (y new, z changed)" as info, and the rest (new/existing/unchanged Item x found and added/changed/is unchanged) as debug? As for a specialized scan log, I don't think that it needs its own setting, and could be controlled by the log verbosity setting.
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
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#81
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?