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 2 Next »

Phases:

A. Person

  1. Basic bio/demo data

  2. Revision to first draft?

  3. Advanced bio/demo data

    1. Undergraduate school

  4. Custom requests

B. Application

  1. Basic application data

  2. Advanced application data

  3. Custom requests

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

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

  2. Advanced interaction activity

    1. Messages

  3. Custom interaction activity

D. Messages (Deliver Campaigns)

Phase

School/Instance

Delivery Date (Slate Team)

Delivery Date (Denodo Team)

A1

Vet

B1

Vet

C1

Vet

D1

Vet

A1

TUSMGP

B1

TUSMGP

C1

TUSMGP

D1

TUSMGP

A1

NUTR

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

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

  • No labels