Parameters need to be maintained when sorting search results

[Kathy Lussier]

Confirmed in master and 2.3

When linking to a public bookbag, a depth=0 parameter is passed, presumably so the link will show all titles in the list, even if those titles aren't owned by the library's whose locg parameter is passed in the link.

For example, the HTML View link for one of my bookbags brings me to:
 https://bark.cwmars.org/eg/opac/results?bookbag=4749;page=0;locg=28;depth=0

However, when you re-sort the list, the depth parameter is dropped, making it appear as if titles have disappeared from the bookbag. What has happened is that the bookbag is now only displaying titles belonging to the OU (or children thereof) in the locg parameter.

The depth parameter (and, I would think, any other parameter in the URL) needs to be maintained when re-sorting the list on the search results page. I would not expect the depth parameter to be maintained once a new search is executed since, at that point, the user has made an explicit choice to narrow results to that OU.

[Kathy Lussier (klussier)]

This is also an issue with facet parameters. See https://bugs.launchpad.net/evergreen/+bug/1356153.

[Kathy Lussier (klussier)]

Confirming this bug based on bug report submitted at https://bugs.launchpad.net/evergreen/+bug/1398954. Note that this bug report also identifies language, literary form, audience, and shelving location as parameters that need to be maintained.

[Liam Whalen (whalen-ld)]

I have tested this on master, and the advanced search parameters are now being preserved via the Search Box. Can anyone else confirm this?

[Liam Whalen (whalen-ld)]

I have a fix for this on Sitka's servers that rebuilds the search parameters via Javascript rather than including them in the Search Box. Is this something the community is interested in having in the community git tree?

You can see our production catalogue here:

http://catalogue.libraries.coop/eg/opac/advanced?bool=and;bool=and;bool=and;qtype=keyword;qtype=title;qtype=author;contains=contains;contains=contains;contains=contains;locg=1;_adv=1;pubdate=is

[Kathy Lussier (klussier)]

Hi Liam,

I can't speak to whether the developers would see this as an acceptable approach to fixing this bug. I know there generally is reluctance to using javascript in the catalog.

I do want to make note of the fact that sorting and limiting to available continue to remove the facet and depth parameters from the search. I would love to see a solution that addresses all parameters. If it goes in as is, I'm adding this comment to serve as a reminder to submit a new bug for those parameters.

Kathy

[Mike Rylander (mrylander)]

As a side effect of the fix for bug 1005040 this is now fixed and the depth CGI param is retained.