Bug 40440 - Ability helpful logs in the staff client when using batch modification tools and import tools
Summary: Ability helpful logs in the staff client when using batch modification tools ...
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-07-17 15:54 UTC by Enica Davis
Modified: 2025-07-23 15:23 UTC (History)
3 users (show)

See Also:
GIT URL:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Enica Davis 2025-07-17 15:54:58 UTC
This may be a duplicate bug, if so please let me know.

While worker-output keeps track of these changes, it would be helpful for libraries to see more details why their batch modification process or import process failed.

As it stands in Koha, you can only see that the import / batch mod process failed as well as when it succeeded.

What libraries are looking for are logs like the patron import, where it lists why the patron data didn't import and what the problem is.
Comment 1 trevor.diamond 2025-07-18 13:52:14 UTC
This is something that would be very useful for our cooperative.  Batch modifications of less than 30 items are easy enough to comb through for any exceptions, but if you're modifying hundreds or thousands of items, the exceptions become much more laborious to find.  And without knowing why those particular items failed, that's more staff time spent on follow up that could be better used elsewhere.