Summary: | FindDuplicate uses 'exact' for searching and is too strict | ||
---|---|---|---|
Product: | Koha | Reporter: | Nick Clemens (kidclamp) <nick> |
Component: | Searching | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P5 - low | CC: | andrew, bc, bdaeuber, dch, dcook, mfuerst, sally.healey, severine.queune |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: |
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15248 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35886 |
||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Bug Depends on: | 14973 | ||
Bug Blocks: |
Description
Nick Clemens (kidclamp)
2020-12-18 11:35:36 UTC
I'm not sure what's in the scope of this bug, but another thing to consider is item type. For example, a suggestion for a movie might reveal the novel adaptation, or vice versa. This adds an extra step to the process, and generally is just a pain (as well as making us look silly with what it thinks are potential duplicates). I was thinking a lot about FindDuplicate today and the merits of "exact" vs inexact searches... If you don't use an "exact" search, "The vixens" would also match "Wild vixens: how foxes raise cubs in nature". I think the sorting is based on biblionumber so you'll just get the earliest catalogued "vixens", since we only take the top result from the search results for FindDuplicate. Perhaps this could even be marked as a duplicate of bug 15248? Making it configurable could be the best solution for everyone. *** Bug 33969 has been marked as a duplicate of this bug. *** I believe especially for short titles a keyword search would be too strict. Maybe a phrase would something we could try, but if it gives too many false positives, people will be annoyed. |