SCT Banner Student / Release Guide / 7.0

Section 5 Common Matching - FunctionalMatching AlgorithmPriority Column Name Data Element Length Required/Exists2 SPRIDEN_SEARCH_LAST_NAME LAST NAME/NON-PERSON NAME 10 RequiredSPRIDEN_SEARCH_FIRST_NAME FIRST NAME 10 RequiredSPBPERS_SSN SSN/SIN/TIN 9 ExistsSPBPERS_BIRTH_DAY DATE OF BIRTH DAY 2 ExistsSPBPERS_BIRTH_MONTH DATE OF BIRTH MONTH 2 ExistsSPBPERS_BIRTH_YEAR DATE OF BIRTH YEAR 2 ExistsSPRADDR_CITY CITY 10 ExistsSPRADDR_ZIP ZIP/POSTAL CODE 5 Exists3 SPRIDEN_SEARCH_LAST_NAME LAST NAME/NON-PERSON NAME 10 RequiredSPRIDEN_SEARCH_FIRST_NAME FIRST NAME 10 RequiredSPBPERS_BIRTH_DAY DATE OF BIRTH DAY 2 ExistsSPBPERS_BIRTH_MONTH DATE OF BIRTH MONTH 2 ExistsSPBPERS_BIRTH_YEAR DATE OF BIRTH YEAR 2 ExistsSPRADDR_CITY CITY 10 ExistsSPRADDR_ZIP ZIP/POSTAL CODE 5 ExistsMatching AlgorithmOverviewThe new matching algorithm used with Common Matching processing is composedof two matches - primary and secondary. The primary match selects a pool of Bannerrecords that may match based on first, middle, or last name, and/or SSN and ID. Ifa record is selected as part of the primary match, then it will be one of the potentialmatches. The secondary match then looks at all the records from the primary matchpool and uses the rest of the fields in the matching rule to see if only one recordmatches exactly. If only one record matches exactly, that record is a match. If morethan one record matches, then all those records that match or partially matchbecome the potential matches.January 2005 Student Release 7.0Confidential Release Guide 149