Bug 13509

Summary: Cross reference link for "Author" in search results always uses keyword search.
Product: Koha Reporter: Barton Chittenden <barton>
Component: SearchingAssignee: Galen Charlton <gmcharlt>
Status: CLOSED FIXED QA Contact: Testopia <testopia>
Severity: enhancement    
Priority: P5 - low CC: katrin.fischer
Version: Main   
Hardware: All   
OS: All   
Change sponsored?: --- Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:

Description Barton Chittenden 2015-01-02 17:41:50 UTC
Doing an advanced search in the staff client using 

drop down "Title"
search for "Black and Decker"

The first search result is

The complete guide to patios : plan, build and maintain
by Schmidt, Philip. Black & Decker Corporation (Towson, Md.)

Where 'Schmidt, Philip' and 'Black & Decker Corporation (Towson, Md.)' are separate author links.

The link under 'Black & Decker Corporation (Towson, Md.)'

Is

http://.../cgi-bin/koha/catalogue/search.pl?q=au:%22Black%20&%20Decker%20Corporation%20(Towson,%20Md.)%22

This is a keyword search, rather than search by phrase, so the most relevant results are all authors with 'Black' in their names, rather than 'Black & Decker', which would have ranked higher in a search by phrase. 

The library is *not* using queryparser.

Indexing using DOM.

Possibly related bugs:

The library in question is using authorities, but the bug description doesn't really match.

Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5842 
 Cross-Reference links to authorized fields give incomplete search results

---

This is old, and marked as 'pushed' it seems relevant, but I'm not sure.

Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5941 
 Change the link in the authority search results to a phrase search


--- 

Not directly related, but it also has to do with cross reference links...

Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13301 
 Call number link in search results is broken
Comment 1 Katrin Fischer 2020-01-06 13:43:02 UTC
This issue is due to the not uri-encoded & in the generated URL. It's fixed by the use of str:uri-encode in the XSLT templates now.