Participants

• Marcos Alcozer
• Britto Augustine
• Rohith Chintamaneni
• Rosh Dhanawade
• Jean-Francois Guertin
• Eshwar Kedari
• Jim McKay
• Doug Quinton
• John Raub
• Josh Reimer
• Andrew Rice
• Jim Robertson
• John Watson
• Patrick Yoho
• Chris Moffatt
• Vinaya Mayya
• Stephen Fuqua
• Sayee Srinivasan

Agenda

1. Welcome and sign in (attendees fill out Google Attendance sheet) (5 min)

2. Update and discussion on tooling and data out roadmaps -  background for these topics identified by the TAG (30 min)

...

5. Signoff / reminder to sign attendance sheet (5 min)

...

Materials

Notes

Priority Topics

Notes combined from discussion in #2 & #3 on the agenda

The prioritization exercise resulted in the following order of topics

1. API data out performance (7 votes)
2. Improving support for SSO/Multi-Tenancy across all Ed-Fi tools (6 votes)
3. Improvements to SIS and Assessment certifications (4 votes)
4. Simplifying security configuration (3 votes)
5. Cross platform support - w/ Docker support (2 votes)
6. Migrations and bulk load support and tools (2 votes)
7. COVID-19 responsiveness (0 votes)

Topic: API data out performance

• Can improve simply by allowing 1000 records max per request instead of limiting to 100 records max. 

  Jira Legacy
  server Ed-Fi Issue Tracker serverId e04b01cb-fd08-30cd-a7d6-c8f664ef7691 key ODS-1856

• Composites work well, but are limited by requirement to recompile. Need to understand other approaches in the industry. GraphQL over existing ODS/API would not make denormalization easy, although GraphQL at least allows client to dictate shape of the response.
• Event-driven design for queuing new records would be useful for "warehouse notifications"
• Bulk JSON output might give highest performance. No one responded enthusiastically to the topic.
• E Rice interested in close involvement with the data out work.
• Roster data - flatter / faster view via API may help with vendor adoption, especially those not already using Clever, etc.

Topic: Improving support for SSO/Multi-Tenancy across all Ed-Fi tools

• On Admin App support for claim set editing, J Raub asks about support for claims to apply to a school year in a multi-year ODS, so that for example SIS Vendor 1 can access 2020 data but not 2021, and SIS Vendor 2 access 2021 (and forward). → Does not currently support this. Possible workaround: assuming firewall with whitelisted access, remove SIS Vendor 1 from the whitelist. Create reverse-proxy (e.g. NGiNX) on another server, whitelist the vendor to that other server. Only reverse-proxy the 2020 resources so that the vendor cannot access the 2021 (and beyond) URLS.
• There is community demand and interest  to integrate Admin App, Data Import, and third-party tools (e.g. Data Checker) via SSO to a single Ed-Fi login or to Google, AD, etc. Ideally plug-in existing ed org's SSO. J Guertin, R Dhanawade, E Rice, J Watson also express support and interest.
• Multi-tenancy: wild west. Ed-Fi needs help understanding the common needs in detail. Community request for guidance - Silvia Brunet-Jones at MSDF working on a white paper for configuration use cases.
• There was historical discussion around user management in the ODS. Alliance decided not to follow-through. Right call? Response: no objections to that.

Topic: Improvements to SIS and Assessment certifications

• Discussion centered around concerns about differences between certification and operational readiness. Ed orgs are likely to expect rapid implementation that may not be realistic. How can this be communicated more clearly? Playbooks are one answer. 

Previously Identified Priorities

TAG members are requested sign-up for those interested in following up (via Eric Jansson) on those priorities.