soc-pe-bot
commented
2 years ago Team's Response
Thank you for your input. However, we think that this is not in scope because we already mention in the UG that in order for it to be duplicate, it must be the exact same name. Reason why we allow for spacing difference to not be detected as duplicate is to allow users to add contacts that might have same legal name in terms of wording by differentiating it using spaces, numbers, or capitalization. In future iterations, if we receive overwhelming feedback from users requesting for stronger duplicate detection, we will evolve our differentiation of names to be more sophisticated. Currently, we have feedback requesting for more freedom in valid names which is why we have our current design.
Items for the Tester to Verify
:question: Issue response
Team chose [response.NotInScope]
- [x] I disagree
Reason for disagreement: In reality, there are lots of other ways to specify that 2 people are different, such as assigning them IDs, or differentiating them by email instead(as email is unique to each person). Doing this is just simply not the best of practice, as we would not expect people of different spaces to be of different identities.
As we can see, John Doe and John Doe are considered as 2 different persons. At times, users may accidentally inputted a duplicate person, but the extra space caused it to not be detected. Perhaps, the spaces can be parsed differently, or that the handling of such cases be documented