Libraries are reporting that patrons are very confused during self-checkout. The problem is they are expecting the list of checkouts to be in the order they checked out the items ( first checkout on the bottom, last item checked out on top ). However, the checkouts table is sorted by title ( ascending ) then due date ( descending ). This is not intuitive.
Created attachment 40242 [details] [review] Bug 14404 - Checkouts default sort order for Self Checkout (SCO) confusing for patrons Libraries are reporting that patrons are very confused during self-checkout. The problem is they are expecting the list of checkouts to be in the order they checked out the items ( first checkout on the bottom, last item checked out on top ). However, the checkouts table is sorted by title ( ascending ) then due date ( descending ). This is not intuitive. Test Plan: 1) Enable Koha's self checkout 2) Use the SCO to check out a random assortment of items, make sure you don't check them out in alphabetical order 3) Note the order of the items in the list is not based on the order you checked them out in 4) Apply this patch 5) Refresh the page 6) Note the items are now in the order you checked them out with the last on top and the first on bottom
Created attachment 40249 [details] [review] Bug 14404 - Checkouts default sort order for Self Checkout (SCO) confusing for patrons Libraries are reporting that patrons are very confused during self-checkout. The problem is they are expecting the list of checkouts to be in the order they checked out the items ( first checkout on the bottom, last item checked out on top ). However, the checkouts table is sorted by title ( ascending ) then due date ( descending ). This is not intuitive. Test Plan: 1) Enable Koha's self checkout 2) Use the SCO to check out a random assortment of items, make sure you don't check them out in alphabetical order 3) Note the order of the items in the list is not based on the order you checked them out in 4) Apply this patch 5) Refresh the page 6) Note the items are now in the order you checked them out with the last on top and the first on bottom Signed-off-by: Mark Tompsett <mtompset@hotmail.com>
Sorry but I think it's better to keep consistency between "no-show" and "nosort".
Created attachment 40832 [details] [review] Bug 14404 [QA Followup] - Rename class nosort to no-sort for readability and consistency
Created attachment 40861 [details] [review] Bug 14404 - Checkouts default sort order for Self Checkout (SCO) confusing for patrons Libraries are reporting that patrons are very confused during self-checkout. The problem is they are expecting the list of checkouts to be in the order they checked out the items ( first checkout on the bottom, last item checked out on top ). However, the checkouts table is sorted by title ( ascending ) then due date ( descending ). This is not intuitive. Test Plan: 1) Enable Koha's self checkout 2) Use the SCO to check out a random assortment of items, make sure you don't check them out in alphabetical order 3) Note the order of the items in the list is not based on the order you checked them out in 4) Apply this patch 5) Refresh the page 6) Note the items are now in the order you checked them out with the last on top and the first on bottom Signed-off-by: Mark Tompsett <mtompset@hotmail.com> Signed-off-by: Jonathan Druart <jonathan.druart@koha-community.org>
Created attachment 40862 [details] [review] Bug 14404: Rename class no-show to noshow for consistency with nosort Signed-off-by: Jonathan Druart <jonathan.druart@koha-community.org>
(In reply to Kyle M Hall from comment #4) > Created attachment 40832 [details] [review] [review] > Bug 14404 [QA Followup] - Rename class nosort to no-sort for readability and > consistency I am against this patch, the "nosort" already exists in other places. Tomas, either 1/ you push my patch to get consistency between nosort (existented before this patch and in other places) or 2/ don't push it for readability and we will need to fix the existent occurrences of nosort.
Patches pushed to master. Thanks Kyle and Jonathan!
Pushed to 3.20.x will be in 3.20.3
Pushed to 3.18.x, will be in 3.18.10.
*** Bug 12014 has been marked as a duplicate of this bug. ***