Conditions for duplicate handling are not optimal

[nus-pe-bot]

Bug

• The conditions to separate duplicates can be implemented better

Reproduction

• add n/Thomas Henry p/98765432 e/johnd@example.com a/John street, block 123, #01-01
• add n/Thomas henry p/98765432 e/johnd@example.com a/John street, block 123, #01-01
• The above 2 commands add 2 different users to RealConnect. The differentiating of duplicates criteria is stated in the UG as Full name (mandatory) (Alpha-numeric only, space allowed) (exact duplicate not allowed, case-sensitive)
• I believe that this criteria is not good enough as I am able to add 2 John Does (possibly writing name as uncaps or caps as I forgot if they are already added). The key to differentiate should be improved.

Screenshot

---

_{[original: nus-cs2103-AY2425S1/pe-interim#3759] [original labels: severity.Medium type.FeatureFlaw]}

[starbucksventi]

Team's Response

Thank you for pointing this out. However, we feel that this is a matter of what settings the user wants to incorporate - i.e. whether the user wants the app to be case sensitive, case-insensitive or some other condition for checking equivalence. As the current stage of development is quite early, we were not able to implement an app that is thorough enough to incorporate all settings, and thus went with this current one that we have - that case sensitivity is a condition for name equivalence.

If we chose the converse, i.e. case insensitivity, then one could argue that it too does not fit certain use cases. One such example is CASPER, which could represent an acronym for a real estate group, and Casper, the name of a potential buyer.

Either way, we feel the user will rarely run into this error, since we expect the person to be a seasoned typist and Real Estate Agent and therefore believe it to be of low severity. However, we will take this important point under advisement for future iterations.

Duplicate status (if any):

--