Has anyone come up with an easy way to scrub data to improve quality (examples would be where Constituents use all lower case or upper case letters, or spell out the word Street or Avenue when standards are to be St or Ave, etc.) Those kind of quality issues.
At issue are fname, lname, street1, city, prefix and gender.
Unknown said: Has anyone come up with an easy way to scrub data to improve quality (examples would be where Constituents use all lower case or upper case letters, or spell out the word Street or Avenue when standards are to be St or Ave, etc.) Those kind of quality issues. At issue are fname, lname, street1, city, prefix and gender.
A good place to start would be Brian Grundstrom's "lf_titlecase". Look for him in the directory and click through to his shared files.
You'll need to tweak that code for your org's standards, and think carefully about how and when you want to execute it. Once that's done the above works splendidly for what you describe.
Thanks for sharing that Brian!
Hi Daniel,
This is an excellent use case for a service interceptor. Ron Wilson has written a sample interceptor that formats pretty much all constituent contact information, you can find it on TASK under optional components.
Cheers,
Patrick.
Unknown said: This is an excellent use case for a service interceptor. Ron Wilson has written a sample interceptor that formats pretty much all constituent contact information, you can find it on TASK under optional components.
If we look into the comments of Ron's plugin sample code we see
"This more complex example closely recreates the widely shared Auto Address Correction functionality originally created by Brian Grundstrom..."
Brian's lf_titlecase has fans everywhere. :-)