Attendees

First Name	Last Name	Organization
Rohith	Chintamaneni	Arizona Department of Education
David	Clements	Ed-Fi Alliance
Patrick	Devanney	ClassLink
Rosh	Dhanawade	Indiana University INsite
Mindy	DuFault	Infinite Campus
LaQuinta	Extine	Leon County Schools
Stephen	Fuqua	Ed-Fi Alliance
Jean-Francois	Guertin	EdWire
David	Hefley	Nebraska Department of Education
Eric	Jansson	Ed-Fi Alliance
Vinaya	Mayya	Ed-Fi Alliance
Jim	McKay	Instructure
Chris	Moffatt	Ed-Fi Alliance
Heather	Potts	Ector County ISD
Doug	Quinton	PowerSchool
Daniel	Ralyea	South Carolina Department of Education
Andrew	Rice	Education Analytics
Sandi	Roesner	Ector County ISD
Audrey	Shay	Wisconsin Department of Public Instruction
Sayee	Srinivasan	Ed-Fi Alliance
Molly	Stewart	Inidiana University INsite
Patrick	Yoho	InnovateEDU Inc

Agenda

Onboarding and kickoff to our year
TAG members to voice over suggested priorities for the 2021-22 year
Continue on the topic of how to improve the efficiency with which Level 1 error messages are handled
Solicit interest in breakouts focused on Ed-Fi data standardization efforts

Onboarding and kickoff to our year (see slides)
TAG members voice over suggested priorities for the 2021-22 year (see slides)
Topics Proposed

Validation API
Multi Tenancy for Admin App
Specific data model improvements
Improving native Ed-Fi descriptors with proper descriptions
Improving Transcripts / Student Academic Records
Possible analytics domain and context
Greater data standardization (see next slide)
Getting operational context implemented - Operational Context UI
Open source community improvements-Talent directory -A mascot for Ed-Fi-
Improve usability of Ed-Fi API directly from a Web Application
OAuth/OpenID for Ed-Fi API-API Out tools and support
API Publisher
Improvements to certification-Greater Granularity on Certification
v3 SIS Certifications around grades. Districts are consistently disappointed to hear that native SIS integrations don't include current term grades-Notable absences-The issue of new suite releases / breaking changes
Continue on the topic of how to improve the efficiency with which Level 1 error messages are handed

TAG members voiced interest in improving the error messages
Question: Have you talked to Stack Overflow about a different pricing model for a nonprofit like Ed-Fi?
One suggestion was to focus on just the most painful areas, instead of tackling whole issue
One other proposed idea was to try and validate the data on pre-submission to the API; the mechanism for this was not discussed
Another idea: have API errors link to the community resource we create
Another idea: when considering a platform wide change, consider looking at opentelemetry.io standards to implement tracing/logging and metrics and replacing log4net by serilog