Bug 26146 - Patron duplicate matching - fuzzy matching?
Summary: Patron duplicate matching - fuzzy matching?
Status: RESOLVED MOVED
Alias: None
Product: Koha
Classification: Unclassified
Component: Patrons (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-05 14:50 UTC by Sally
Modified: 2023-09-25 11:41 UTC (History)
3 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sally 2020-08-05 14:50:53 UTC
Koha doesn't have a middle name field so librarians may try to use the first name field to hold both first names and middle names.

This means that Koha's duplicate patron feature doesn't work, e.g.

Brian David Jones already exists on the system.
Patron is added as Brian Jones.
Koha doesn't find the duplicate patron, because it thinks "Brian" is different to "Brian David"

OR

Brian Jones already exists on the system.
Patron is added as Brian David Jones.
Koha doesn't find the duplicate patron, because it thinks "Brian David" is different to "Brian"

Is it possible to have fuzzy matching on the first name field, so "Brian Jones" would match "Brian David Jones" and "Brian David Jones" would match "Brian Jones" ?
Comment 1 Katrin Fischer 2023-09-22 19:07:31 UTC
Hi Sally, Koha does have a middle name field now - does this resolve the issue?
Comment 2 Sally 2023-09-25 08:38:23 UTC
(In reply to Katrin Fischer from comment #1)
> Hi Sally, Koha does have a middle name field now - does this resolve the
> issue?

Hi Katrin, yes - middle name solves it.  :)

This issue is why we sponsored the middle name development - but I forgot we had this bug open!  I'd close it, but not sure which RESOLVED status is best to use.
Comment 3 Katrin Fischer 2023-09-25 08:42:13 UTC
Hi Sally, you could use "RESOLVED MOVED" here or maybe "RESOLVED WONTFIX". I tend to use the first if the problem has been resolved, but the other bug is not a real duplicate.
Comment 4 Katrin Fischer 2023-09-25 08:42:41 UTC
... but overall, we are not picky :)
Comment 5 Sally 2023-09-25 11:41:03 UTC
Fab, thanks Katrin :)