Matching Rules for Data Loads – What we’ve learned!

1. Matching Rules for Data Loads – What we’ve learned!

2. Jessica Comfort Business Systems Analyst

3. Goals for today’s presentation • Review Banner forms used in the set up of a tape load • Review Banner forms used in the matching process • Match on Null – how this works • Share what we’ve learned • Learn from each other

4. Rules for what type of data loads? Currently: ACT AP CAPPEX CWL ICF MSI NCF SAT GRE TOEFL SEARCH (PSP, PLP,NRC, ACN, SAN) What types of data do you load into Banner?

5. 2010 2011 2012 2013 2014 Present

6. Banner forms to know Set up Tape Load Process Set up Matching Process GTVCMSC – name matching source GORCMSC – how the data loads, match type=person, address=MA, phone=MA, email=OFFC GORCMRL – set up rules for load type • STVCTYP – Contact Code: ACT • STVINFC – Interface Code, Description, Contact Type, Common Matching: ACT • STVPREL – Prospect Code, Description, Interface Code, Tape Code: ACT • STVASRC – Address Source Code, Description: ACT • SOTCNVT - Needs ACT loaded with a copy from WIQ (optional)

7. Tape Load Process • SRTPURG – Clears data from temp tables • SRTLOAD (A&U) – Loads data to temp tables • SRRSRIN – Electronic Match Process • SRIPREL – Review records M,N,S,D • SRRPREL – Moves data from temp tables to production tables

8. Match on Null – What does that mean?

9. Single rule set *at Michigan Tech, must have Last_Name in ALL rule sets (or what ever you have set in GORCMDD)

10. Multiple rule sets

11. Multiple rule sets cont. ***MOST STRICT rule should be LAST rule set! Reference p. 34 of Banner Doc from Ellucian

12. Results of changes we’ve made Spring 2012 to Present • Establishment of a team to monitor/discuss the tracking of data results and time use as a result of changes • Review of data files and the fields each type of load are comprised of, allowing for customization of each load type to have its own set of rules • Two-level matching rules have shown a significant decrease in the number of records incorrectly matching to existing Banner records • Planning upcoming end-user training for use of matching rules and process as related to areas outside of STUDENT.

13. What we’ve learned • Importance of standard data requirements for load files (ie., first name, last name, dob, address, city, state, zip, email) • Understand – Match on null • Single and Multiple Rule sets • Continuous process of evaluation and testing AND

14. Exploring options available in GORCMSC

15. Jessica Comfort Business Systems Analyst 906-487-1849 jcomfort@mtu.edu