/
MSP SIG - Meeting 3 - 2023-04-04

MSP SIG - Meeting 3 - 2023-04-04

Aug 15, 2023

Participants

First Name Last Name Organization Marcos Alcozer Ed-Fi Alliance Sean Casey Ed-Fi Alliance David Clements Ed-Fi Alliance Jean-Francois Guertin EdWire Jason Hoekstra Ed-Fi Alliance Eric Jansson Ed-Fi Alliance Vinaya Mayya Ed-Fi Alliance Eshara Mondal Education Analytics Megan Nash Education Analytics Jeremy Perkins Instructure Andrew Rice Education Analytics Mark TenHoor Education Analytics

Materials

Notes

Review of last meeting notes / summary

  • Generally look good.

  • Believed we were talking about sunsetting Data Import?  Answer: yes, Eric to correct that

  • Led to a discussion of sunsetting Data Import 

    • What would the TAG or GAT would think about sunsetting the end user app? Who does the roadmap serve? We know individual LEAs struggle.

    • Broad SIG agreement that we should collaborate on template mapping and sync services generally for assessments and that we would sunset would be the bespoke technical implementation.

    • Big question: how do we drive exchange of assessment results and how do we coordinate better in the meantime?

Action: Take this up at the next SIG meeting; Sean to lead with some "what we have learned"

ODS API Deployment options

  • See proposal here- https://edfi.atlassian.net/wiki/display/EFTD/Multi-Tenancy%2C+Deployment+Modes%2C+Routing

  • Questions

    • Do SEAs need the backwards compatibility options? We know of at least 2 who do.

    • Connection strings – how to store a password in the DB? As secure as the DB server, but general commentary that there should be a more secure option here, maybe default to not allowing this,

    • Combine databases – admin and security? Been raised as a topic, not now as is a big change.

    • Change queries – always concerned about efficiency – main issue is that there are many of these endpoints to poll? Is there a way to show what APIs have changed data, to eliminate polling of many APIs?

    • Porting back to 6.1? It would be a big change, not on the roadmap. Looking at decoupling data standard support is the better path forward.