Search grammar tag stacking in basic search box
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Evergreen 3.0
You can end up with stacked search grammar tags in the search box.
To see this happen live in our catalog, go to https:/
- search term "heidi", choose Title from the dropdown
- get results
- click on "More Search Options" (this just takes you to the advanced search screen)
- in the advanced search, choose Title and heidi. Search.
- get results. You'll see "title:heidi" in the search box.
- choose Title from the dropdown. don't change what's in the search box.
- get results. You'll see "title:title:heidi"
You can rinse/repeat on this as many times as you like. (I only did it five times.)
It seems to me the system should somehow recognize the search grammar is already on "title:" if Title is chosen from the dropdown and not start stacking.
Changed in evergreen: | |
status: | New → Confirmed |
tags: | added: opac search |
**waving hands** We probably want to adjust both the initial server-side query construction to separate system and user supplied components (there's a syntactical mechanism for that spelled with {'s) and enhance the query canonicalization done by the storage service so that it can provide the user-typed portion separate from the constructed part. Then we can display only the user-typed part in the text box.