Lead/Admissions Denodo Data Roadmap

Owned by Helen Williams
Last updated: Dec 17, 2024 by Elizabeth Storrs
4 min read

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

Sprint date

Application/Person v1 (Beth)

Engagement v1 (Helen)

Schools v1 (Beth)

Programs v1

General

Completed

  • Slate queries finalized and connected to Denodo for Vet, GSBS, and Nutrition.

 

 

 

 

by Thanksgiving
Nov 27, 2024

  • Slate queries finalized and connected to Denodo for TUSMGP and Fletcher.

  • Query/data structure draft created [Nutrition as model].

  • Sample spreadsheet of data provided to UCM.

  • develop prospectus for cleaning school data

 

  • Start technical conversation series with Matt

  • Finalize next data priorities

  • Build out interim marketing report for Nutrition

by Christmas
Dec 20, 2024

  • Applicants who straddle multiple terms (defers, early admits, dual programs): start conversation @ data definitions [IR]

  • Draft queries created in Fletcher, Vet, GSBS, and TUSMGP.

  • Meeting with UCM on expectations.

  • Business process guide for Slate users providing engagement data through Denodo finalized.

  • determine path for schools data quality initiative

  • feed of NUTR 2025 cycle primary undergraduate school and major

  • Initial dataset built in TUSMGP with first-priority fields

  • complete Connecting and Combining Data with Denodo course

January 2-18, 2025

  • identify all of the types of applicants who straddle multiple terms; draft standard business practices for handling/counting them

  • Query finalized and connected to Denodo for Nutrition.

  • Meet with Vet and Fletcher to understand their

  • [funding]

  • Populate data in TUSMGP

  • Demonstrate dataset to stakeholders

  • Copy dataset model to Fletcher, Vet, GSBS, and Nutrition

  • Tableau training

January 21- February 7

 

  • Query finalized and connected to Denodo for TUSMGP and GSBS

 

  • Ask stakeholders to populate their datasets.

  • Build query to send data to Denodo for TUSMGP

 

February 10 - March 1

 

 

 

  • Copy query to Fletcher, Vet, GSBS, and Nutrition

 

March 4 - March 21

 

 

 

  • Query finalized and connected to Denodo for TUSMGP, Fletcher, Vet, GSBS, and Nutrition

 

 

Data Grouping Deliverables

 

Data Grouping

Version/Phase

Description

Priority (1 - critical, 5 - nice to have)

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

  1. Basic bio/demo data

  2. Review and revision period

  3. Advanced bio/demo data

    1. Undergraduate school

  4. Custom requests

Instance

est. delivery to DS&E

Available to Selected End Users

Review Period

Instance

est. delivery to DS&E

Available to Selected End Users

Review Period

Vet

 

 

 

Grad Hlth Sci (NUTR/GSBS)

 

 

 

 

TUSMGP

 

 

 

Fletcher

 

 

 

 

 

B. Application

  1. Basic application data

  2. Review and revision period

  3. Advanced application data

  4. Custom requests

 

C. Interaction/Activity/Source Data (Inquiry Details)

  1. Basic interaction activity (incl. program of interest)

  2. Review and revision

  3. Advanced interaction activity

    1. Messages

  4. Custom interaction activity

 

D. Messages (Deliver Campaigns)

  1.  

 

Phase

School/Instance

Delivery Date (Slate Team)

Phase

School/Instance

Delivery Date (Slate Team)

A1/B1

Vet

 

C1

Vet

 

D1

Vet

 

A1/B1

TUSMGP

 

B1

TUSMGP

 

C1

TUSMGP

 

D1

TUSMGP

 

A1/B1

NUTR

 

C1

NUTR

 

D1

NUTR

 

 

 

What does “done” look like?

Query in Slate is built and configured with web services
Denodo “view” is built?
Data refresh is scheduled/ongoing
Field definitions are added
Query description is added
Access/permissioning is configured?

 

Notes:

  • Do we need a “beta” period?

  • Feedback from stakeholders/clients--how to factor that into the project plan?

  • How do we handle ongoing requests/concerns

  • Capturing the next “core fields” for the University

  • Goal is to build a dashboard that is used for all schools

  • Gather admisisons directions to create standard definitions (e.g. Veterans)

    • Under Data Governance Committee

    • Advisory vs. Directive?

  • Slate team builds the queries sent to Denodo that creates the “base view” – only for DSE

 

Questions for Group meeting/Matt

  • 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

  1. Person

    1. Simple bio/demo data

    2.  

  2. Application

    1. Simple program/app data

    2. Funnel Dates

      1. Complete Date

      2. Interview Date

    3. Invite to Interview Flag

    4.  

    5. Fee waived

    6. HRSA/Socioeconomic Indicators

    7. Application review indicators

      1. GPA

    8. Decline for institution

  3. Schools

  4. Engagements

    1. Lead Form submissions

    2. UCM/Hubspot

    3. First Source

    4. Flags

      1. Submitted a form

      2. Registered for an event

      3. Contacted the school

  5. Program Dataset (Meta data about programs)

    1. Cycle dates

      1. Application Open

      2. Application Deadline

      3. Decision dates

      4. Semester Start date (race release)

      5. Fiscal Year

      6. Academic Year

      7. Enrollment targets?

    2. Program length

    3. Program launch date/term

    4. Program close date

    5. Program Application Review stuff

      1. Do they require interviews?

      2. Rolling admission?

      3. Number of required recommendations

      4. Required test scores?

      5. Definition of complete application

      6. Requirements for complete post-submission? What is collected after you submit?

    6. Fee waiver process?

    7. Application fee amount?

    8. Location

    9. Format/Modality

    10. Degree or non-degree

    11. SIS codes

    12. PF codes

    13. Tuition

    14. Scholarship?

    15. Program Staff (use for content blocks?)(use the existing user table?)

      1. Admissions Director

      2. Manager, etc.

      3. Admissions Counselor/staff

    16. Program selectivity rating

 

 

 

Instances

  1. Vet

  2. Nutrition

  3. GSBS

  4. TUSMGP

  5. Fletcher

Milestones

  1. Identify data to be provided

  2. Identify level of data inaccuracy

  3. Identify causes of data inaccuracy

  4. Retroactively “fix” inacurate data

  5. Business process to ensure data remains accurate

  6. Audit process to identify future inacuracy

  7. Slate Query v1

  8. Data review/validation

    1. Review internally (Helen or Beth cross-check)

    2. External stakeholders (Brian,

  9. Slate Query v2

  10. Refresh/Add query to Denodo