-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge duplicates should require sex AND date of birth to be equal [1] #3787
Labels
backend
Affects the web backend
cases
change
A change of an existing feature (ticket type)
qa-verified
Issue has been tested and verified by QA
Milestone
Comments
@bernardsilenou Please confirm. |
@MartinWahnschaffeSymeda
|
BarnaBartha
pushed a commit
that referenced
this issue
Feb 1, 2021
BarnaBartha
added a commit
that referenced
this issue
Feb 2, 2021
…cateLogic #3787 - duplicate cases should be both of same sex and birthDate
Sprint Backlog Team Application (deprecated)
automation
moved this from Review
to Testing
Feb 2, 2021
Validated ticket on the latest version of Sormas version 1.55.0 snapshot |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backend
Affects the web backend
cases
change
A change of an existing feature (ticket type)
qa-verified
Issue has been tested and verified by QA
Feature Description
Duplicate detection for retrospective merging considers some properties of the cases. Among others the sex and date of birth.
Problem Description
Currently the case is considered possible duplicate when sex OR date of birth are available and equal.
Proposed Change
Instead the logic should be an AND.
So when two cases of the same sex have a different date of birth, they should not be considered possible duplicates.
Additional info
Consider "unknown" / should not conflict with male or sth. else
The text was updated successfully, but these errors were encountered: