This adds a new optional parameter for the contact value. If the patron id is left blank, and the contact value is present then it will try to invalidate the contact info for all patrons that have that contact info.
I think there also needs to be some normalization of the contact value. For email addresses we should lowercase the value and the expected value so that "<email address hidden>" matches "<email address hidden>"
For phone numbers maybe just strip out separator characters so "218-555 4564" matches "2185554564". I'm not sure what to do with trailing phone info, like extension numbers. If I'm saying that I want to invalidate "111-222-3333", should that invalidate the number if a customer has their other phone set to "111-222-3333 ext 445", and vice versa?
Working branch at lp1574141_ invalidate_ by_contact_ info git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ stompro/ lp1574141_ invalidate_ by_contact_ info
user/stompro/
http://
This adds a new optional parameter for the contact value. If the patron id is left blank, and the contact value is present then it will try to invalidate the contact info for all patrons that have that contact info.
I think there also needs to be some normalization of the contact value. For email addresses we should lowercase the value and the expected value so that "<email address hidden>" matches "<email address hidden>"
For phone numbers maybe just strip out separator characters so "218-555 4564" matches "2185554564". I'm not sure what to do with trailing phone info, like extension numbers. If I'm saying that I want to invalidate "111-222-3333", should that invalidate the number if a customer has their other phone set to "111-222-3333 ext 445", and vice versa?
Thanks
Josh