Will the first name First name + Last name + Date of birth be unique?
I need help developing algorithms / databases for my work in a web application (I apologize for the long question in advance)
App Description:
I'm setting up a customer registration station (it's basically just a monitor that displays a web page and is connected to a scanner) where customers who come to the office (similar to a library) can scan their office ID card (this has a unique barcode) code) for registration, customer information (name, surname, date of birth, registration time ...) will be sent / saved on the server, and the office administrator will be able to see which is now in the office and doing something ...)
When creating an ID-card for a new client, the only necessary information is: name, surname and date of birth (the client can be of any age from children to senior) => the system will create a unique barcode (16 digits) and print a new ID card (only with its barcode)
Problem
If the customer has forgotten / lost their ID card, or sometimes the card is too old, so the barcode cannot be scanned, the customer can dial their first + last name and date of birth to the registration station, then the system will search for (first name, last name + first name + date birth) and determine if this customer exists and check them. But it is possible that there is more than one person with the same name and birthday: - then the system can display all agreed people for viewing, but how can the client know which one is himself? - or this situation can be avoided if the system does not allow the client, who will have the database in the first place with the same name and add. But then the client who came "second" will be very upset that he / she cannot have a card :))
Edit:
How can I deal with this problem, I mean this is just an office, so we cannot ask for an SSN or a driver's license ... the registration process should be simple and fast, some of them may be children that I don't have have an id or phone number (they will come with their parents / guardians) and many of them are seniors (over 70 or even 80), they can't even type, why the idea of "ID card - scan" is here to help them - all they have to do is scan their card ... (I don't think they could ever remember the "secret question") SMS verification won't work (phone number can be changed, not all customers have here will phone, carrier (coverage, rate ...) involved, I don't want that).
OK after reading all your suggestions:
I am thinking of a 4 digit password (like the 3 digit security code on the back of a credit card) - it will be printed on the ID with instructions and everything, it will be different from the unique customer number (used for scanning), here like this works: - when creating a new customer identification card, the system will ask for an additional 4-digit password code, as well as print it on the card, algorithms will also be installed so that customers with the same name + dob cannot have the same password.
In case the client cannot use / lost the card, after entering the name + dob for registration, the system only asks for this 4-digit access code, if there is more than one person , otherwise, if there is only one person, the system will check them on the right ...
if they ever forgot this pass code, i mean they can't do anything for themselves, the receptionist has to help them in some way , what you guys think i am still open to suggestions
My final solution:
Since the cards have no more information (customer information) than the barcode (customer number), the best way is to preprint (pre-made) to be ready on the table to give to new customers or for card replacement purposes.
-
When creating a new client, the registrar will manually enter name + name + number + before + phone number (optional) + email address (optional) + home address + client number (like the same as in the card they are going to give the client) +. submit, the system will check everything if everything is a good registrar and then offer the client a new card => client go back to the check-in station.
-
When customers forget the card => they will have to see the receiver => perform the verification process => the registrar will manually verify them.
-
If the card is damaged or the card is damaged => they will need to see how the receiver => perform the verification process => the registrar and then provide the customer with the replacement card => the customer go back to the check-in station and check in.
source to share
Some rambling thoughts:
You can assign a PIN to users and use it to make their account unique. Presumably, to make sure it's unique, you have to assign it, you can't let them invent it. (You could let them invent one and then check for uniqueness. This can be useful so people can use numbers that have a meaning to them so they can remember them.) The big catch with this is that if a person loses their PIN, you are stuck. If the PIN is printed on the card, then if the card is damaged or worn out, yes, they can enter the PIN. But if they have lost the card, they will not have another PIN entry.
You can request your phone number and use it as an identifier. My grocery store does this for my discount card. I think everyone has a phone today. For a small number who don't have this, you can create a random number that looks like a phone number but is invalid (so it won't duplicate any real phone number) and use that as a PIN. For example, if you are in the US you can make the generated numbers start at 555-555 and then make the last 4 digits look like a PIN. Then the only people that would be a problem are those who do not have a phone AND who have lost their card, which must be very small.
Is there any information in this system that is confidential or are people going to spend money? I mean, if someone walked up to a kiosk and typed in their neighbor's name and date of birth and accessed that account, would it be a problem? You didn't say what the system does. If getting into the system gives someone access to medical records or a bank account, or a transcript of their last confession to their priest, then you need to take steps to prevent unauthorized access, you cannot let anyone come in and claim they are someone else. and come in. A few years ago, I am reminded of a case where a reporter got access to tapes of some of the DVD tenants. He was apparently hoping to find that he was filming a lot of vile pornography or some that he could use,to embarrass the guy, although it turned out to be mostly Westerns. My point is that even seemingly innocent information can confuse someone under the right circumstances, so you have to be careful.
How often do people lose or damage cards? And are there any clerks out there who could help someone in such cases? That is, if in 99% of cases someone comes, pulls out his card, and he is in it, and everything is fine, and the number of times someone has a lost or damaged card is very small, you can say that in In those cases, they must contact the clerk and show the damaged card, or, if they say they have lost their card, show identification. Then the clerk can check everything and give them a new card. You could find clerks by name and have a screen that shows dates of birth and addresses, ask the client what is their date and address of birth, and if it matches one, give them a new card, if not, tell them I'm sorry. ' not in the file. This is very different from a security point of view,showing the client a list of birthdates and addresses and letting them pick one as a client (a) enter a common or overheard name and then select any matching entry that shows or even (b) use that to find the address of someone who they want to chase and then you can be held accountable.
source to share
In the current project, I met the same thing to find a client. The project is dedicated to television material, so the second level of the "sieve" is the address. And I think you need to expand the customer information: username, email, avatar or something easy to remember (or send SMS with a code). You can also add user-friendly behavior: if the customer cannot decide which record is about him, the customer must go through the wizard and add the required information. Yes, it is difficult to find common evidence for all clients, but you can support several types of additional information. In other words: first name, last name and date of birth are not enough to unambiguously receive a person.
source to share