Summary: | Purchase suggestion Search (title filter) only exact match | ||
---|---|---|---|
Product: | Koha | Reporter: | Barry Cannon <bc> |
Component: | Acquisitions | Assignee: | Bugs List <koha-bugs> |
Status: | RESOLVED DUPLICATE | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P5 - low | CC: | bc, jonathan.druart |
Version: | 23.05 | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: | ||
Attachments: | Workflow of purchase suggestions search |
Created attachment 152238 [details] Workflow of purchase suggestions search If a borrower logs into the OPAC and searches for a Purchase Suggestion it will only return hits if the exact string is entered (see attached). Looking at the underlying query it preforms an exact match on `title`. SELECT `me`.`suggestionid`, `me`.`suggestedby`, `me`.`suggesteddate`, `me`.`managedby`, `me`.`manageddate`, `me`.`acceptedby`, `me`.`accepteddate`, `me`.`rejectedby`, `me`.`rejecteddate`, `me`.`lastmodificationby`, `me`.`lastmodificationdate`, `me`.`STATUS`, `me`.`archived`, `me`.`note`, `me`.`staff_note`, `me`.`author`, `me`.`title`, `me`.`copyrightdate`, `me`.`publishercode`, `me`.`date`, `me`.`volumedesc`, `me`.`publicationyear`, `me`.`place`, `me`.`isbn`, `me`.`biblionumber`, `me`.`reason`, `me`.`patronreason`, `me`.`budgetid`, `me`.`branchcode`, `me`.`collectiontitle`, `me`.`itemtype`, `me`.`quantity`, `me`.`currency`, `me`.`price`, `me`.`total` FROM `suggestions` `me` WHERE ( ( `suggestedby` = '33805' AND `title` = 'suggested' ) ) Maybe a wildcard search might be better here? Or, using Datatables client side, like the staff interface. Observed on 22.11 and 23.05