![]() ![]() When is the most appropriate time to show users a list of similar looking records during the process of creating new records? Option 1 - Synchronous / Modal Matches same First Name + Last Name + DOB), then the best any system can do is look to minimize the amount of duplicates, and technology can play a role in that business process. If we rely on multiple fields to establish a record AND genuine records can repeat information across fields (i.e. Even though we've generated an identifier that will bear real world significance, it can only be used to differentiate accounts, not people. However, the same user/person/individual can still create nearly identical accounts. This does a great job at dynamically showing validation errors as you type. Note 3: While you can create your own sort of natural key, like a username, this isn't really a mechanism for prevent duplicates of anything but the generated name itself.įor example, here's the sign up page on Reddit: Note 2: Bear in mind that you might NOT want to use email or phone as a unique identifier for contact records (for example, multiple professionals can all share the business contact email and phone number). So you should prompt for any unique information first, either in a stepper or seperate page in order to avoid any unnecessary typing. Note 1: As with any validation error, it's best to do so inline and immediately if the data state is invalid. For example, if your record has a Social Security Number, ISBN, Active Directory Account, or occasionally email / phone, you can prevent duplicates by guaranteeing each record has a distinct key.įor example, here's the sign up page on Twitter: Your approach will be fundamentally different based on whether a Natural Key exists for the type of record your are trying to create.Ī natural key is something that uniquely identifies a piece of data that already exists in the real world. If not duplicated, then we create account AND we can ask for confirmation of mail account If duplicated mail, we offer teh user the option to access her account.ģb. System checks if the email isn't duplicated We add mail as first field to avoid user fill unnecessary fields in case of existing accounts. Check image below (click if you need to enlarge): Now, with this in mind, we can make things run smoothly. ![]() Since there can't be 2 emails that are the same, this is a perfect choice. To make it worse, not all countries have the same amount of digits, so this is clearly not a good choice either.īut do not despair! We have a field that is very easy to validate, we can use for confirmation AND can't be repeated: email. Then you might find an user wit mobile number NNN-NNN-NNNN in UNicornCountry and then mobile number NNN-NNN-NNNN in RainbowCountry. You might say "OK, let's validate with city prefix". Otherwise, you could have the mobile number NNN-NNNN for someone in Big City and then NNN-NNNN for someone in Small City. This could work on an intranet or if your app is restricted geographically, eg only one city. First of all, let's consider which data can be duplicated and which data cannot be duplicated.Īs other answers mentioned, Name (first, last or combination of both) is not a good choice, since there might be many repeated names.
0 Comments
Leave a Reply. |