11.07.2015 Views

SCT Banner Student / Release Guide / 7.0

SCT Banner Student / Release Guide / 7.0

SCT Banner Student / Release Guide / 7.0

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Section 5 Common Matching - FunctionalSetting Up Common Matching2. Set up defaults for the source codes.Use the Common Matching Source Code Form (GORCMSC) to set up thedefaults to be used with a particular source code.Be sure that you set up your matching source code on GORCMSC prior tosetting up the rules associated with it on GORCMRL.For example, you can assign default address, telephone, and email types to thesource code which will default into GOAMTCH if the source code is used fromthere. GORCMSC is also used to identify whether the source code will be usedto perform matching against person data and/or non-person data and whetherthe source code can be used with online matching. Optionally, you candesignate other specific forms a user can navigate to in order to see moredetailed information about possible matched records by using the Detailsbutton on GOAMTCH.3. Assign default online matching source codes to a user ID.Use the Common Matching User Setup Form (GORCMUS) to assign a defaultonline matching source code to a specific Oracle user ID. In addition, you canspecify whether a specific user ID is allowed to choose from other matchingsource codes, or if they are restricted to using just the default source code. Youcan also indicate if a specific user ID is excluded from having to use onlineCommon Matching.For example, if a user is a “super-user” who never creates duplicate PIDMrecords, they may be exempted from having the GOAMTCH form appear fromSPAIDEN by checking the Exclude User (Indicator).4. Set up the matching rules associated with the source codes.The Common Matching Rules Form (GORCMRL) is used to set up the actualmatching rules associated with the source codes. Previously, SOAINFR was usedin <strong>Banner</strong> <strong>Student</strong> to define the specific matching rules for an interface code.Now, GORCMRL is used for this purpose.Use this form to create each rule, assign a priority to it, and then assign thespecific database fields for each rule which will be used by the matchingalgorithm. You can also copy previously created rules, as well as add specificprocedures for matching components that are not contained within <strong>Banner</strong>General (i.e, matching on high school data for <strong>Banner</strong> <strong>Student</strong>).Note: Previously on SOAINFR, if a field was to be included in a rule but was notrequired, it had an indicator set to Y. With Common Matching, that samefield would now be specified as Exists on GORCMRL.January 2005 <strong>Student</strong> <strong>Release</strong> <strong>7.0</strong>Confidential <strong>Release</strong> <strong>Guide</strong> 147

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!