SCT Banner Student / Release Guide / 7.0

More documents

Recommendations

Info

Section 5 Common Matching - FunctionalSetting Up Common MatchingCommon Matching specifically affects the SPAIDEN, SRAQUIK, SAAQUIK,SRIPREL, SAAEAPS, and SHAEDIS forms in Student. The Common MatchingEntry Form (GOAMTCH) is used with these forms as follows:• Users who are not excluded on GORCMUS will see GOAMTCH automaticallyfrom SPAIDEN, SRAQUIK, and SAAQUIK. If they are excluded, data entry willremain the same as in pre-7.0 Banner releases.• GOAMTCH can be turned off when a new person is created on SPAIDEN,SRAQUIK, and SAAQUIK. It cannot be turned off when a new person iscreated on SRIPREL, SAAEAPS, or SHAEDIS, since GOAMTCH replaces theobsolete SOQMTCH and SRQMTCH forms formerly used by those threeforms.• GOAMTCH replaces the SOQMTCH and SRQMTCH forms that werepreviously used by SRIPREL, SAAEAPS, and SHAEDIS to perform matching.SOQMTCH and SRQMTCH are now obsolete.• Data in the temporary tables behind SRIPREL, SAAEAPS, and SHAEDIS iscopied to the GOAMTCH temporary table. If changes to that data are made onGOAMTCH, the changed data will be used by the calling form (SRIPREL,SAAEAPS, or SHAEDIS) when a new record is loaded.• For SRIPREL, SAAEAPS, and SHAEDIS, GOAMTCH is used to attempt tomatch data for a person in a temporary table to data for a person alreadycreated in Banner, before the person is loaded into Banner.• The interface codes on STVINFC are now associated with Common Matchingrules using the Common Matching Source field. If the codes are not tied toCommon Matching, they will not be used in the matching process.Please refer to the SCT Banner General 7.0 Release Guide for more information on theGeneral forms used with this enhancement.Setting Up Common MatchingIn order to use Common Matching at your institution, you must enable it using theOnline Matching Process Enabled (Indicator) on the Installation Controls Form(GUAINST).Use the following steps to set up Common Matching processing.1. Create source codes.Use the Common Matching Source Codes Validation Form (GTVCMSC) tocreate the various source codes that may be used in Common Matching. Theseare similar to the interface codes that exist in Banner Student. Rules will beassigned to these source codes to be used with the matching algorithm.Student Release 7.0 January 2005146 Release Guide Confidential
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 Banner Student 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 BannerGeneral (i.e, matching on high school data for Banner Student).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 Student Release 7.0Confidential Release Guide 147
Page 1 and 2:
SCT BannerStudentRelease GuideJanua
Page 3 and 4:
Release GuideStudent SystemIntroduc
Page 5 and 6:
Table of ContentsGeneral Student -
Page 7 and 8:
Table of ContentsHow the New Matchi
Page 9 and 10:
Table of ContentsLearner Curriculum
Page 11 and 12:
Table of ContentsLearner Module Val
Page 13 and 14:
Table of ContentsChanged Tables . .
Page 15 and 16:
Table of ContentsPCU Tape Load Regu
Page 17 and 18:
IntroductionIntroductionThis docume
Page 19 and 20:
Section I New User Interface - Func
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Section 2 New Banner Online Help -
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Section 3 Concurrent Curricula Phas
Page 43 and 44:
Page 45:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96: Section 3 Concurrent Curricula Phas
Page 105 and 106: Section 3 - Concurrent Curricula Ph
Page 111 and 112: Section 4 New Value-Based Security
Page 145: Section 5 Common Matching - Functio
Page 149 and 150: Section 5 Common Matching - Functio
Page 181 and 182: Section 5 - Common MatchingSample R
Page 189 and 190: Section 6 Improved Drop/Withdrawal
Page 197 and 198:
Section 6 Improved Drop/Withdrawal
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Section 8 New Value-Based Security
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Section 9 Common Matching - Technic
Page 261 and 262:
Section 9 Common Matching - Technic
Page 263 and 264:
Section 10 APIs - TechnicalAPI Disc
Page 265 and 266:
Section 10 APIs - TechnicalAPIs Use
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Section 10 APIs - TechnicalChanged
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
Section 12 Miscellaneous Enhancemen
Page 297 and 298:
Page 299 and 300:
Page 301 and 302:
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
Page 315 and 316:
Page 317 and 318:
Section 13 Problem ResolutionsCatal
Page 319 and 320:
Section 13 Problem ResolutionsSched
Page 321 and 322:
Section 13 Problem ResolutionsSched
Page 323 and 324:
Section 13 Problem ResolutionsCours
Page 325 and 326:
Section 13 Problem ResolutionsSuppo
Page 327 and 328:
Section 13 Problem ResolutionsLocat
Page 329 and 330:
Section 13 Problem ResolutionsLocat
Page 331 and 332:
Section 13 Problem ResolutionsRecru
Page 333 and 334:
Page 335 and 336:
Page 337 and 338:
Section 13 Problem ResolutionsAdmis
Page 339 and 340:
Page 341 and 342:
Page 343 and 344:
Page 345 and 346:
Section 13 Problem ResolutionsGener
Page 347 and 348:
Section 13 Problem ResolutionsRegis
Page 349 and 350:
Page 351 and 352:
Page 353 and 354:
Page 355 and 356:
Page 357 and 358:
Page 359 and 360:
Page 361 and 362:
Page 363 and 364:
Page 365 and 366:
Page 367 and 368:
Section 13 Problem ResolutionsAcade
Page 369 and 370:
Page 371 and 372:
Page 373 and 374:
Page 375 and 376:
Page 377 and 378:
Page 379 and 380:
Page 381 and 382:
Page 383 and 384:
Page 385 and 386:
Page 387 and 388:
Page 389 and 390:
Section 13 Problem ResolutionsCAPP
Page 391 and 392:
Page 393 and 394:
Page 395 and 396:
Section 13 Problem ResolutionsOvera
Page 397 and 398:
Page 399 and 400:
Page 401 and 402:
Page 403 and 404:
Section 13 Problem ResolutionsFTES
Page 405 and 406:
Section 13 Problem ResolutionsRepor
Page 407 and 408:
Section 13 - Problem ResolutionsSam
Page 409 and 410:
Page 411 and 412:
Page 413 and 414:
show all

SCT Banner Student / Release Guide / 7.0

Create successful ePaper yourself

Delete template?

Save as template?