...
A. Person
Basic bio/demo data
Revision to first draft?
Advanced bio/demo data
Undergraduate school
Custom requests
...
- 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