閉環：防止數據錯誤激增.ppsx

《閉環：防止數據錯誤激增.ppsx》由會員分享，可在線閱讀，更多相關《閉環：防止數據錯誤激增.ppsx（38頁珍藏版）》請在三個皮匠報告上搜索。

1、Closing the Loop:Preventing Data Errors from ProliferatingCeniya Palmer-BaumannUniversity of Massachusetts DartmouthDan MoranSolidanHolger DippelUniversity of Massachusetts DartmouthCLOSING THE LOOP:PREVENTING DATA ERRORS FROM PROLIFERATINGSlate Summit 2023WHO WE ARECeniya Palmer-BaumannDirector of

2、Information Systems,UMass Dartmouth(previously Associate Director of Admissions&Lead Slate Captain)cpalmerbaumannumassd.eduDan MoranFounder,SHolger DippelChief Information Officer,UMass Dartmouthholger.dippelumassd.eduWE WILL TALK ABOUT Slate in the context of UMass&UMass Dartmouth Slate-PeopleSoft

3、Integration Managing Integration Data Errors Q&AOVERVIEW:SLATE UMASS(D)UMASS DARTMOUTHMission StatementUMass Dartmouth distinguishes itself as a vibrant,public research university dedicated to engaged learning and innovative research resulting in personal and lifelong student success.The University

4、serves as an intellectual catalyst for economic,social,and cultural transformation on a global,national,and regional scale.UMASS ALL SLATEUMASS DARTMOUTHEnrollment:7,218 Undergraduate/College Now(Alternative Admissions)Graduate/Law Online&Continuing Education Non-DegreeDemographics 50%First Generati

5、on students 82%of population are from Massachusetts 35%Students of Color 28%Transfer studentsSLATE UMASS DARTMOUTH Implemented:Spring 2021 Preparing for 3rd cycle in Slate 5(!)admissions areas in a single Slate instance:Undergraduate Alternate Admissions Graduate Law School Continuing Education Mark

6、eting coordinates recruitment and communicationsBOSTON,DARTMOUTH,LOWELLSLATE PROJECTPEOPLESOFT INTEGRATIONPEOPLESOFT APP SOURCESUMASS BOSTON,DARTMOUTH,LOWELL Campus-managed Slate instances Shared multi-institution PS Campus Solutions instance Standardized reporting roll-up Slate SFTP export queries

7、Standardized integrations via BoomiINTEGRATION DELIVERABLESSTANDARDIZED INTEGRATIONSSlate Export FileCriteriaSchedulePeopleSoft Return FileApp create(UGRD,GRAD,LAW)Application in awaiting decision,awaiting confirmation or decidedEach export intervalPeopleSoft student idPeopleSoft app numberBiodemo d

8、ata*Any recordMidday,eveningApp data*Any recordMidday,eveningApp activity&decisionsNew records onlyMidday,eveningEducation history*Any recordEveningTest scoresNew records onlyEveningStudent groupsNew records onlyMidday,eveningService indicatorsNew records onlyMidday,eveningDeposit transactionsNew re

9、cords onlyAfternoonMerit scholarshipsAny recordOvernight(Mondays only)Document export to DINew records onlyOvernightMorning,midday,eveningPS status update file*Boomi compare produces delta file for PS import efficiencyPEOPLESOFT Some PeopleSoft customizations i.e.Suspense Effective Dates Test Score

10、mapping table for UGRD and GRAD Used delivered AAWS to load into the CTM(constituent transaction management)Applications would post to PS delivered tables(used the Slate Ref Nbr in the Ext Adm Appl Nbr)External Education was the most troublesome integrationPEOPLESOFT CUSTOM STAGING TABLES Series of

11、tables to track transactions for initial insert,change in status,update of PS App Nbr and PS Emplid(student id)Captured data,filenames,runtimes etc.Each table started with the same 10 fields for consistency Some PeopleSoft Customizations i.e.Suspense Effective Dates Extremely helpful during testing

12、and stabilization period Actual component interface errors would be saved to this tableINTEGRATIONERROR HANDLINGPROBLEMIMPACTS TO OPERATIONS Inconsistent status updates and movement through processes Misalignment of status updates carried through post-matriculation processes Completed apps not“movin

13、g”to counselor queues=Bottleneck of completed apps without decisions Constant movement/toggling between two systems Reporting discrepancies Data inconsistencies to other integrated systems(Housing,Financial Aid,Health services,orientation,etc.)PROBLEM:DATA ERRORS At first:poking around wheres the er

14、ror?Slate?PeopleSoft?Then:emails with error spreadsheets NEED A MANAGEABLE SOLUTION1.Add error explanations2.Send error reports to Slate SFTP3.Handle errors in Slate4.Prevent repeat or cascading errorsIN SLATESTORE:EntityIMPORT:Source formatRESOLVE:Widget and tabPREVENT:Query filter STOREMultiple er

15、rors can occur over time fora single person/application record1-to-many relationshipSQL database:table or objectSlate:Entity(via Database-Entities)STORE:INTEGRATION ERROR ENTITYIMPORT:SOURCE FORMATRESOLVE:WIDGET AND CUSTOM TAB1.Create a form with scope of“Entity Widget”2.Create a custom widget(form)

16、with scope“Application Page”and add the entity widget form3.Create an application custom tab using the custom widget1.FORM WITH SCOPE OF“ENTITY WIDGET”2.CUSTOM WIDGET3.CUSTOM TABRESOLVE:APPLICATION TABRESOLVE:INTEGRATION ERROR WIDGETPREVENT:EXPORT QUERY FILTERPROBLEM SOLVED?Integration errors import

17、ed&stored in SlateError management in application contextQuery filters prevent cascading or repeat errorsBUTHow are Slate admins aware of records with errors?Clean data!Reporting accuracy&alignment Efficient application processing/timeliness of decisionsSLATE ADMIN DASHBOARDTHANK YOU!Ceniya Palmer-BaumannDirector of Information Systems,UMass Dartmouthcpalmerbaumannumassd.eduDan MoranFounder,SHolger DippelChief Information Officer,UMass Dartmouthholger.dippelumassd.edu#SlateSummit