I took a look at this code today. Overall, it looks good. I just have a couple of questions.
1. The detailed view of the search results page does not appear to be honoring the new sort order. I would expect parts to be sorting here the same way that they do on the bib record page. See
2. The xul-based holds interfaces of the staff client can display a holds column that is sortable. Should we expect these interfaces to honor the imposed sort order? In my testing, they are still sorting alphabetically. This is a general question for users.
Hi Dan,
I took a look at this code today. Overall, it looks good. I just have a couple of questions.
1. The detailed view of the search results page does not appear to be honoring the new sort order. I would expect parts to be sorting here the same way that they do on the bib record page. See
https:/ /mlnc1. mvlcstaff. org/eg/ opac/results? query=sports% 20illustrated; qtype=keyword; locg=1; detail_ record_ view=1
in comparison to
https:/ /mlnc1. mvlcstaff. org/eg/ opac/record/ 238
2. The xul-based holds interfaces of the staff client can display a holds column that is sortable. Should we expect these interfaces to honor the imposed sort order? In my testing, they are still sorting alphabetically. This is a general question for users.
Thanks Dan!
Kathy