AgeFinder Error Fixing

Katrina Noplos

To anyone who's run AgeFinder (or similar service):

I've got my results, spot checked for accuracy, and decided they were accurate enough (even though not exactly 100%) to load into Bio 1 (and not just leave as an attribute)

I've decided to patch up some of the blatant errors while I've got 'em all in a query, and so far have had some success fixing a couple errors looking for people in their 20s or younger whose gift totals are $$$$$ (I've found running them individually on AlumniFinder, they're actually much older)

My question is this: what other ways could I possibly scan these results to find what might be blatant errors?

Faith Murray

Depending on how long your database has been running, you could scan for "constituent date added" and "address valid from" fields. For example, we adopted Raiser's Edge in 1999, and we don't enter minors in the system. So if a person's Agefinder reads 25 years old, but we added them in our system in 2003, I know the donor must be at least 33 years old in actuality.