matching rules for data loads – what we’ve learned!

Post on 02-Jan-2016

231 Views

Category:

Documents

2 Downloads

Preview:

Click to see full reader

TRANSCRIPT

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

Jessica ComfortBusiness Systems Analyst

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

Rules for what type of data loads?Currently:ACTAPCAPPEXCWLICFMSINCFSATGRETOEFLSEARCH (PSP, PLP,NRC, ACN, SAN)

What types of data do you load into Banner?

2010 2011 2012 2013 2014 Present

Set up Tape Load Process

• 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)

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

Banner forms to know

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

Match on Null – What does that mean?

YES –Match on NULL

No –Match on NULL

BANNER DATA BANNER DATA

BirthDay

NULL NULL Data(1) Data(1)

NULL Data(1)

Data(1) NULL

Data(1) Data(1)

Single rule set

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

Multiple rule sets

Multiple rule sets cont.

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

Results of changes we’ve madeSpring 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.

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 testingAND

• Exploring options available in GORCMSC

Jessica ComfortBusiness Systems Analyst906-487-1849jcomfort@mtu.edu

top related