/
July 2026 - Ed-Fi Data Management Service Workgroup

July 2026 - Ed-Fi Data Management Service Workgroup

Participants

Not Captured

Agenda

  • Review the features and enhancements included in the Ed-Fi API v8.0 release

  • Align on priorities and planned features for Ed-Fi API v8.1

  • Confirm next steps and action items for the workgroup

Workgroup Goals

  • Gather input to prioritize features and refine the application design, ensuring alignment with early adopter needs.

  • Provide an opportunity for workgroup members to actively contribute by participating in hands-on testing, helping to identify bugs, usability issues, and areas for improvement. Your feedback will directly shape the final product.

  • Collaborate to ensure the development achieves a stable release.

Presentation

Summary

  • Ed-Fi API v8 is targeted for the 2027–28 school year, with full retirement of the legacy ODS/API and Admin API by 2029–30.

  • PostgreSQL 16 is fully supported. SQL Server 2025 is available for early testing but is not yet production-ready for vendor data collection.

  • Docker images and Docker Compose are the primary deployment methods; IIS installers and traditional deployment scripts are not currently provided.

Discussion Highlights

  • Participants requested the ability to optionally disable features such as Ownership-Based Authorization, Identity API, and Streaming. Not every implementation will require these capabilities, making feature toggles valuable for simpler deployments. Features such as Profiles and Change Queries were not identified as requiring configuration switches.

  • Request-response logging was identified as a useful troubleshooting feature but a relatively lower implementation priority. A configurable solution to enable full Request/response logging for specific API clients without restarting the service was suggested.

  • Change Query tracking table growth and cleanup were discussed. Cleanup policies must be coordinated with downstream consumers to prevent data loss while managing storage and performance. Some implementations purge tracking tables every 30 days, while others retain them indefinitely to support multiple consumers.

  • Custom validation scenarios were discussed for extending IResourceValidator, including:

    • Validating student resources against external identity systems.

    • Making optional collections (for example, Race and Language) required for specific implementations.

    • Preventing Special Education and Title I program associations from being posted as generic program associations.

    • No additional custom validation patterns were identified beyond extending IResourceValidator.

  • The development team will review native JSON storage compatibility with Azure SQL Managed Instance.

Action Items

  • Prioritize completing full SQL Server support, including cascade updates, and provide an early beta for vendor testing.

  • Evaluate configuration options to enable or disable optional features.

  • Investigate runtime configuration for client-specific request/response logging.

  • Provide cloud deployment documentation and quick-start guidance aligned with the Ed-Fi API 8.0 release.