1. Email Validation Check
Version 21 rep_ver #017591
Yoel Kortick

2. Agenda Introduction Configuration Example
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

3. Introduction Purpose of Enhancement:
New functionality has been added to check the validity of a patron's e‐mail address.
Description:
The following new tab100 flag has been added to the ADM library setup: ‐VALIDATION.
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

4. Introduction Possible values for EMAIL-VALIDATION Y
The system performs a patron's validation check and displays a message if the address is not valid (warning message, not a block).
The check is activated when the patron address is updated and the field is populated.
It is performed when the address is updated via GUI, OPAC, PLIF loader, DLF-API, and X-services. N
Default. No validity check is performed.
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

5. Introduction If the flag is set to Y, the validation includes:
Syntax check
Existence of only one “at” symbol
Existence of a dot after the “at” symbol
No space in the address.
Domain existence check
a check confirming that the remote server exists.
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

6. Agenda Introduction Configuration Example
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

7. Configuration This is the only configuration needed
USM50> grep ^ -VALIDATION tab100
-VALIDATION=Y
USM50>
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

8. Agenda Introduction Configuration Example
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

9. Example in GUI
In the GUI patron’s address was added by accident as (two .’s)
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach
After clicking “Update” the above message is received

10. Example in GUI
In the GUI patron’s address was added by accident as (‘k’ instead of ‘i’)
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach
After clicking “Update” the above message is received

11. Example in GUI
The reason gave us an error is because gmakl.com is not a domain.
Domain gmail.com gives a response
Domain gmail.com gives a response
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach
Domain gmakl.com gives no response

12. Example in Web Now we will register a patron in the web OPAC
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

13. Example in Web Again we will give him a “bad” email
Here we forgot the “.” between “yahoo” and “com”, and then we get this message:
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

14. Example in X server
We will use this URL to update the address of patron
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach
The domain jimyjones.com does not exist

15. Example in X server The X server gives the error message also
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach