MSP SIG - Meeting 19 - 2024-02-06
- Eric Jansson
- Ann Su
Owned by Eric Jansson
Participants
Click here to expand...
First Name | Last Name | Organization |
Mark | TenHoor | Education Analytics |
Geoff | McElhanon | Edufied |
Lyria | Zeh | Edufied |
David | Cintron | EdWire |
Jean-Francois | Guertin | EdWire |
Jim | Rife | ESP |
Michael | Watson | InnovateEDU |
Eric | Jansson | Ed-Fi Alliance |
Kathleen | Browning | Ed-Fi Alliance |
Nate | Gandomi | Ed-Fi Alliance |
Jason | Hoekstra | Ed-Fi Alliance |
Jeff | Putnam | Ed-Fi Alliance |
Mustafa | Yilmaz | Ed-Fi Alliance |
Support: Ann Su, Ed-Fi Alliance
Agenda
- Improving SEA data model alignment: continues to be an issue for efficient vendor support of SEA efforts
- Tech Congress agenda/program input
- 2023 holdover items
- Assessment data integration – review high demand vendors and how to position better for vendors (https://edfi.atlassian.net/wiki/display/ESIG/MSP+SIG+-+Meeting+18+-+2023-12-12)
- OneRoster and Ed-Fi API (see notes from https://edfi.atlassian.net/wiki/display/ESIG/MSP+SIG+-+Meeting+16+-+2023-11-07) including assessment rostering (see https://edfi.atlassian.net/wiki/display/ESIG/MSP+SIG+-+Meeting+13+-+2023-09-26)
- CEDS integration strategies (https://edfi.atlassian.net/wiki/display/ESIG/MSP+SIG+-+Meeting+10+-+2023-08-15)
Notes
Improving SEA data model alignment
MSPs in general advised a stronger guidance to SEAs from the Alliance: they felt like the message was not being heard. Sub recommendations included:
- use case studies or examples to detail impacts better; i.e., show a state the costs to vendors and the ecosystem when alignment mistakes are mad
- include the impacts of SEA release processes
- include that customizing the Ed-Fi open source implementation can also lead to issues
Tech Congress Feedback
- Please don’t stack technical roadmap sessions (solved for 2024!)
- Love the spaces and times for intentional conversations (time between sessions), and the stakeholder groups were good for this as well (will do again in 2024)
More narrow topics
- Data validations API and specification: this has been a long-standing proposal and to my mind would make a great deep-dive session. If this added additional efficiency to state reporting and data hub operations (as we think it would), it could be very impactful in lowering LEA costs.
- Upgrade processes & movement to ODS7.1: the MSP community felt that there would be benefit in sharing lessons learned about the move to ODS 7.1 (ODS 7.1 makes a lot more configuration options available
- Admin API: would love to engage more on how this might grow and expand over time.
Future Agenda Items
- Feature flags for new features - should we look at this as a pattern (example, expose validations API behind a feature flag)
- CEDS & SLDS grants to support EDFacts with Generate - share out the learnings (e.g., element mapping technologies, etc.)