Attention: Confluence is not suitable for the storage of highly confidential data. Please ensure that any data classified as Highly Protected is stored using a more secure platform.
If you have any questions, please refer to the University's data classification guide or contact ict.askcyber@sydney.edu.au
2019-12-11 Data Stream - Planning next Steps
- Jules Levin
Date
Dec 11, 2019
Participants
@Jules Levin
@Brad Fernandes (Unlicensed)
@Yeng Sembrano
Goals
Data Stream Planning
Discussion topics
Description | Who |
|---|---|
Cleansing of Advance data is a largely manual process. | Yeng |
Discrepancies are identified and then a business rule created and script writing to look for the more discrepancies and fix | Yeng |
For Alumni, information such as degrees, date of birth are often not valid | Yeng |
For donors, giving information may not be correct | Yeng |
Yeng documents the rules, writes the scripts in SQL and updates. About 20 rules identified. 15 rules scripted. | Yeng |
Three categories for cleansing Development (DO) | Yeng |
Prospect health will also look at data cleansing of contact details | Yeng |
Team needs access to SITS back-end to do compare and validation. One off extract provided by ICT | Yeng |
Target timeline is for first Release of Phoenix to go live in June/July 2020 so Advance data cleansing required prior | Jules |
Cleansing is not a linear process so difficult to time box but target is to have cleansing done by March 2020 | Yeng |
After cleansing is data enrichment - might be with new CRM. Prospect health, could bring in data | Yeng |