Materials

Administrative app roadmap

Participants

Administrative app roadmap

Question: Should we keep Admin App for 7.0 and beyond?
- Answer was generally "yes"
- Needed for the non-MSP/pure open-source route, other collaborative growth
- Can also be used for external developers as a resource
Priorities for Admin App and related administrative tooling
- Need to expand Admin API to eliminate any MSP or integrator SQL
- Admin consoles from Ed-Fi should fully "dog food" Admin API
- Consider a YAML or similar config system for setting it up
- Instructure has an open source out of the box accessible react library https://instructure.design

Question: should we sunset API Publisher with something more modern?
- Answer was ambiguous - not fully addressed, but generally strong interest in looking at 3rd party open source tools in this area. However, this function is needed - don't change path until there is a clear and usable community option.
- Enable Data Union's tech may be more modern - EA offered that they continue to use both EDU and API Publisher
Question: How does AdminApp work with Meadowlark if Meadowlark is productized?

Alliance strategy and organization

Comments

Big urban LEAs are routes to lots of students but not to vendor market change
LMS market is consolidated while edu data more broadly is not; however, in lower grades the LMS market is not consolidated, but mostly fragmented in many competing apps
Q: can the Alliance drive collaboration of standards bodies. A: the Alliance has tried that several times and is continuing to try that. The issues that interfere are differing missions and organizational structures. The best way to drive this is for organizations to demand this. and create contexts/projects that push this forward.
Student data portability remains of interest
Issue with low talent in the Ed-Fi ecosystem - organizations draining each other's talent
Shared interest in driving LEA collaborative implementations as a strategy to growth