Slate Instance | TUP | ||||||
Requestor | Ariana Balayan, Hannay Fridy | ||||||
TTS Staff | Helen Williams | ||||||
Date | 11/1/2023 | ||||||
Status |
| ||||||
Summary Description | Build a way for TUSMGP to accurately and consistently report enrollment funnel data, specifically year-to-year comparisons for started, submitted, complete, admitted, and intends to enroll data points. |
Detailed description of desired deliverable:
Research:
Entity was named Reporting Data (Application)
AFD = Application Funnel Dates
Outcome:
Created a custom entity for Reporting Data (Application) in the TUP database, which is application-scoped and can be used to store status change date (SCD) values for the application record for use in application funnel reporting.
...
Retention policies to delete JD/MPH apps without a reply to the “combined MPH program status” question?
No applications that are deferred (cloned into this cycle) should have created, submitted, or decided dates in the Reporting data entity.
What to do about B/MPH now that they are letting them apply during sophomore year? When people apply “late” how do we count them in the numbers (have app in same cycle/not deferred?)
...
Retention rules to delete reporting data rows on apps tagged with Error - Do not Use
Query to look for applications that have more than one of each kind of AFD
| Expand | ||
|---|---|---|
| ||
Program = PA or PA/MPH Start Term/Year = Spring 2025 Initial query shows that Reporting Data (Application) (RDA) values are: Created = NULL Submitted = populating with date for submitted apps Complete = populating with date 8/2/2024 - spent the day creating files and testing imports into both prod and TEST. Was able to identify the issue with the complete date populating (even though we hadn’t decided how to measure that). Was happening because the existing export/import loop was not excluding PA students and so was passing through the date their Slate app became awaiting decision. Updated the export, then did a retro refresh to delete all existing values, then ran an import with the prereq fulfilled date from CASPA. For 2024 data, figured out that the only applications in Slate are those that got interviewed last cycle, leaving the in progress, submitted but incomplete, and the complete but not reviewed/denied before interview files not in Slate. Created two sets files saved in Box > Projects > Slate Data Audit Cleanup > CASPA 2024 Application Funnel Dates folder, one for the existing apps to update and one for the records that didn’t already have a 2024 application. Plan is for the first group to import just to update the fields on the existing app; for the second group, will import and create unsubmitted applications with AFD updated. This way we aren’t adding to our total for billing reasons. Created a source format in TEST to import the file with the “no applications” records. This worked, matched with existing records or created new ones. Not having the rules fire means the header doesn’t get updated and the CAS ID doesn’t get indexed for the search field… still think that’s better than letting the rules run but should maybe test that? On Monday, need to do the import for the existing applications. also need to update the test source format with the program (forgot about PA vs. PA/MPH but updated the spreadsheet so it is there now). Then run the import for the non-existing applications and have Alessa/Hannah check the deliver campaigns to make sure that those applicants aren’t going to get any emails. Maybe refresh test first? Problems to solve still:
|
Program | Created Date | Submitted Date | Complete Date |
|---|---|---|---|
PA and PA/MPH | CAS/Liaision In Progress Date (date they select our program from CAS) | CAS/Liaision Submitted Date | Date that prereq requirements were reviewed and marked fulfilled |