Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Target date

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 sent out for validation against previous external reporting (Brian Cody, Sara Abbott, IR)

by Christmas

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

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)

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?

  • No labels