4/3/2017 – 04/14/2017
Completed
- POC - Grad Division - Complete.
- Receiving the Registrar files for the legacy data input (SIF/SOC) - Complete.
- Performance Issue – Worked with Nisha to – Complete.
- Confirmation the list of source for Grad Aid - Complete.
- Development for Fund Detail Report - Complete.
- Financial Aid - Mapping spec Documentation.
...
- Performance issue on the ODS instance.
- Establish the connection for the known Legacy data inputs through Informatica.
- Continue to work with the remaining technical leads to identify the legacy data connectivity.
- Start the ETL Development of the known Legacy inputs.
- Grad Div - Development
3/20/2017 – 03/31/2017
Completed
- POC - Function Rewrite - Complete.
- Performance Issue – Worked with Nisha to identify the bottleneck – Complete.
- Grad Aid - Informatica connectivity established.
- Grad Div – Informatica connectivity established.
- Ticket created to cleanup Legacy schemas and corresponding users.
...
- POC - Grad Division
- Establish the connection for the known Legacy data inputs through Informatica.
- Continue to work with the remaining technical leads to identify the legacy data connectivity.
- Start the ETL Development of the known Legacy inputs.
- Grad Aid - Development.
- Financial Aid - Mapping spec Documentation.
3/6/2017 – 03/17/2017
Completed
- Demo Registrar POC Enrollment report - Complete.
- Support the POC on Enrollment report.
- Ticket created to drop the old schemas for legacy data – Done.
- Performance Issue - Loading data into KFS – complete Loaded 300,000 records in 2 min 25 secs and confirmed that it’s the ODS database issue on the poor performance.
- Informatica AWS testing - Complete
- Worked on establishing the firewall between the Grad DB and Informatica.
- Worked on establishing the firewall between the Admissions DB and Informatica.
- Worked on establishing the firewall between the OIR DB and Informatica.
- Rewriting the Financial Aid Database function (Identifying the student is a CA resident or not) in Informatica. – Development Complete.
- Testing of the POC function is on hold as the test environment does not have data in the underlying base tables.
...
- POC Demo – 3/13/2017
- Establish the connection for the known Legacy data inputs through Informatica.
- Continue to work with the remaining technical leads to identify the legacy data connectivity.
- Start the ETL Development of the known Legacy inputs.
2/20/2017 – 03/03/2017
Completed
- Registrar Enrollment report - POC work complete.
- Created a PowerPoint presentation on POC to have a walkthrough on the demo.
- Created indexes to address the report performance.
- Added unique identifier in MST_REG_STUDENT table.
- Added OLD and NEW student ID in the MST_REG_STUDENT table and loaded the same.
- Supported the POC report development activities.
- Creation of separate Legacy schema – Done.
- Discussed about the options for the poor performance of loading the data into ODS tables.
- Worked on establishing the firewall between the Grad DB and Informatica.
- Established the PC connectivity to UG Admissions MySQL DB.
- Established the PC connectivity to OIR database.
- Submitted a request to create a temporary schema in the KFS oracle Database.
- Submitted a ticket to establish the firewall connection between PC and KFSDEV database.
- Provided a brief summary to Chris Schultz regarding the performance issue.
- Rewriting the Financial Aid Database function (Identifying the student is a CA resident or not) in Informatica.
...
- POC Demo – 3/13/2017
- Establish the connection for the known Legacy data inputs through Informatica.
- Continue to work with the remaining technical leads to identify the legacy data connectivity.
- Start the ETL Development of the known Legacy inputs.
2/01/2017 – 2/17/2017
Completed
Met with the team to discuss the need for multiple schemas for legacy data, so will create only one legacy schema(UCI_LEGACY) for all different functional units.
Can we have one schema created to store all functional unit legacy data and name the tables accordingly to segregate the data and identify.
Staging Tables:
STG_REG_SIF
STG_REG_SOC
STG_FINAID_CODE
Composite Tables:
MST_REG_STUDENT
MST_REG_COURSE
Advantages are listed below by going through the above option.
One individual user account.
For reporting it’s easy to join the data or else need to create separate data sources for each of them.
ETL just one connection object created.
ETL code we don’t need to specify schema when you join data across different functional units.
...