[Bug 40815] New: Item Search -- Allow 1000 visible rows.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40815 Bug ID: 40815 Summary: Item Search -- Allow 1000 visible rows. Change sponsored?: --- Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs@lists.koha-community.org Reporter: l.curanzy@newportlibrary.org QA Contact: testopia@bugs.koha-community.org CC: m.de.rooy@rijksmuseum.nl Created attachment 186446 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=186446&action=edit Image of dropdown menu that ends at 100. Right now, 100 is the max number of visible rows we can select from Item Search results in order to export to Item Batch Modification. This means, for 1,600 results, I need to export the results 16 times. 1000 is the max number of results that can be exported to Batch Modification at one time. Why not make this an option? If 1000 rows were an option in the dropdown menu (image attached). I would only have to export the Batch Modification 2 times. That's many fewer! Thanks for your consideration! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40815 Anneli Österman <anneli.osterman@koha-suomi.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |anneli.osterman@koha-suomi. | |fi --- Comment #1 from Anneli Österman <anneli.osterman@koha-suomi.fi> --- Where does the information that 1000 is the max number of results to be exported come from? You can change the maximum with MaxItemsToProcessForBatchMod system preference. I think we have batch modified up to 15 000 items at once in our libraries. We have set limit of 1000 to MaxItemsToDisplayForBatchMod because displaying 15 000 items in batch modification is too slow and ends up in proxy error / timeout. But you can still modify more than 1000 successfully even if they are not shown. Modifications go to the background jobs which allows you to modify larger batches than before the background jobs were added. But yes, otherwise I also think that 100 is a bit small number when doing batch modifications and 1000 rows is a more useful option. :) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40815 Lillian <l.curanzy@newportlibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #2 from Lillian <l.curanzy@newportlibrary.org> --- Thanks Anneli! I think changing that system preference will make things easier for our purposes! Our setting is at 1000. I will increase this and be happy! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40815 Lillian <l.curanzy@newportlibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |--- Status|RESOLVED |REOPENED --- Comment #3 from Lillian <l.curanzy@newportlibrary.org> --- Would increasing this number cause server strain? It might be better to add only 1000 records to batch mod at once. Unless there is a good max number that someone can recommend. I know it probably depends on how many changes we are making to the records at once. Ultimately, I would still like 1000 to be an option on the display records, since it's the default Koha setting for MaxItemsToProcessForBatchMod preference. Thanks again Anneli! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40815 --- Comment #4 from Anneli Österman <anneli.osterman@koha-suomi.fi> --- I do not know the technical explanation but this is how they are described in the manual: "Jobs are tasks that are queued in the system to be treated when the server has the resources to do it." So how I understand it is that they decrease the strain because the batch modifications are made when the server has more resources at hand. Maybe someone with more technical knowledge could explain what happens when batch modifications are done? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org