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

[PR #4797] Add a 'Match after scan' option to the schedule scan config #4350

New Issue
Open
opened 2026-04-25 00:19:23 +02:00 by adam · 0 comments
adam commented 2026-04-25 00:19:23 +02:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/advplyr/audiobookshelf/pull/4797
Author: @indiefan
Created: 11/4/2025
Status: 🔄 Open

Base: master ← Head: match-after-scan

📝 Commits (2)

  • 0ab72d8 Adds a 'Match after scan' option to the manual schedule configuration options for scanning.
  • 3a751f7 Add a minimum confidence level threshold to match after scan runs.

📊 Changes

9 files changed (+221 additions, -106 deletions)

View changed files

📝 client/components/modals/libraries/EditModal.vue (+2 -0)
📝 client/components/modals/libraries/ScheduleScan.vue (+40 -3)
📝 client/strings/en-us.json (+2 -0)
📝 server/controllers/LibraryController.js (+22 -0)
📝 server/managers/CronManager.js (+14 -1)
📝 server/models/Library.js (+2 -0)
📝 server/routers/ApiRouter.js (+3 -98)
📝 server/scanner/Scanner.js (+10 -4)
➕ server/utils/cleanup.js (+126 -0)

📄 Description

Brief summary

Adds an optional configuration toggle to the "Schedule" tab in edit library to also run "Match Books" after the manually scheduled scans take place. Includes a slider for minimum confidence level threshold to accept the match.

Which issue is fixed?

I'm not aware of an open issue for this feature. Allows for manually scheduling matching to be performed at a regular cadence.

In-depth Description

Adds a boolean to the library settings model and confidence level threshold, then uses these in the CronManager to execute the match after the scan completes. Refactors ApiRouter a bit to avoid a circular dependency with the CronManager.

How have you tested this?

Manually triggered in my dev build and ran npm test in both the root and client folders (are there other tests I should run?).

Screenshots

image image

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/advplyr/audiobookshelf/pull/4797 **Author:** [@indiefan](https://github.com/indiefan) **Created:** 11/4/2025 **Status:** 🔄 Open **Base:** `master` ← **Head:** `match-after-scan` --- ### 📝 Commits (2) - [`0ab72d8`](https://github.com/advplyr/audiobookshelf/commit/0ab72d879e4e6b6b8068c1759f4fad21a8515aab) Adds a 'Match after scan' option to the manual schedule configuration options for scanning. - [`3a751f7`](https://github.com/advplyr/audiobookshelf/commit/3a751f711ad9ab62682fdf3a6d1b0e37257cf21a) Add a minimum confidence level threshold to match after scan runs. ### 📊 Changes **9 files changed** (+221 additions, -106 deletions) <details> <summary>View changed files</summary> 📝 `client/components/modals/libraries/EditModal.vue` (+2 -0) 📝 `client/components/modals/libraries/ScheduleScan.vue` (+40 -3) 📝 `client/strings/en-us.json` (+2 -0) 📝 `server/controllers/LibraryController.js` (+22 -0) 📝 `server/managers/CronManager.js` (+14 -1) 📝 `server/models/Library.js` (+2 -0) 📝 `server/routers/ApiRouter.js` (+3 -98) 📝 `server/scanner/Scanner.js` (+10 -4) ➕ `server/utils/cleanup.js` (+126 -0) </details> ### 📄 Description ## Brief summary Adds an optional configuration toggle to the "Schedule" tab in edit library to also run "Match Books" after the manually scheduled scans take place. Includes a slider for minimum confidence level threshold to accept the match. ## Which issue is fixed? I'm not aware of an open issue for this feature. Allows for manually scheduling matching to be performed at a regular cadence. ## In-depth Description Adds a boolean to the library settings model and confidence level threshold, then uses these in the CronManager to execute the match after the scan completes. Refactors ApiRouter a bit to avoid a circular dependency with the CronManager. ## How have you tested this? Manually triggered in my dev build and ran npm test in both the root and client folders (are there other tests I should run?). ## Screenshots <img width="820" height="604" alt="image" src="https://github.com/user-attachments/assets/d6b62058-d25f-433f-b6dc-301eb6b48230" /> <img width="820" height="646" alt="image" src="https://github.com/user-attachments/assets/34ee5df0-1032-481c-ba2a-e6b9f0af511f" /> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
adam added the pull-request label 2026-04-25 00:19:23 +02:00
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 pull-request
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#4350
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?