Summary: | Item Search - Display All entries is dangerous | ||
---|---|---|---|
Product: | Koha | Reporter: | Mathieu Saby <mathsabypro> |
Component: | Searching | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | trivial | ||
Priority: | P5 - low | CC: | anneli.osterman, jonathan.druart |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: |
Description
Mathieu Saby
2025-09-29 07:57:06 UTC
If the maximum number of rows are limited, there should be possibility configure it. For example 1000 rows is a bit low number when you are doing batch edits. Background jobs allows you to modify bigger batches that 1000 so it would be unfortunate change if the amount is limited to 1000 by default. It also works well for more than 1.000 items in most cases. For most our libraries "all" works and can be useful. If a limit is proposed, it should be configurable. The only correct way to implement this need is to implement a generic solution, in the table settings. We already have "Default display length", we could have a "Max Length", or even a multi select for each table with the different options (10, 20, 50, 100, 500, all). Preferably on top of bug 38259. |