2018-12-19 - IMS EDU-API Task Force

• Analysis of Person Models

Common EDU API Matrix: https://docs.google.com/spreadsheets/d/1ky2yASn8YU2yXhL0MPfwpKOQBu805lxbR0tARWOhBis/edit?usp=sharing

Andrew Marmor

Andrew Marmor

• Microsoft has developed a higher-ed data model,

• Microsoft dynamics (business applications platform)

• Available on github: https://github.com/Microsoft/Dynamics-365-Industry-Accelerators/tree/master/edu

• https://appsource.microsoft.com/en-us/product/dynamics-365/mshied.highereducationcommondatamodel?mktcmpid=blog_CISlnEvalToolLaunchIMML&src=DataAmpMainBlog%2Cwebsite&tab=Overview

• Privacy

• Microsoft model has single FERPA field, discussion on how to handle individual privacy selections

• Higher Ed Accelerator requires Dynamic 365 license, seems to be a platform to build additional apps (PowerApp) and analytics (PowerBI) directly on top of . https://community.dynamics.com/365/b/dynamics365isvsuccess/archive/2018/10/30/a-first-look-at-the-dynamics-365-higher-education-accelerator

• Person object is called Contact in MS model

• Question: How to tie enrollment to contact

  • Academic Period Detail ties together

• Question: Are instructors and students both contacts

  • Yes - Contact has a Type = STUDENT, Instructor etc…

  • Account - Entity, again can have a Type of SCHOOL

• Review of timelines for work going forward

Next steps: Now that we have all of the data and examples of multiple different models for Person, what do we do now?

Consensus

• Create a plain list of everything we would want in a Person API with proposed fields that would be included as a step prior to adding anything to GitHub/Swagger.

• Review

• Standardize Fields, Naming Convention, etc..

• Potentially begin to publish a DRAFT person model to GitHub

• Create Swagger sandbox of Draft model to iterate individual needs against

• Once vetted, do we generate an OpenAPI definition?

Question: Jarred U.Wi - Should we fork/copy BYU’s swagger spec as a start before starting from scratch.