SCT Banner Student / Release Guide / 7.0

More documents

Recommendations

Info

Section 4 New Value-Based Security and Personally Identifiable Information Security Using Fine-Grained Access Control - FunctionalObsolete FormObsolete FormValue-Based Security Person Access Query Form (SOIVPAC)This form is being desupported in Banner Student. The new FGAC PredicateInquiry Form (GOIFGAC) is used in Banner 7.0 to display the predicates by tableand user.Changed MenusStudent System Management Menu (*SMANAGER)The Value-Based Security Person Access Query Form (SOIVPAC) has been removedfrom the Student System Management Menu (*SMANAGER).Student Release 7.0 January 2005144 Release Guide Confidential
Section 5 Common Matching - FunctionalOverviewSection 5Common Matching - FunctionalThis enhancement is new for Release 7.0.OverviewThe Common Matching enhancement has been designed to prevent the creation ofmultiple PIDMs for a single person or non-person in Banner. Basic person APIs havebeen developed to provide common logic for how all PIDMs are created. These APIsinclude: identification information (SPRIDEN), biographic and demographicinformation (SPBPERS), address information (SPRADDR), telephone information(SPRTELE), email information (GOREMAL), and emergency contact information(SPREMRG). You can turn Common Matching on and off as needed, either for theinstitution or for a specific user.Common Matching uses a central, rule-based algorithm to check for possibledatabase matches before a new person or non-person record is inserted into theSPRIDEN table. The same algorithm is used for new records created by data loadedvia batch processes and data entered in online forms (such as SPAIDEN). A newmatch package is used to perform the matching algorithm.You can still perform required searches from SPAIDEN before new records areinserted into the database. If a person or non-person record already exists, you canupdate it with new information from the current source, such as a new address typeor a new email type. The existing record will not be overwritten. Alias tables inBanner General are now used to store aliases for first and middle names, as well asnon-person names. These aliases are used by the matching algorithm.New forms in Banner General are used to set up Common Matching. The newCommon Matching Entry Form (GOAMTCH) is used with SPAIDEN and otherforms in Student to enter information for a new ID and then execute the matchingprocess before a new PIDM is created in Banner. You can enable the matchingprocess at your institution using the Online Matching Process Enabled (Indicator)on the Installation Controls Form (GUAINST). If the matching process is enabledon GUAINST, all users are required to perform matching.You can exempt selected users from the matching process on the new CommonMatching User Setup Form (GORCMUS). You can also set up user online matchingsource defaults on GORCMUS. You can build multiple rules on the new CommonMatching Rules Form (GORCMRL) for matching persons or non-persons, usingfields and field lengths from a new data dictionary. Special matching procedures canalso be attached to rules allowing the algorithm to match on fields that are notcommon (i.e., high school data).January 2005 Student Release 7.0Confidential Release Guide 145
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: 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 143: Section 4 New Value-Based Security
Page 147 and 148: Section 5 Common Matching - Functio
Page 181 and 182: Section 5 - Common MatchingSample R
Page 189 and 190: Section 6 Improved Drop/Withdrawal
Page 195 and 196:
Section 6 Improved Drop/Withdrawal
Page 197 and 198:
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?