My answers regarding Rice are embedded in the text below. A couple of
The work involved in this process is always on the owner, not the
software. There really is no software solution that will do this
automatically either COTS, Home Grown or Open Source. All of higher ed
has had this challenge so at least there is company in this problem space.
Benn Oshrin wrote:
> One of the issues we're about to (re)examine here is matching people
> who come from multiple sources.
> A typical case is a student who we already know about from the student
> system gets hired as a casual or work study employee, and we want to
> make sure their information from the personnel system gets attached to
> their existing identity rather than have a new (second) identity
> created for them.
> We already perform weak matching that catches most cases, but we are
> looking to signficantly improve our handling of these individuals. We
> would prefer to get a better idea of what others are doing before we
> make our plans, and so I'd like to throw out a few questions to the list.
> 1. Did you write your own matching algorithms or do you use a
> vendor solution?
We wrote our own.
> 2. If you wrote your own, what criteria do you match on?
The trick is getting a common set from all sources. We identify on the
following as a minimum from all sources.
We look at
1) Key ID from source system
3) Name matching
4) Considering another field like mothers maiden name or place of birth
given we can get all data source managers to agree to add/manage that
> 3. If you use a vendor solution
> a. Which one do you use?
> b. Is it a full vendor implementation, or do you just call
> hooks from your own existing applications?
> c. Who implemented your solution? (vendor, consultants, staff,
> 4. What has been your success rate with your implementation?
Very good success rate given that the source systems information is
correct. Very low overhead, but our student/faculty/staff system is the
same data source. Our guest systems are the only ones that can provide
> 5. What are your procedures for handling close/multiple potential
This is a flag and manual process. The source systems are changed to
reflect correct information or collisions
> 6. What are your procedures for recovering incorrect matches?
notify the data source managers of the collision
> 7. If not otherwise covered above, what are the interfaces to your
> system? (manual data entry via web, batch feeds, real time api,
Real time API and batch feeds, manual entries for sponsored guests.
> I will summarize off-list replies.