MSP SIG - Meeting 24 - 2024-11-05
Participants
Agenda
Next steps following our September meeting with demos of data mapping technologies – next steps to push collaboration on this forward
Feedback from Student Information Systems on our collective performance with SEA data specifications
Notes
Discussion of the problem we are trying to solve of sharing mappings and the ambiguity of a charter for the work
Drive agency buy-in?
Drive vendor buy-in and ownership?
Importance of governance tooling as a way of presenting agencies and others with mappings while not embedding them in the technical details
Proposal: get MSPs to agree on 1 assessment mapping as as a first step
Discussion and agreement on difficulty to create a simple UI for mapping data (part of the problem solved by the ESP tools)
Open question of if this work might forcing mappings on assessment vendors - is that OK?
One perspective is these vendors can contribute to those mappings
Another is that they should own the actual API implementation - that is the key step to having a voice in the mapping
Regardless: the concept is that we want them to be part of the community governance process that is being community-governed specifications
A way to work with 1EdTech on vendor/product IDs from their registry?
The agreed upon direction was generally to get the MSP community sharing mappings first, then think about growth elsewhere to other adjacent issues (like agency buy-in). On this, see actions below.
Actions
EA to share a YAML file for one assessment - NWEA Map Growth
EA to present a how mapping decisions were made for that spec, with discussion
(Ed-Fi) At the December MSP SIG, ask the questions:
do MSPs like the YAML technology as a means of sharing mappings?
do MSPs like the MAP Growth mapping provided?