Incorrect format of the missing match in the call number browse
Description
Steps to Reproduce:
Navigate to Inventory-> Call number browse
Browse by QM21 V550 1704
Expected Results: As in Lotus release:
Actual Results:
Additional information: The following call numbers are ordered in expected order but the browsed call number is translated into shelving order and the matching call number is not recognized.
*This ticket will also cover adjusting requests that UI sends to backend so shelfKey is not used. That covers following scenarios: 1. User starts call number browse: query: callNumber>="HN59 .T39 2014" or callNumber<"HN59 .T39 2014" 2. User clicks on one of the rows: (callNumber=HN 259 T39 42014 C 11) sortby title 3. User clicks Previous button: callNumber < "HN 259 S84 C 11" 4. User clicks Next button : callNumber > "HN 259 S780 C 11"*
Seems like not all changes were included in the release. In 9.1.7 were released changes only from here but we also have changes here. can you take a look? cc:
Steps to Reproduce:
Navigate to Inventory-> Call number browse
Browse by QM21 V550 1704
Expected Results:
As in Lotus release:
Actual Results:
Additional information:
The following call numbers are ordered in expected order but the browsed call number is translated into shelving order and the matching call number is not recognized.
*This ticket will also cover adjusting requests that UI sends to backend so shelfKey is not used. That covers following scenarios:
1. User starts call number browse:
query: callNumber>="HN59 .T39 2014" or callNumber<"HN59 .T39 2014"
2. User clicks on one of the rows:
(callNumber=HN 259 T39 42014 C 11) sortby title
3. User clicks Previous button:
callNumber < "HN 259 S84 C 11"
4. User clicks Next button :
callNumber > "HN 259 S780 C 11"*