https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42018
Bug ID: 42018
Summary: Inconsistent behavior for null values for fields
selected in PatronDuplicateMatchingAddFields
Initiative type: ---
Sponsorship ---
status:
Product: Koha
Version: 25.11
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5 - low
Component: Patrons
Assignee: [email protected]
Reporter: [email protected]
QA Contact: [email protected]
CC: [email protected], [email protected]
PatronDuplicateMatchingAddFields behaves differently for null values depending
on whether the null values are in the existing patron record or the record
being created.
To replicate:
-Set PatronDuplicateMatchingAddFields to surname, firstname, email
Scenario 1:
-Create patron A with a first name and surname, but null email
-Create patron B with a first name and surname matching patron A, but a value
in email -----> NOT FLAGGED as duplicate
Scenario 2:
-Create patron A with a first name, surname, and email
-Create patron B with a first name and surname matching patron A, but null
email -----> FLAGGED as duplicate
It seems that the two scenarios should behave the same way, or that there
should be documentation of the different behavior in the manual.
This applies to 40082 but is also true for duplicate matching in the staff
interface.
--
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
[email protected]
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
