When testing MCL sorting in the request app, testers encountered a situation when sorting by barcode where requests without a user barcode were not sorting correctly (interspersed with other request where a patron barcode value was present.
Steps to Reproduce:
- Log into some Juniper Bugfest
- Go to the Requests app
- Filter by request status "Closed - Cancelled"
- Attempt to sort the results descending by "Requester Barcode"
Results are sorted, descending, by requester barcode, with empty values sorted appropriately.
Records with empty requester barcode values are intermixed with records where a requester barcode is present.
May be worth taking a look at the general sort accuracy, as well, just to make sure.
NOTE: Per discussion on
CIRCSTORE-286, this is being caused by a mismatch in what the /circulation/requests endpoint returns and what /request-storage/requests returns and can query on. /circulation/requests takes the response from /request-storage/requests and augments it with current information from /users (in this case), but the record sorting is done by the storage module, which uses it's locally-stored copies of the data. Until data sync is developed for user data in requests, there is no way to resolve this issue.