SIS SIG - Meeting 1 - 2023.09.13
- Eric Jansson
- Mustafa Yilmaz
- Ann Su
Owned by Eric Jansson
Participants
Click here to expand...
First Name | Last Name | Organization |
Matt | Hoffman | Aeries Software |
Ronald | Peasha | Infinite Campus |
Jennifer | Sauro | Infinite Campus |
Jim | Robertson | PowerSchool |
Sean | Casey | Ed-Fi Alliance |
Eric | Jansson | Ed-Fi Alliance |
Vinaya | Mayya | Ed-Fi Alliance |
Jeff | Putnam | Ed-Fi Alliance |
Sayee | Srinivasan | Ed-Fi Alliance |
Mustafa | Yilmaz | Ed-Fi Alliance |
Support: Ann Su, Ed-Fi Alliance
Agenda
- Welcome / introductions
- Review of SIG goals
- Level 1 error messages – possible technical improvements (Vinaya)
- Difficult extensions, data model designs or business logic at the API interface (review Ed-Fi efforts to improve this + feedback/proposals for other solutions) (Eric)
- Validation error management
Notes
SIG Goals discussion
- MSP ecosystem and SIs create the problems with fragmentation, not just states - we need to think about ways to also address improvement there
- Ed-Fi could benefit from use cases for data elements to make the semantics clear
Actions
- Action: add MSP and SIs and to goal #3
- Action: add more semantics to goal #1
Validation errors
Thoughts on dependency order failures?
- Farther down in hierarchy the errors are harder
- The killer: if the student resource is missing, the error is bad. Note: this has been fixed.
- Missing dependencies generate massive retries
- What is the responsibility of vendors with regards to support for dependency order? Is expectation that vendors check dependencies? Opposing view from SIS systems was presented
- Perspective 1: the API should send back a clear error message saying that a dependency was missing
- Perspective 2: the vendor should check dependencies before messages are sent and not send them if those are missing
Topic for Next meeting:
- Review state alignment work
- Review playbooks
- Use cases that underlay our specifications