2018-12-05 - IMS EDU-API Task Force
Date
Dec 5, 2018
Attendees
@Adam Sottosanti (Deactivated)
@Diana Antova (Absent)
@Steven Maglio (Absent)
Goals
Capture meeting notes for those who could not attend
Discussion items
Time | Item | Who | Notes |
---|---|---|---|
|
Here are some random scribbled notes as I tried to understand: Coversation led by BYU Group Affiliation BYU API - BYU API - Concept of the person API is “Here is everything we know about a person” Person Object is a GIANT VIEW of the person, everything related to a person Personal Question/ Thought: BYU Person Objects pulls from multiple data sources, not just a single source. The Person API is an aggregate of that data. Processing real time data from SQL is not probably very ideal for something like this so I’m wondering if they use an intermediary system to capture source data changes in real time and publish changes to a data stream which becomes the source of the API. Authorizations are done at the "Field Set" level, which makes the larger data set easier to digest as applications only get access to what they have access to Question about Relationships Question regarding Demographics: Comment: There are cases where data when used together becomes more sensitive than any of the individual pieces of data alone. The example they gave was Combining Class Schedule with Course Enrollment. Security: Concept of securing "Field Sets" instead of at the field level Fields may appear in multiple field sets/duplicated Vocabulary LIS Model uses basic vocabulary to describe things whereas BYU uses specific vocabulary.
Concept of Publishers/Subscribers to areas. Subs can/do get notified when a subject area has changed since they last received data. What changed is less clear, can result in "change messages" that are really not applicable to all subs. Comment: Universities will always need "one more field" Having a standardized extension mechanism for adding extensions needs to be available and built into the process. "is this extension local (for one school) or something that should be pushed to the main. Free For All approach to adding things Creates 5 different ways to define the something = Bad. review of eduPerson model. BYU has a credentials table, so that as credentials change the can handle it. Things that aren't global like NetID, ByuID become more global type of credentials, this is handled.
| ||
| Not Covered | ||
|
|
| They asked for volunteer schools that may want to be in a Proof Of Concept for this project along with Oregon State. I was NOT sure if we were interested in this. @Steven Maglio / @Diana Antova |
|
| Not Covered |