SCT Banner Student / Release Guide / 7.0

Section 5 Common Matching - FunctionalMatching AlgorithmNote: If the matching source is defined to match non-person records, andSPRIDEN_SEARCH_LAST_NAME is not like the non-person name from theexternal Source, the matching algorithm will check to see if a matchingrecord exists on the GORNPNM alias table.(b)One of the following must be true:First Name data element is not defined.orFirst Name data element is defined for the rule, andSPRIDEN_SEARCH_FIRST_NAME is equal to the external source first namefor the specified length.Note: If the SPRIDEN_SEARCH_FIRST_NAME is not like the first name from theexternal source, the matching algorithm will check to see if a matchingrecord exists on the GORNAME alias table (if the matching source isdefined to match person records).(c)One of the following must be true:Middle Name data element is not defined.orMiddle Name data element is defined for the rule, andSPRIDEN_SEARCH_MI is equal to the external source middle name for thespecified length.Note: If the SPRIDEN_SEARCH_MI is not like the middle name from the externalsource, the matching algorithm will check to see if a matching recordexists on the GORNAME alias table (if the matching source is defined tomatch person records).3. If ID is defined for the matching source and rule priority number, retrieve allrecords from Banner with a matching ID.The ID data element is defined as part of the rule, and SPRIDEN_ID is equal tothe external source ID.Secondary Matching LogicThe secondary matching process compares the data elements defined for thematching source and rule priority number for all records returned by the primarymatching process. The goal of the secondary match is to find an exact matchbetween the external source record and a Banner record.January 2005 Student Release 7.0Confidential Release Guide 153