[Bug 38122] New: Cannot sort holdings table by status
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Bug ID: 38122 Summary: Cannot sort holdings table by status Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs@lists.koha-community.org Reporter: lucas@bywatersolutions.com QA Contact: testopia@bugs.koha-community.org CC: gmcharlt@gmail.com, kyle.m.hall@gmail.com Bug 37334 will bring filtering to the holdings table status column. This bug is for the sorting of the status column. -- 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=38122 Lucas Gass <lucas@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |33568 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33568 [Bug 33568] Use the REST API to display items on the staff biblio detail view -- 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=38122 Michelle Spinney <mspinney@clamsnet.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mspinney@clamsnet.org -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Sarah Cornell <sbcornell@cityofportsmouth.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sbcornell@cityofportsmouth. | |com -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Kris <kbecker@jcls.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kbecker@jcls.org -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ilona R <hattara@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hattara@gmail.com -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Kristi <kkrueger@cuyahogalibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kkrueger@cuyahogalibrary.or | |g --- Comment #1 from Kristi <kkrueger@cuyahogalibrary.org> --- Our staff are anxious to have this restored! They use the sort on bibs that have more than 20 items, some that have over 100. -- 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=38122 Nick Clemens (kidclamp) <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nick@bywatersolutions.com Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Nick Clemens (kidclamp) <nick@bywatersolutions.com> --- *** This bug has been marked as a duplicate of bug 37334 *** -- 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=38122 Nick Clemens (kidclamp) <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|DUPLICATE |--- -- 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=38122 Jonathan Druart <jonathan.druart@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jonathan.druart@gmail.com --- Comment #3 from Jonathan Druart <jonathan.druart@gmail.com> --- (In reply to Kristi from comment #1)
Our staff are anxious to have this restored! They use the sort on bibs that have more than 20 items, some that have over 100.
Can you detail your use case please? -- 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=38122 --- Comment #4 from Kristi <kkrueger@cuyahogalibrary.org> --- We have several use cases: 1.Branch staff sort by status to see if they can identify an available copy and the branch it’s located at. 2. Our acquisitions team uses it to see how many viable (not missing, lost, withdrawn) copies are left on something that has high holds. Popular titles can have over 100 items. 3. Technical services uses it when looking at items that need to be called in to see if they are checked out, marked missing, etc. 4. We have wi-fi hotspots that are very popular and have several hundred items on the bib for each model. A lot of them are marked damaged, others are long overdue (Lost), some are Missing. These different statuses can make it confusing to know what should be circulating, so our staff use the status sort to eye up what is damaged, missing, etc. -- 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=38122 Jonathan Druart <jonathan.druart@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=37334 --- Comment #5 from Jonathan Druart <jonathan.druart@gmail.com> --- Don't you think bug 37334 would help in most of those situations? -- 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=38122 --- Comment #6 from Kristi <kkrueger@cuyahogalibrary.org> --- For use cases 1 and 2 especially, the sort rather than the filter would be the preferred method. -- 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=38122 Katie Bliss <kebliss@dmpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kebliss@dmpl.org -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 SamSowanick <sam.sowanick@corvallisoregon.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sam.sowanick@corvallisorego | |n.gov --- Comment #7 from SamSowanick <sam.sowanick@corvallisoregon.gov> --- Our staff would love this feature back too. They find it easier to quickly scan the items over filtering. But ideally there is room for both :). Upvoting. -- 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=38122 Jonathan Druart <jonathan.druart@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |In Discussion --- Comment #8 from Jonathan Druart <jonathan.druart@gmail.com> --- I prefer to be honest with you, there is very little chance to see the sort implemented in a near future. It was an limitation of bug 33568 that has been announced since day 1. I will do my best to provide alternative solutions that can potentially answer your needs however. (In reply to SamSowanick from comment #7)
They find it easier to quickly scan the items over filtering.
Can you detail what you mean here please? -- 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=38122 --- Comment #9 from SamSowanick <sam.sowanick@corvallisoregon.gov> --- The sort function is a way to group the items allowing scanning over all the items at one time, allowing seeing proportions of items status on one bib. Filtering accomplishes this but requires you to know what status you are looking for; while also hiding other items not in the searched status. I also just realized that you can SHIFT + CLICK to sort two fields at the same time, so it is fully possible that I am missing an alternate something. I will see if I can get more context from our staff. Thank you for highlighting the context to the limitations for this bug. -- 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=38122 Donna <bwsdonna@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bwsdonna@gmail.com --- Comment #10 from Donna <bwsdonna@gmail.com> --- Sorry - I'm not fluent in all the tech stuff, so it might be something obvious. But if all the other columns on the holdings table are sortable, why is status the only one that is not? -- 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=38122 --- Comment #11 from Jonathan Druart <jonathan.druart@gmail.com> --- (In reply to Donna from comment #10)
Sorry - I'm not fluent in all the tech stuff, so it might be something obvious. But if all the other columns on the holdings table are sortable, why is status the only one that is not?
Because it's calculated, not stored in DB like other attributes. If you want to sort by status you will need to calculate the status for all the items then display the 20 you want to display. -- 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=38122 --- Comment #12 from Lucas Gass (lukeg) <lucas@bywatersolutions.com> --- (In reply to Jonathan Druart from comment #8)
I prefer to be honest with you, there is very little chance to see the sort implemented in a near future. It was an limitation of bug 33568 that has been announced since day 1.
Unfortunately this is not an option. Before Bug 33568 one could sort by statuses, this is a regression and many libraries cannot live without it. -- 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=38122 --- Comment #13 from Lucas Gass (lukeg) <lucas@bywatersolutions.com> --- I can work on this after we get Bug 37334 pushed. -- 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=38122 --- Comment #14 from Jonathan Druart <jonathan.druart@gmail.com> --- (In reply to Lucas Gass (lukeg) from comment #13)
I can work on this after we get Bug 37334 pushed.
What are you plans? -- 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=38122 Marie-Luce Laflamme <marie-luce.laflamme@inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marie-luce.laflamme@inlibro | |.com --- Comment #15 from Marie-Luce Laflamme <marie-luce.laflamme@inlibro.com> --- Please bring back the "sort by statuses" option. -- 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=38122 Rebecca Coert <rcoert@arlingtonva.us> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rcoert@arlingtonva.us -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 mreid <mreid@batestech.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mreid@batestech.edu --- Comment #16 from mreid <mreid@batestech.edu> --- Please restore ability to sort the holdings table by status. This is particularly an issue for our bibs with large holdings (up to 150 items) across multiple branches. Staff appreciated being able to sort by status to quickly eyeball the list and determine which branch has available items; we also have use cases similar to those listed by Kristi on 11/8/24, particularly with our hotspots and laptops. -- 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=38122 --- Comment #17 from Lucas Gass (lukeg) <lucas@bywatersolutions.com> --- (In reply to mreid from comment #16)
Please restore ability to sort the holdings table by status. This is particularly an issue for our bibs with large holdings (up to 150 items) across multiple branches. Staff appreciated being able to sort by status to quickly eyeball the list and determine which branch has available items; we also have use cases similar to those listed by Kristi on 11/8/24, particularly with our hotspots and laptops.
Have a look at Bug 37334. Filtering by available and then sorting by branch may solve your problem. -- 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=38122 Koha collecto <koha@collecto.ca> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |koha@collecto.ca -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Steve, OSLRI, USA <sspohn@oslri.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bywater@oslri.net, | |sspohn@oslri.net -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #18 from Kristi <kkrueger@cuyahogalibrary.org> --- While filtering will be welcome, sorting is needed when staff are reviewing more than one status at a time. For example, to see how many copies on a bib are checked out or available to determine how many "live" copies there are as opposed to missing, damaged, etc. Our branch staff were accustomed to using the sort and continue to ask when this functionality will be restored. -- 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=38122 Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tom.rice@cityofcarrollton.c | |om --- Comment #19 from Emily Lamancusa (emlam) <emily.lamancusa@montgomerycountymd.gov> --- *** Bug 39921 has been marked as a duplicate of this bug. *** -- 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=38122 --- Comment #20 from Jonathan Druart <jonathan.druart@gmail.com> --- Created attachment 183789 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=183789&action=edit Bug 38122: Add the ability to group holdings by status This is a quite ugly solution, but that may answer end-user needs. It add the option the group items by status on the bibliographic record detail page. However it will have VERY bad impact on performances for record with a lot of items, as we are going to determine the status of each items of the record. -- 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=38122 --- Comment #21 from Jonathan Druart <jonathan.druart@gmail.com> --- Patch for discussion, it is not ready for inclusion. -- 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=38122 --- Comment #22 from Lucas Gass (lukeg) <lucas@bywatersolutions.com> --- Using k-t-d, I tested some performance using the "Group by status" button, I created items with various status's set: 80 items - 1348ms 200 items - 1463ms 500 items - 1995ms 1000 items - 2635ms -- 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=38122 Baptiste Wojtkowski (bwoj) <baptiste.wojtkowski@biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |baptiste.wojtkowski@biblibr | |e.com --- Comment #23 from Baptiste Wojtkowski (bwoj) <baptiste.wojtkowski@biblibre.com> --- Hi, Is the provided patch supposed to be working or is is just an illustration of what we should do ? I had to tweak a lot to have it working, and I still cannot have it working well I think. I can provide my changes but there is one point I don't get, why do we order by Id at the end of the group search ? I cannot find the place where it is ordered by group after this.
order_by => [ \[ sprintf( "field(me.itemnumber, %s)", join( ', ', map { qq{'$_'} } @item_ids ) ) ] ]
-- 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=38122 --- Comment #24 from Jonathan Druart <jonathan.druart@gmail.com> --- (In reply to Baptiste Wojtkowski (bwoj) from comment #23)
Hi, Is the provided patch supposed to be working or is is just an illustration of what we should do ? I had to tweak a lot to have it working, and I still cannot have it working well I think.
It is supposed to work. Which problems did you face?
I can provide my changes but there is one point I don't get, why do we order by Id at the end of the group search ? I cannot find the place where it is ordered by group after this.
order_by => [ \[ sprintf( "field(me.itemnumber, %s)", join( ', ', map { qq{'$_'} } @item_ids ) ) ] ]
We are ordering by itemnumbers, but using the array @item_ids that defines a specific order. -- 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=38122 --- Comment #25 from Baptiste Wojtkowski (bwoj) <baptiste.wojtkowski@biblibre.com> --- I could not have it sorting the items by status at all :) I faced three different issues : 1 - Since the function that creates the event is called by the event, I had an increasing number of calls to the API, without guarantee of the nature of the last one resolving 2 - Since group_by_status_values is reset at each resolution of the event $(".GroupByStatus").on("click"), I actually never sent the correct url to the API. 3 - WIth this fixed, the API was crashing, I had to change as follows - push @item_ids, $items_rs->search( { _status => $status } )->get_column('itemnumber'); + push @item_ids, $items_rs->search( { status => $status } )->get_column('itemnumber'); -- 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=38122 --- Comment #26 from Baptiste Wojtkowski (bwoj) <baptiste.wojtkowski@biblibre.com> --- Oh wait, I might just have resolved a conflict improperly -- 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=38122 Baptiste Wojtkowski (bwoj) <baptiste.wojtkowski@biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |37334 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37334 [Bug 37334] Cannot filter holdings table by 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=38122 --- Comment #27 from Hammat wele <hammat.wele@inlibro.com> --- Created attachment 184550 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=184550&action=edit Bug 38122: Sort holdings table by status To test: 1. Apply the patch 2. Go to a record details page Example: http://localhost:8081/cgi-bin/koha/catalogue/detail.pl?biblionumber=285 3. Add several items to the record (with different statuses) 3. Click the Status column header in the holdings table to sort ---> items are correctly sorted by status (ascending and descending on repeated clicks) -- 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=38122 Hammat wele <hammat.wele@inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hammat.wele@inlibro.com Status|In Discussion |Needs Signoff -- 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=38122 --- Comment #28 from Jonathan Druart <jonathan.druart@gmail.com> --- (In reply to Hammat wele from comment #27)
Created attachment 184550 [details] [review] Bug 38122: Sort holdings table by status
To test:
1. Apply the patch 2. Go to a record details page Example: http://localhost:8081/cgi-bin/koha/catalogue/detail.pl?biblionumber=285 3. Add several items to the record (with different statuses) 3. Click the Status column header in the holdings table to sort ---> items are correctly sorted by status (ascending and descending on repeated clicks)
Please explain because I don't understand what this patch is supposed to do. -- 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=38122 --- Comment #29 from Jonathan Druart <jonathan.druart@gmail.com> --- (In reply to Hammat wele from comment #27)
Created attachment 184550 [details] [review] Bug 38122: Sort holdings table by status
This patch does not work if you don't have all the items display. Example: I have 223 items, 4 are lost: Show first 20 items order by desc status: https://snipboard.io/9HWmp8.jpg (available first) Show first 20 items order by asc status: https://snipboard.io/vMmn9b.jpg (available first) Show all order by desc status (ok) https://snipboard.io/XZ8uqi.jpg -- 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=38122 --- Comment #30 from Jonathan Druart <jonathan.druart@gmail.com> --- The initial patch is far from perfect and not ready for inclusion (at the minimum tests are missing). If you want to move this forward I would suggest to first help this first patch being pushed, then we can iterate on top of it. -- 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=38122 --- Comment #31 from Jonathan Druart <jonathan.druart@gmail.com> --- Another problem with sorting by status like you did is that it's going to be translated and the ordering won't make any senses. -- 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=38122 Jonathan Druart <jonathan.druart@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |In Discussion -- 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=38122 Bug 38122 depends on bug 33568, which changed state. Bug 33568 Summary: Use the REST API to display items on the staff biblio detail view https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33568 What |Removed |Added ---------------------------------------------------------------------------- Status|Needs documenting |RESOLVED Resolution|--- |FIXED -- 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=38122 Miranda Nero <mnero@oslri.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mnero@oslri.net -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Mathieu Saby <mathsabypro@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mathsabypro@gmail.com --- Comment #32 from Mathieu Saby <mathsabypro@gmail.com> --- We are currently upgrading to Koha 24.11 and have discovered this regression. It must be fixed. -- 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=38122 --- Comment #33 from Jonathan Druart <jonathan.druart@gmail.com> --- (In reply to Mathieu Saby from comment #32)
We are currently upgrading to Koha 24.11 and have discovered this regression. It must be fixed.
(In reply to Jonathan Druart from comment #30)
If you want to move this forward I would suggest to first help this first patch being pushed, then we can iterate on top of it.
-- 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=38122 Christine Lee <chlee@pascolibraries.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |chlee@pascolibraries.org -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Hammat wele <hammat.wele@inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #184550|0 |1 is obsolete| | -- 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=38122 --- Comment #34 from Hammat wele <hammat.wele@inlibro.com> --- Created attachment 187227 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=187227&action=edit Bug 38122: (follow-up) Fix grouping of holdings by status when sorting When 'Group by status' is enabled, sorting on other columns is ignored to ensure that items remain correctly grouped by status. To test: 1. Apply the patch 2. Run yarn build 3. Create a record with multiple itemss having different statuses. 4. Click on «Group by status» button ---> items are grouped by status 5. Sort on other colunms ---> items are still grouped by status 6. Click on «Ungroup by status» button ---> items are no more grouped by 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=38122 --- Comment #35 from Hammat wele <hammat.wele@inlibro.com> --- Created attachment 187410 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=187410&action=edit Bug 38122: (follow-up) Make "Group by status" and "Ungroup by status" translatable -- 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=38122 Jonathan Druart <jonathan.druart@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |p50226253@csdceo.org --- Comment #36 from Jonathan Druart <jonathan.druart@gmail.com> --- *** Bug 40944 has been marked as a duplicate of this bug. *** -- 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=38122 --- Comment #37 from Mathieu Saby <mathsabypro@gmail.com> --- Is that bug ready to be sign off, or still "in discussion"? -- 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=38122 --- Comment #38 from Jonathan Druart <jonathan.druart@gmail.com> --- (In reply to Mathieu Saby from comment #37)
Is that bug ready to be sign off, or still "in discussion"?
A first step would be to test the patch and tell us if it works for you. It's not ready for inclusion yet. -- 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=38122 --- Comment #39 from Mathieu Saby <mathsabypro@gmail.com> --- I'm testing it out. Two related ideas came to me while playing around with the copy table: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41023 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41022 -- 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=38122 --- Comment #40 from Mathieu Saby <mathsabypro@gmail.com> --- I tested on a sandbox, and it seems to work. But honestly, I'm not sure that it really meets the needs of libraries—maybe, maybe not... Other people should test it. As this is not specified in your test plan, could you please clarify how sorting is supposed to be performed by your patch? Based on the value of "_status" returned by the API? Will "available" items appear first (it seems so from my test)?
From a librarian's point of view, this "grouping" does not seem very different from a "sort", except that you can't reverse the order. But if I understand correctly, it would be really technically complicated to control this feature with an arrow in the column header like for the other columns?
-- 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=38122 --- Comment #41 from Jonathan Druart <jonathan.druart@gmail.com> --- (In reply to Mathieu Saby from comment #40)
I tested on a sandbox, and it seems to work. But honestly, I'm not sure that it really meets the needs of libraries—maybe, maybe not... Other people should test it.
What are your needs?
As this is not specified in your test plan, could you please clarify how sorting is supposed to be performed by your patch? Based on the value of "_status" returned by the API? Will "available" items appear first (it seems so from my test)?
available, checked_out, local_use, in_transit, lost, withdrawn, damaged, not_for_loan, on_hold, recalled, in_bundle, restricted
From a librarian's point of view, this "grouping" does not seem very different from a "sort", except that you can't reverse the order. But if I understand correctly, it would be really technically complicated to control this feature with an arrow in the column header like for the other columns?
It can eventually be implemented later, but it's not within the scope of this bug. Any other changes must be on separate bug reports. -- 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=38122 --- Comment #42 from Jess <p50226253@csdceo.org> --- I work in a school Librabry and sorting by status is very helpful for me as I can see all the students who still have copies out under their name at the top of the list. This is helpful because we have many copies of the same manuel. Seeing all the names of the kids who still have their copy all together makes it easier for me to see who i need to chase down.... hope that makes sense -- 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=38122 --- Comment #43 from Jonathan Druart <jonathan.druart@gmail.com> --- (In reply to Jess from comment #42)
I work in a school Librabry and sorting by status is very helpful for me as I can see all the students who still have copies out under their name at the top of the list. This is helpful because we have many copies of the same manuel. Seeing all the names of the kids who still have their copy all together makes it easier for me to see who i need to chase down.... hope that makes sense
Please test the patch and tell us if it works for you. -- 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=38122 --- Comment #44 from Jess <p50226253@csdceo.org> --- I dont know how to test patches... I don't think I have Admin access to our system unfortunetly. I just wanted to share the bug because its been there for a long time now and my higher up said that we have to wait until we go to the next version of KOHA, that was almost a year ago... we're still running on 24.05.05.000 -- 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=38122 Brenda <bowens@washoecounty.us> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bowens@washoecounty.us -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Discussion |Needs Signoff -- 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=38122 --- Comment #45 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 191419 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=191419&action=edit Bug 38122: Add the ability to group holdings by status Merge conflict resolved. -- 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=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #187227|0 |1 is obsolete| | --- Comment #46 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 191420 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=191420&action=edit Bug 38122: (follow-up) Fix grouping of holdings by status when sorting When 'Group by status' is enabled, sorting on other columns is ignored to ensure that items remain correctly grouped by status. To test: 1. Apply the patch 2. Run yarn build 3. Create a record with multiple itemss having different statuses. 4. Click on «Group by status» button ---> items are grouped by status 5. Sort on other colunms ---> items are still grouped by status 6. Click on «Ungroup by status» button ---> items are no more grouped by 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=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #187410|0 |1 is obsolete| | --- Comment #47 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 191421 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=191421&action=edit Bug 38122: (follow-up) Make "Group by status" and "Ungroup by status" translatable -- 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=38122 --- Comment #48 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 191423 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=191423&action=edit Bug 38122: Add the ability to group holdings by status Merge conflict resolved. -- 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=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #183789|0 |1 is obsolete| | Attachment #191419|0 |1 is obsolete| | --- Comment #49 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 191424 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=191424&action=edit Bug 38122: Add the ability to group holdings by status This is a quite ugly solution, but that may answer end-user needs. It add the option the group items by status on the bibliographic record detail page. However it will have VERY bad impact on performances for record with a lot of items, as we are going to determine the status of each items of the record. -- 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=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #191420|0 |1 is obsolete| | --- Comment #50 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 191425 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=191425&action=edit Bug 38122: (follow-up) Fix grouping of holdings by status when sorting When 'Group by status' is enabled, sorting on other columns is ignored to ensure that items remain correctly grouped by status. To test: 1. Apply the patch 2. Run yarn build 3. Create a record with multiple itemss having different statuses. 4. Click on «Group by status» button ---> items are grouped by status 5. Sort on other colunms ---> items are still grouped by status 6. Click on «Ungroup by status» button ---> items are no more grouped by status -- 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=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #191421|0 |1 is obsolete| | --- Comment #51 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 191426 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=191426&action=edit Bug 38122: (follow-up) Make "Group by status" and "Ungroup by status" translatable -- 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=38122 Andrew Fuerste-Henry <andrew@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|koha-bugs@lists.koha-commun |ayoub.glizi-vicioso@inLibro |ity.org |.com CC| |andrew@bywatersolutions.com -- 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=38122 Andrew Fuerste-Henry <andrew@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Failed QA --- Comment #52 from Andrew Fuerste-Henry <andrew@bywatersolutions.com> --- With these patches applied I don't have any items showing in the holdings table on cgi-bin/koha/catalogue/detail.pl -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #53 from Lisette Scheer <lisette@bywatersolutions.com> --- The holdings table won't load for me In the browser inspect tool seeing the following errors: 98 Uncaught SyntaxError: redeclaration of let group_by_status_values detail.pl:2727:13note: Previously declared at line 2708, column 13detail.pl:2708:13 09:26:12.449 Uncaught ReferenceError: build_items_table is not defined <anonymous> http://localhost:8081/cgi-bin/koha/catalogue/detail.pl?biblionumber=6&found1=1:3778 <anonymous> http://localhost:8081/cgi-bin/koha/catalogue/detail.pl?biblionumber=6&found1=1:3773 -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #191423|0 |1 is obsolete| | Attachment #191424|0 |1 is obsolete| | --- Comment #54 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 191529 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=191529&action=edit Bug 38122: Add the ability to group holdings by status The “Group by status” button is not located in the Status column itself. It is located above the table, in the action bar along with Show filters, Select all, and Clear all. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #55 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 191530 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=191530&action=edit Bug 38122: Add the ability to group holdings by status This is a quite ugly solution, but that may answer end-user needs. It add the option the group items by status on the bibliographic record detail page. However it will have VERY bad impact on performances for record with a lot of items, as we are going to determine the status of each items of the record. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #191425|0 |1 is obsolete| | --- Comment #56 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 191531 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=191531&action=edit Bug 38122: (follow-up) Fix grouping of holdings by status when sorting When 'Group by status' is enabled, sorting on other columns is ignored to ensure that items remain correctly grouped by status. To test: 1. Apply the patch 2. Run yarn build 3. Create a record with multiple itemss having different statuses. 4. Click on «Group by status» button ---> items are grouped by status 5. Sort on other colunms ---> items are still grouped by status 6. Click on «Ungroup by status» button ---> items are no more grouped by status -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #191426|0 |1 is obsolete| | --- Comment #57 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 191532 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=191532&action=edit Bug 38122: (follow-up) Make "Group by status" and "Ungroup by status" translatable -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #191530|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Failed QA -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #58 from Jonathan Druart <jonathan.druart@gmail.com> --- Why is this Failed QA? -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #59 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- (In reply to Jonathan Druart from comment #58)
Why is this Failed QA?
Hi! I did some testing and found a few points: 1- Grouping: I noticed that in a few cases some identical statuses aren't grouping together propraly. 2- Sorting: Currently, the groups aren't in alphabetical order. it becomes a bit difficult to navigate. 3- Translations: I spotted a few strings that are currently not translatable. We'll need to wrap those so our international community can use the feature too. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #60 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- (In reply to Jonathan Druart from comment #58)
Why is this Failed QA?
Hi! I did some testing and found a few points: 1- Grouping: I noticed that in a few cases some identical statuses aren't grouping together properly. 2- Sorting: Currently, the groups aren't in alphabetical order. When there is a lot of data, it becomes a bit difficult to navigate for the user 3- Translations: I spotted a few strings that are currently not translatable. We'll need to wrap those so our international community can use the feature too. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #191529|0 |1 is obsolete| | --- Comment #61 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 192992 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=192992&action=edit Bug 38122: Add the ability to group holdings by status This is a quite ugly solution, but that may answer end-user needs. It add the option the group items by status on the bibliographic record detail page. However it will have VERY bad impact on performances for record with a lot of items, as we are going to determine the status of each items of the record. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #191531|0 |1 is obsolete| | --- Comment #62 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 192993 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=192993&action=edit Bug 38122: (follow-up) Fix grouping of holdings by status when sorting When 'Group by status' is enabled, sorting on other columns is ignored to ensure that items remain correctly grouped by status. To test: 1. Apply the patch 2. Run yarn build 3. Create a record with multiple itemss having different statuses. 4. Click on «Group by status» button ---> items are grouped by status 5. Sort on other colunms ---> items are still grouped by status 6. Click on «Ungroup by status» button ---> items are no more grouped by status -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #191532|0 |1 is obsolete| | --- Comment #63 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 192994 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=192994&action=edit Bug 38122: (follow-up) Make "Group by status" and "Ungroup by status" translatable -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #64 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 192995 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=192995&action=edit Bug 38122: (follow-up) Correct item regrouping behavior -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #65 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- (In reply to Ayoub Glizi-Vicioso from comment #60)
(In reply to Jonathan Druart from comment #58)
Why is this Failed QA?
Hi!
I did some testing and found a few points:
1- Grouping: I noticed that in a few cases some identical statuses aren't grouping together properly.
2- Sorting: Currently, the groups aren't in alphabetical order. When there is a lot of data, it becomes a bit difficult to navigate for the user
3- Translations: I spotted a few strings that are currently not translatable. We'll need to wrap those so our international community can use the feature too.
After reconsidering my previous comment about sorting the statuses alphabetically, I think it would actually make more sense to order them by availability priority instead of alphabetical order. Since this concerns item statuses in Koha, a logical progression based on availability would likely be more useful for staff.(In reply to Ayoub Glizi-Vicioso from comment #60)
(In reply to Jonathan Druart from comment #58)
Why is this Failed QA?
Hi!
I did some testing and found a few points:
1- Grouping: I noticed that in a few cases some identical statuses aren't grouping together properly.
2- Sorting: Currently, the groups aren't in alphabetical order. When there is a lot of data, it becomes a bit difficult to navigate for the user
3- Translations: I spotted a few strings that are currently not translatable. We'll need to wrap those so our international community can use the feature too.
After reconsidering my previous comment about sorting the statuses alphabetically, I think it would actually make more sense to order them by availability priority instead of alphabetical order. Since this concerns item statuses in Koha, a logical progression based on availability would likely be more useful for staff. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #66 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- (In reply to Ayoub Glizi-Vicioso from comment #60)
(In reply to Jonathan Druart from comment #58)
Why is this Failed QA?
Hi!
I did some testing and found a few points:
1- Grouping: I noticed that in a few cases some identical statuses aren't grouping together properly.
2- Sorting: Currently, the groups aren't in alphabetical order. When there is a lot of data, it becomes a bit difficult to navigate for the user
3- Translations: I spotted a few strings that are currently not translatable. We'll need to wrap those so our international community can use the feature too.
After reconsidering my previous comment about sorting the statuses alphabetically, I think it would actually make more sense to order them by availability priority instead of alphabetical order. Since this concerns item statuses in Koha, a logical progression based on availability would likely be more useful for staff. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #192995|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #192995|1 |0 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #192995|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #192995|1 |0 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #192992|0 |1 is obsolete| | --- Comment #67 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 193149 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=193149&action=edit Bug 38122: Add the ability to group holdings by status This is a quite ugly solution, but that may answer end-user needs. It add the option the group items by status on the bibliographic record detail page. However it will have VERY bad impact on performances for record with a lot of items, as we are going to determine the status of each items of the record. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #192993|0 |1 is obsolete| | --- Comment #68 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 193150 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=193150&action=edit Bug 38122: (follow-up) Fix grouping of holdings by status when sorting When 'Group by status' is enabled, sorting on other columns is ignored to ensure that items remain correctly grouped by status. To test: 1. Apply the patch 2. Run yarn build 3. Create a record with multiple itemss having different statuses. 4. Click on «Group by status» button ---> items are grouped by status 5. Sort on other colunms ---> items are still grouped by status 6. Click on «Ungroup by status» button ---> items are no more grouped by status -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #192994|0 |1 is obsolete| | --- Comment #69 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 193151 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=193151&action=edit Bug 38122: (follow-up) Make "Group by status" and "Ungroup by status" translatable -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #192995|0 |1 is obsolete| | --- Comment #70 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 193152 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=193152&action=edit Bug 38122: (follow-up) Correct item regrouping behavior -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #71 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 193153 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=193153&action=edit Bug 38122: Fix server error when handling malformed request parameters -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #72 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Note: (In reply to Ayoub Glizi-Vicioso from comment #71)
Created attachment 193153 [details] [review] Bug 38122: Fix server error when handling malformed request parameters
Note: If you encounter a 400 error during status grouping, you might need to run 'yarn api:bundle' to update the API documentation. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Bug 38122 depends on bug 37334, which changed state. Bug 37334 Summary: Cannot filter holdings table by status https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37334 What |Removed |Added ---------------------------------------------------------------------------- Status|Needs documenting |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #193149|0 |1 is obsolete| | --- Comment #73 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 195227 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=195227&action=edit Bug 38122: Add the ability to group holdings by status This is a quite ugly solution, but that may answer end-user needs. It add the option the group items by status on the bibliographic record detail page. However it will have VERY bad impact on performances for record with a lot of items, as we are going to determine the status of each items of the record. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #193150|0 |1 is obsolete| | --- Comment #74 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 195228 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=195228&action=edit Bug 38122: (follow-up) Fix grouping of holdings by status when sorting When 'Group by status' is enabled, sorting on other columns is ignored to ensure that items remain correctly grouped by status. To test: 1. Apply the patch 2. Run yarn build 3. Create a record with multiple itemss having different statuses. 4. Click on «Group by status» button ---> items are grouped by status 5. Sort on other colunms ---> items are still grouped by status 6. Click on «Ungroup by status» button ---> items are no more grouped by status -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #193151|0 |1 is obsolete| | --- Comment #75 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 195229 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=195229&action=edit Bug 38122: (follow-up) Make "Group by status" and "Ungroup by status" translatable -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #193152|0 |1 is obsolete| | --- Comment #76 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 195230 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=195230&action=edit Bug 38122: (follow-up) Correct item regrouping behavior -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #193153|0 |1 is obsolete| | --- Comment #77 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 195231 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=195231&action=edit Bug 38122: Fix server error when handling malformed request parameters -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #78 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 195232 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=195232&action=edit Bug 38122: Improve items sorting logic in bibliographic details -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Needs Signoff --- Comment #79 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Note: If you encounter a 400 error during status grouping, you might need to run 'yarn api:bundle' to update the API documentation or/and restart plack (if installed). -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 David Nind <david@davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |david@davidnind.com Status|Needs Signoff |Patch doesn't apply --- Comment #80 from David Nind <david@davidnind.com> --- The patch no longer applies 8-(... /kohadevbox/perl-git-bz/bin/git-bz apply 38122 📋 Bug 38122 - Cannot sort holdings table by status • 195227 - Bug 38122: Add the ability to group holdings by status • 195228 - Bug 38122: (follow-up) Fix grouping of holdings by status when sorting • 195229 - Bug 38122: (follow-up) Make "Group by status" and "Ungroup by status" translatable • 195230 - Bug 38122: (follow-up) Correct item regrouping behavior • 195231 - Bug 38122: Fix server error when handling malformed request parameters • 195232 - Bug 38122: Improve items sorting logic in bibliographic details Apply? [(y)es, (n)o, (i)nteractive] y Preparing 6 patch(es): ✓ Prepared 6 patch(es) Applying 6 patch(es): Patch application failed for attachment 195227 - Bug 38122: Add the ability to group holdings by status -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Patch doesn't apply |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #195227|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #195228|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #195229|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #195230|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #195231|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #195232|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #81 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 195868 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=195868&action=edit Bug 38122: Add the ability to group holdings by status This is a quite ugly solution, but that may answer end-user needs. It add the option the group items by status on the bibliographic record detail page. However it will have VERY bad impact on performances for record with a lot of items, as we are going to determine the status of each items of the record. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #82 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 195869 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=195869&action=edit Bug 38122: (follow-up) Fix grouping of holdings by status when sorting When 'Group by status' is enabled, sorting on other columns is ignored to ensure that items remain correctly grouped by status. To test: 1. Apply the patch 2. Run yarn build 3. Create a record with multiple itemss having different statuses. 4. Click on «Group by status» button ---> items are grouped by status 5. Sort on other colunms ---> items are still grouped by status 6. Click on «Ungroup by status» button ---> items are no more grouped by status -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #83 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 195870 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=195870&action=edit Bug 38122: (follow-up) Make "Group by status" and "Ungroup by status" translatable Patch from commit eda77f1 -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #84 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 195871 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=195871&action=edit Bug 38122: (follow-up) Correct item regrouping behavior Patch from commit 5670bb0 -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #85 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 195872 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=195872&action=edit Bug 38122: Fix server error when handling malformed request parameters Patch from commit 2b4f439 -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #86 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 195873 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=195873&action=edit Bug 38122: Improve items sorting logic in bibliographic details Patch from commit c70e608 -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #87 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 195874 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=195874&action=edit Bug 38122: Improve column filtering and grouping logic Patch from commit f700460 -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #88 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- (In reply to David Nind from comment #80)
The patch no longer applies 8-(...
/kohadevbox/perl-git-bz/bin/git-bz apply 38122
📋 Bug 38122 - Cannot sort holdings table by status
• 195227 - Bug 38122: Add the ability to group holdings by status • 195228 - Bug 38122: (follow-up) Fix grouping of holdings by status when sorting • 195229 - Bug 38122: (follow-up) Make "Group by status" and "Ungroup by status" translatable • 195230 - Bug 38122: (follow-up) Correct item regrouping behavior • 195231 - Bug 38122: Fix server error when handling malformed request parameters • 195232 - Bug 38122: Improve items sorting logic in bibliographic details
Apply? [(y)es, (n)o, (i)nteractive] y
Preparing 6 patch(es): ✓ Prepared 6 patch(es)
Applying 6 patch(es):
Patch application failed for attachment 195227 [details] [review] - Bug 38122: Add the ability to group holdings by status
Merge conflicts have been resolved. I also applied improvements to the filtering and grouping logic. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #89 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- (In reply to Ayoub Glizi-Vicioso from comment #79)
Note: If you encounter a 400 error during status grouping, you might need to run 'yarn api:bundle' to update the API documentation or/and restart plack (if installed).
This still stands. The note remains valid: running 'yarn api:bundle' and/or restarting Plack may be required to avoid the 400 error when grouping by status. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Brendan Lawlor <blawlor@clamsnet.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |blawlor@clamsnet.org --- Comment #90 from Brendan Lawlor <blawlor@clamsnet.org> --- In testing I noticed a couple of things. Not not blockers, but worth noting. Once you click Group by status you can not change the sort by until you click Ungroup by status. It would be nice if you could still sort by columns while you are grouped by status. If you have many items on a bib, there can be a sort of infitie scrolling glitch caused by the sticky headers. This glitch is still there without the patch, but is worse with the grouping. The scrolling glitch is resolved by bug 42003, so I am signing off on this. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Brendan Lawlor <blawlor@clamsnet.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Signed Off -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Brendan Lawlor <blawlor@clamsnet.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #195868|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Brendan Lawlor <blawlor@clamsnet.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #195869|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Brendan Lawlor <blawlor@clamsnet.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #195870|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Brendan Lawlor <blawlor@clamsnet.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #195871|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Brendan Lawlor <blawlor@clamsnet.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #195872|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Brendan Lawlor <blawlor@clamsnet.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #195873|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Brendan Lawlor <blawlor@clamsnet.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #195874|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #91 from Brendan Lawlor <blawlor@clamsnet.org> --- Created attachment 196593 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=196593&action=edit Bug 38122: Add the ability to group holdings by status This is a quite ugly solution, but that may answer end-user needs. It add the option the group items by status on the bibliographic record detail page. However it will have VERY bad impact on performances for record with a lot of items, as we are going to determine the status of each items of the record. Signed-off-by: Brendan Lawlor <blawlor@clamsnet.org> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #92 from Brendan Lawlor <blawlor@clamsnet.org> --- Created attachment 196594 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=196594&action=edit Bug 38122: (follow-up) Fix grouping of holdings by status when sorting When 'Group by status' is enabled, sorting on other columns is ignored to ensure that items remain correctly grouped by status. To test: 1. Apply the patch 2. Run yarn build 3. Create a record with multiple itemss having different statuses. 4. Click on «Group by status» button ---> items are grouped by status 5. Sort on other colunms ---> items are still grouped by status 6. Click on «Ungroup by status» button ---> items are no more grouped by status Signed-off-by: Brendan Lawlor <blawlor@clamsnet.org> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #93 from Brendan Lawlor <blawlor@clamsnet.org> --- Created attachment 196595 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=196595&action=edit Bug 38122: (follow-up) Make "Group by status" and "Ungroup by status" translatable Signed-off-by: Brendan Lawlor <blawlor@clamsnet.org> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #94 from Brendan Lawlor <blawlor@clamsnet.org> --- Created attachment 196596 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=196596&action=edit Bug 38122: (follow-up) Correct item regrouping behavior Signed-off-by: Brendan Lawlor <blawlor@clamsnet.org> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #95 from Brendan Lawlor <blawlor@clamsnet.org> --- Created attachment 196597 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=196597&action=edit Bug 38122: Fix server error when handling malformed request parameters Signed-off-by: Brendan Lawlor <blawlor@clamsnet.org> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #96 from Brendan Lawlor <blawlor@clamsnet.org> --- Created attachment 196598 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=196598&action=edit Bug 38122: Improve items sorting logic in bibliographic details Signed-off-by: Brendan Lawlor <blawlor@clamsnet.org> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #97 from Brendan Lawlor <blawlor@clamsnet.org> --- Created attachment 196599 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=196599&action=edit Bug 38122: Improve column filtering and grouping logic Signed-off-by: Brendan Lawlor <blawlor@clamsnet.org> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Lucas Gass (lukeg) <lucas@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- QA Contact|testopia@bugs.koha-communit |lucas@bywatersolutions.com |y.org | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Jonathan Druart <jonathan.druart@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Failed QA --- Comment #98 from Jonathan Druart <jonathan.druart@gmail.com> --- 1. I like the UI, but the code seems too complicated IMO. a. Duplicating the status logic at the DB level (order by) is a bad idea. b. The coded value (01 for On hold, 00 for Available) it not a good pattern c. Before following up on the other remarks, please explain why the first patch is not working correctly. I feel like we should do baby steps here instead of massive changes not covered by tests. 2. prove xt/tt_kohaTable_tidy.t xt/tt_kohaTable_tidy.t .. 1/879 # Failed test 'koha-tmpl/intranet-tmpl/prog/en/includes/html_helpers/tables/items/catalogue_detail.inc has 'kohaTable' instances in a <script> tag with Template::Toolkit tags. You have reverted most of the changes done on bug 41566. 3. Missing tests 4. I don't think we need to group_by_status in the global swagger.yaml. What's the reason? api/v1/swagger/swagger.yaml + group_by_status: 5. - ajax: { url: item_table_url }, + ajax: { url: "/api/v1/biblios/[% biblio.biblionumber | uri %]/items?" + group_by_status() }, => Then the item_table_url is not longer used and can be removed at 303 let item_table_url = `/api/v1/biblios/${biblionumber}/items?`; 6. Performances - did you benchmark this approach on a biblio with lot of items? 7. Why is filter_out_restricted ordering items? I don't think it should. 8. You removed a FIXME, did you fix it? - # FIXME We need to order_by serial.publisheddate if we have _order_by=+me.serial_issue_number 9. Did you see bug 41254 and bug 41602? -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Jonathan Druart <jonathan.druart@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- QA Contact|lucas@bywatersolutions.com |jonathan.druart@gmail.com -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #99 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Thanks for the feedback. About the initial patch: the issue I ran into was that the grouping wasn’t always working correctly. For example, some statuses were properly grouped, but then the same status could appear again later on its own. I also noticed filtering issues — for instance, when filtering on “recalled” (if I remember correctly), all statuses were shown, and when filtering on “available”, nothing was returned. Regarding group_by_status in swagger.yaml, you’re right — I can move it back to where it was. I was just trying to align it with the other parameters. For bug 41566, the revert was likely caused while resolving a merge conflict. I hadn’t seen bugs 41254 and 41602, sorry about that. I’ll check them. I just noticed that I was trying to fix everything in this patch, sorry again about that. I can revert the changes I made here and focus this patch only on the grouping issue, then handle the filtering bug in an existing Bugzilla or a new one, and open another Bugzilla for the UI changes if that makes more sense. I’ll go over all the points you mentioned, but it might take some time before I can come back with an updated version. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Jonathan Druart <jonathan.druart@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Jonathan Druart <jonathan.druart@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #196593|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Jonathan Druart <jonathan.druart@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #196594|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Jonathan Druart <jonathan.druart@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #196595|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Jonathan Druart <jonathan.druart@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #196596|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Jonathan Druart <jonathan.druart@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #196597|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Jonathan Druart <jonathan.druart@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #196598|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Jonathan Druart <jonathan.druart@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #196599|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #100 from Jonathan Druart <jonathan.druart@gmail.com> --- Created attachment 197184 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=197184&action=edit Bug 38122: Add the ability to group holdings by status This is a quite ugly solution, but that may answer end-user needs. It add the option the group items by status on the bibliographic record detail page. However it will have VERY bad impact on performances for record with a lot of items, as we are going to determine the status of each items of the record. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Jonathan Druart <jonathan.druart@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|ayoub.glizi-vicioso@inLibro |jonathan.druart@gmail.com |.com | QA Contact|jonathan.druart@gmail.com |testopia@bugs.koha-communit | |y.org --- Comment #101 from Jonathan Druart <jonathan.druart@gmail.com> --- I have rebased my original patch, and it still seems to work as expected. Please test and let me know if it is not working correctly. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Jonathan Druart <jonathan.druart@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #197184|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #102 from Jonathan Druart <jonathan.druart@gmail.com> --- Created attachment 197185 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=197185&action=edit Bug 38122: Add the ability to group holdings by status This is a quite ugly solution, but that may answer end-user needs. It add the option the group items by status on the bibliographic record detail page. However it will have VERY bad impact on performances for record with a lot of items, as we are going to determine the status of each items of the record. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #103 from Jonathan Druart <jonathan.druart@gmail.com> --- (In reply to Ayoub Glizi-Vicioso from comment #99)
Thanks for the feedback.
About the initial patch: the issue I ran into was that the grouping wasn’t always working correctly. For example, some statuses were properly grouped, but then the same status could appear again later on its own. I also noticed filtering issues — for instance, when filtering on “recalled” (if I remember correctly), all statuses were shown, and when filtering on “available”, nothing was returned.
This is a bug in main, I have opened bug 42349 (Incorrect filter by recalls). -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Jonathan Druart <jonathan.druart@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=42349 -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Kathleen <kkosiec@santabarbaraca.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kkosiec@santabarbaraca.gov -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #197185|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #104 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 197533 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=197533&action=edit Bug 38122: Add the ability to group holdings by status This is a quite ugly solution, but that may answer end-user needs. It add the option the group items by status on the bibliographic record detail page. However it will have VERY bad impact on performances for record with a lot of items, as we are going to determine the status of each items of the record. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #105 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- Created attachment 197534 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=197534&action=edit Bug 38122: Tidy and Minor cleanup in catalogue_detail.inc (replace Template Toolkit leftovers) 1- perl `misc/devel/tidy.pl` executed. 2- Fixes xt/tt_kohaTable_tidy.t failure triggered by catalogue_detail.inc. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ayoub.glizi-vicioso@inLibro | |.com --- Comment #106 from Ayoub Glizi-Vicioso <ayoub.glizi-vicioso@inLibro.com> --- I came across this issue, that is not deal breaking but is worth noting: https://snipboard.io/AGCdJY.jpg When grouping statuses,It would be useful to group sub-statuses as well.. This is the solution I am proposing: diff --git a/Koha/REST/V1/Biblios.pm b/Koha/REST/V1/Biblios.pm index 4c45319b3c..f5bc737313 100644 --- a/Koha/REST/V1/Biblios.pm +++ b/Koha/REST/V1/Biblios.pm @@ -271,12 +271,21 @@ sub get_items { $items_rs = $items_rs->filter_by_bookable if $bookable_only; if ($group_by_status) { + my $sub_status_order = [ + { -asc => 'me.itemlost' }, + { -asc => 'me.notforloan' }, + { -desc => 'me.restricted' } + ]; + my @item_ids; for my $status ( qw( available checked_out local_use in_transit lost withdrawn damaged not_for_loan on_hold recalled in_bundle restricted ) ) { - push @item_ids, $items_rs->search( { _status => $status } )->get_column('itemnumber'); + push @item_ids, $items_rs->search( + { _status => $status }, + { order_by => $sub_status_order } + )->get_column('itemnumber'); } I ran benchmark tests using ApacheBench for the same bibliographic record (~500 items displayed on a single page), with and without this sub-status filter applied. I observed no significant performance difference between both cases: Without sub-status filtering: - Average response time: ~10 254 ms - Longest request: ~13.0 s With sub-status filtering: - Average response time: ~10 208 ms - Longest request: ~13.6 s The differences observed are within normal variance and do not indicate any measurable performance impact. If this addition is considered relevant, it can be included; otherwise, it is not necessary. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #107 from Jonathan Druart <jonathan.druart@gmail.com> --- (In reply to Ayoub Glizi-Vicioso from comment #106)
If this addition is considered relevant, it can be included; otherwise, it is not necessary.
As stated previously already, I think we should go with this simple implementation first, then iterate on top of it. 26.05 is coming soon. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #108 from David Nind <david@davidnind.com> --- Could we get a consolidated test plan for this? There are so many comments etc, that I'm being lazy - not sure what to test or how. Thanks! -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #109 from Jonathan Druart <jonathan.druart@gmail.com> --- (In reply to David Nind from comment #108)
Could we get a consolidated test plan for this?
There are so many comments etc, that I'm being lazy - not sure what to test or how.
Thanks!
On the holdings table it's not possible to sort by status. The patches proposes to have a new "group by status" button at the top of the table, to group items by their status. The idea is to have a bibliographic record with some items having different status. If you use the new "group by status" button the items will then be grouped together in the table. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #110 from David Nind <david@davidnind.com> --- Created attachment 197775 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=197775&action=edit Screenshots - Group by status Had a go at testing, some questions and observations: 1. How is the grouping by status expected to work - alphabetical? (Can't really work out how it is ordered.) 2. When you click on "Group by status": - Filters are shown, but the link above the table is still "Show filters" - "Group by status" changes to "Ungroup by status" - Additional space is needed between the icon and "Ungroup by status" 3. If I click "Ungroup by status": - Filters are still shown for columns - Additional space is needed between the icon and "Group by status" I've attached a PDF with screenshots: 1 - New group by status option 2 - Group by status clicked 3 - After clicking Ungroup by status Testing notes (using KTD): 1. Use a record with several items. (I used Intermediate Perl, biblionumber = 126) 2. Use the "Add multiple copies of this item" when adding items to add items with different statuses (New > New item): - Withdrawn status: Withdrawn - Lost status: Missing - Damaged status: Damaged - Not for loan: Not for loan 3. Checkout some items to some patrons 4. Place an item on hold for a patron and check it in so that it is waiting for pickup 5. Apply the patch 6. yarn api:bundle (not sure if this is required) 7. yarn build (not sure if this is required) 8. Restart everything: restart_all 9. Clear the browser cache 10. Go to the record you added items for with different statuses 11. Note the "Group by status" link above the holdings table in the holdings tab (Show filters - Select all - Clear all - Group by status) 12. Clicking "Group by status" will order/group the items by the values in the status column (note: not in alphabetical order by status, but items with the same status are grouped together) -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #111 from Jonathan Druart <jonathan.druart@gmail.com> --- Created attachment 197777 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=197777&action=edit Bug 38122: Keep filters visibility Patch from commit 76d06f8 -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #112 from Jonathan Druart <jonathan.druart@gmail.com> --- Created attachment 197778 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=197778&action=edit Bug 38122: Add space before the Group/Ungroup links Patch from commit ea45864 -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #113 from Jonathan Druart <jonathan.druart@gmail.com> --- (In reply to David Nind from comment #110)
Had a go at testing, some questions and observations:
Thanks, David!
1. How is the grouping by status expected to work - alphabetical? (Can't really work out how it is ordered.)
This is the order: available checked_out local_use in_transit lost withdrawn damaged not_for_loan on_hold recalled in_bundle restricted Can be adjusted if we need something better.
2. When you click on "Group by status": - Filters are shown, but the link above the table is still "Show filters" - "Group by status" changes to "Ungroup by status" - Additional space is needed between the icon and "Ungroup by status"
3. If I click "Ungroup by status": - Filters are still shown for columns - Additional space is needed between the icon and "Group by status"
Fixed in "Keep filters visibility" and "Add space before the Group/Ungroup links" -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 David Nind <david@davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Signed Off -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 David Nind <david@davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #197533|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 David Nind <david@davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #197534|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 David Nind <david@davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #197777|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 David Nind <david@davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #197778|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #114 from David Nind <david@davidnind.com> --- Created attachment 197813 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=197813&action=edit Bug 38122: Add the ability to group holdings by status This is a quite ugly solution, but that may answer end-user needs. It add the option the group items by status on the bibliographic record detail page. However it will have VERY bad impact on performances for record with a lot of items, as we are going to determine the status of each items of the record. Signed-off-by: David Nind <david@davidnind.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #115 from David Nind <david@davidnind.com> --- Created attachment 197814 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=197814&action=edit Bug 38122: Tidy and Minor cleanup in catalogue_detail.inc (replace Template Toolkit leftovers) 1- perl `misc/devel/tidy.pl` executed. 2- Fixes xt/tt_kohaTable_tidy.t failure triggered by catalogue_detail.inc. Signed-off-by: David Nind <david@davidnind.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #116 from David Nind <david@davidnind.com> --- Created attachment 197815 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=197815&action=edit Bug 38122: Keep filters visibility Signed-off-by: David Nind <david@davidnind.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #117 from David Nind <david@davidnind.com> --- Created attachment 197816 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=197816&action=edit Bug 38122: Add space before the Group/Ungroup links Signed-off-by: David Nind <david@davidnind.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 David Nind <david@davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Text to go in the| |This restores the "Group by release notes| |status" option to the | |holdings table for a record | |in the staff interface | |(after the Show filters, | |Select all, and Clear all | |options). | | | |Clicking "Group by status" | |sorts the items by the | |status column.^ | | | |Clicking "Ungroup by | |status" resets the holdings | |table. | | | |In combination with the | |filters option this | |provides several ways for | |staff to quickly scan and | |organize the items by | |status. | | | |+ Order for grouping items | |is: | | | |* Available (available) | |* Checked out (checked_out) | |* Local use (local_use) | |* In transit (in_transit) | |* Lost (lost) | |* Withdrawn (withdrawn) | |* Damaged (damaged) | |* Not for loan | |(not_for_loan) | |* On hold (on_hold) | |* Recalled (recalled) | |* In bundle (in_bundle) | |* Restricted (restricted) -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Lucas Gass (lukeg) <lucas@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Passed QA -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Lucas Gass (lukeg) <lucas@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #197813|0 |1 is obsolete| | Attachment #197814|0 |1 is obsolete| | Attachment #197815|0 |1 is obsolete| | Attachment #197816|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #118 from Lucas Gass (lukeg) <lucas@bywatersolutions.com> --- Created attachment 199778 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=199778&action=edit Bug 38122: Add the ability to group holdings by status This is a quite ugly solution, but that may answer end-user needs. It add the option the group items by status on the bibliographic record detail page. However it will have VERY bad impact on performances for record with a lot of items, as we are going to determine the status of each items of the record. Signed-off-by: David Nind <david@davidnind.com> Signed-off-by: Lucas Gass <lucas@bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #119 from Lucas Gass (lukeg) <lucas@bywatersolutions.com> --- Created attachment 199779 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=199779&action=edit Bug 38122: Tidy and Minor cleanup in catalogue_detail.inc (replace Template Toolkit leftovers) 1- perl `misc/devel/tidy.pl` executed. 2- Fixes xt/tt_kohaTable_tidy.t failure triggered by catalogue_detail.inc. Signed-off-by: David Nind <david@davidnind.com> Signed-off-by: Lucas Gass <lucas@bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #120 from Lucas Gass (lukeg) <lucas@bywatersolutions.com> --- Created attachment 199780 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=199780&action=edit Bug 38122: Keep filters visibility Signed-off-by: David Nind <david@davidnind.com> Signed-off-by: Lucas Gass <lucas@bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #121 from Lucas Gass (lukeg) <lucas@bywatersolutions.com> --- Created attachment 199781 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=199781&action=edit Bug 38122: Add space before the Group/Ungroup links Signed-off-by: David Nind <david@davidnind.com> Signed-off-by: Lucas Gass <lucas@bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Lucas Gass (lukeg) <lucas@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- QA Contact|testopia@bugs.koha-communit |lucas@bywatersolutions.com |y.org | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Pedro Amorim (ammopt) <pedro.amorim@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Passed QA |Failed QA CC| |pedro.amorim@openfifth.co.u | |k --- Comment #122 from Pedro Amorim (ammopt) <pedro.amorim@openfifth.co.uk> --- I stand with Joubu, and would prefer to not push this, not as is anyway, but understand the real world need for it (especially as it was something that existed before). Regardless, I'm failing QA for now because I feel like we at least need tests written for Biblios::get_items. The 'ideal' dev plan here I believe would be something like: 1) Identify all use cases where an item's computed status needs to be updated (AddIssue, AddReturn, Transfer::transit, Transfer::receive, and more) 2)Store it in the database 3) Get sorting for free and a multitude of other performance improvements -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Jonathan Druart <jonathan.druart@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Passed QA -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #123 from Jonathan Druart <jonathan.druart@gmail.com> --- Created attachment 200046 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=200046&action=edit Bug 38122: Add tests Patch from commit b0aea14 -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Pedro Amorim (ammopt) <pedro.amorim@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Version(s)| |26.11.00 released in| | Status|Passed QA |Pushed to main -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #124 from Pedro Amorim (ammopt) <pedro.amorim@openfifth.co.uk> --- Thanks everyone! Pushed to main for 26.11! -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Lucas Gass (lukeg) <lucas@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Pushed to main |Needs documenting --- Comment #125 from Lucas Gass (lukeg) <lucas@bywatersolutions.com> --- Enhancement, no 26.05.x backport -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 Jonathan Druart <jonathan.druart@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |42979 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42979 [Bug 42979] api/v1/biblios.t on MySQL 8 -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38122 --- Comment #126 from Jonathan Druart <jonathan.druart@gmail.com> --- After we "group by status", the sort icons are still available in the column's headers. Once we click on one of them it's no longer possible to group by status (or it would be a second order by clause). The query still contains the group_by_status flag: ?group_by_status=1&_page=1&_per_page=20&_match=contains&_order_by=-me.collection_code This is not correct. Should we remove the group_by_status if we request a sort on a column? Feel free to open a follow-up bug report for suggestions. Also please commit time for testing a patch, I don't want to wait one year (the first patch here has been originally submitted one YEAR ago!) -- You are receiving this mail because: You are watching all bug changes.
participants (1)
-
bugzilla-daemon@bugs.koha-community.org