...
Target date
Key:
Nutrition/GSBS (TUH)
TUSMGP (TUP)
Vet (TUV)
Fletcher (TUF)
Bold are external deliverables
Items in Dark grey text have been delivered
[brackets] identify dependencies
“Sprint” Schedule by Data Grouping Deliverable
Sprint date | Application/Person v1 (Beth) | Engagement v1 (Helen) | Schools v1 (Beth) | Programs v1 | General |
---|---|---|---|---|---|
Completed |
| ||||
by Thanksgiving |
Basic Person and Application Feeds set up in 4 instances/5 schools (Vet, Fletcher, TUSMGP, GSBS/NUTR)
Cross-check queries set up in each instance
Query data validated against other external reporting (Brian Cody, Sara Abbott, IR)
|
|
|
| ||
by Christmas |
|
|
|
|
|
January 2-18, 2025 |
|
|
|
|
|
January 21- February 7 |
|
| |||
February 10 - March 1 |
| ||||
March 4 - March 21 |
|
Data Grouping Deliverables
Data Grouping | Version/Phase | Description | Priority (1 - critical, 5 - nice to have) |
---|---|---|---|
Person | v1 | Basic bio/demo data, record created date, Tufts EMPLID, Hubspot flag | COMPLETE |
Person | v2 | Most recent program of interest, lead status flags/field? | 1 |
Person | v3 | Socioeconomic indicators | 2 |
Person | v4 | ||
Application | v1 | Basic application details, SIS program codes, basic status flags, basic funnel dates | COMPLETE |
Application | v2 | Advanced funnel dates, advanced status flags | |
Engagement | v1 | RMI form submission, event registration, source import | 1 |
Engagement | v2 | ||
Engagement | v3 | ||
Schools | v1 | Primary US institution attended (bachelor’s degree awarded or expected) and major | 1 |
Schools | v2 | ||
Program Details | v1 | Cycle dates, basic program details, enrollment targets | 1 |
Program Details | v2 | Application review process details | |
Program Details | v3 | ||
Phases:
A. Person
Basic bio/demo data
Review and revision period
Advanced bio/demo data
Undergraduate school
Custom requests
...
What happens to old data?
More access to update fields?
Who is in charge of naming fields/naming conventions?
Where do we solve the “fuzzy” definitions, in Slate or Denodo? To the “university” standard?
e.g. socioeconomic indicator
school-specific clarifications happen in Slate, University wide “joins”/translations happen in Denodo?
e.g., definition of “admitted” is school-specific?
e.g., IPEDS classification is University/Denodo?
Data Collections
Person
Simple bio/demo data
Application
Simple program/app data
Funnel Dates
Complete Date
Interview Date
Invite to Interview Flag
Fee waived
HRSA/Socioeconomic Indicators
Application review indicators
GPA
Decline for institution
Schools
Engagements
Lead Form submissions
UCM/Hubspot
First Source
Flags
Submitted a form
Registered for an event
Contacted the school
Program Dataset (Meta data about programs)
Cycle dates
Application Open
Application Deadline
Decision dates
Semester Start date (race release)
Fiscal Year
Academic Year
Enrollment targets?
Program length
Program launch date/term
Program close date
Program Application Review stuff
Do they require interviews?
Rolling admission?
Number of required recommendations
Required test scores?
Definition of complete application
Requirements for complete post-submission? What is collected after you submit?
Fee waiver process?
Application fee amount?
Location
Format/Modality
Degree or non-degree
SIS codes
PF codes
Tuition
Scholarship?
Program Staff (use for content blocks?)(use the existing user table?)
Admissions Director
Manager, etc.
Admissions Counselor/staff
Program selectivity rating
Instances
Vet
Nutrition
GSBS
TUSMGP
Fletcher
Milestones
Identify data to be provided
Identify level of data inaccuracy
Identify causes of data inaccuracy
Retroactively “fix” inacurate data
Business process to ensure data remains accurate
Audit process to identify future inacuracy
Slate Query v1
Data review/validation
Review internally (Helen or Beth cross-check)
External stakeholders (Brian,
Slate Query v2
Refresh/Add query to Denodo