[Bug 41022] New: In holding table limit the values of each filter to values actually present in items
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41022 Bug ID: 41022 Summary: In holding table limit the values of each filter to values actually present in items Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs@lists.koha-community.org Reporter: mathsabypro@gmail.com QA Contact: testopia@bugs.koha-community.org CC: gmcharlt@gmail.com Maybe it is difficult or not possible but it would be nice to limit the values for items filters to the values actually present in items for each specific record. This could be applied to the 4 fields for which a dropdown list is displayed (item type, homebranch, holdingbranch, status) Ex : you have only 2 items, of item type "book" and "map" => the filter should propose only 2 options ("book" and "map") and not the complete list of item type configured in the system. -- 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=41022 Jonathan Druart <jonathan.druart@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jonathan.druart@gmail.com --- Comment #1 from Jonathan Druart <jonathan.druart@gmail.com> --- For libraries and item types - without using elastic for items I don't think we can implement that without performance issues. It would be interesting to know how much time it takes to `select distinct(field) from items where biblionumber=x` when there are a lot of items (10k). For status - not conceivable (still perf related) without storing the status. -- 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=41022 --- Comment #2 from Jonathan Druart <jonathan.druart@gmail.com> --- (In reply to Jonathan Druart from comment #1)
For libraries and item types - without using elastic for items I don't think we can implement that without performance issues. It would be interesting to know how much time it takes to `select distinct(field) from items where biblionumber=x` when there are a lot of items (10k).
And there are also the values from the host records that will need to be retrieved. -- 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=41022 --- Comment #3 from Mathieu Saby <mathsabypro@gmail.com> --- You don't apply a filter immediatly when the table is displayed. Manually you need a few second to get to the filters with your mouse or keyboard. Would it be possible to hide (in a invisible way) some values of the filters *after* the display of the table ? -- 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=41022 --- Comment #4 from Mathieu Saby <mathsabypro@gmail.com> --- Technically, would it be relevant to develop a new API route to retrieve the list of values present in the different fields of the items for a record? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org