Does a customer need to provide his/her birthdate?

Birth date on a customer’s record is one of the required fields in Carl*X and it has several benefits for the customer and our system alike. Not only does a birth date assist with demographic information we can use for statistical analysis for materials and programs, but it also helps protect the customer when and if their library account becomes compromised. For instance, if a minor presents a library card with a birth year of 1958 you know there is a potential problem.
When a customer applies for a library card via our Online Borrow Registration (OBR) the Carl*X system will automatically check for name and birth date duplication. If a duplication record is found, the system will place a note on both the OBR record and the related card’s record so that staff can correct this duplication when the customer comes into the library to convert their online card. REMEMBER: You should always do a PATRON SEARCH prior to the entry of any new library card application to check for duplications.
The employee expectation is to secure an accurate birth date from the customer if one is not provided on the completed library card application. Communicating the value of such information to the customer may be necessary, but failure by the customer to provide a birth date should not prevent the employee from issuing a library card to the customer. Entering a fictitious birth date that most accurately represents the customer’s age range would be appropriate in these rare instances.
- Log in to post comments
Comments
"Entering a fictitious birth date that most accurately represents the customer’s age range would be appropriate in these rare instances."
This fictitious date is to be our best estimate? Do we tell the customer?
Jim, that's a very good question.
If a customer chooses not to provide us with a birth date we would want to be sure that they understood why we were asking for it and the way that it benefits them for us to have it included on their account. They should understand that our system requires that something be entered in the birth date field and that if they can't provide us with one we will have to enter our best guess. We should be sure they understand that in future if they forget their card when they come to the library or were to lose their card we would check their ID before providing them with their account number. With a fictitious birth date we could not be certain that we had a match to the account and that could result in difficulty for them in using the library. Bottom line is that there needs to be a good conversation with the customer about this before a fictitious birth date is entered.
Thank you Julie. That seems to me to be a great explanation. Jim, please let Julie or me know if that does not fully answer your question.