Participants
- Marcos Alcozer
- Britto Augustine
- Rohith Chintamaneni
- Rosh Dhanawade
- Stephen Fuqua
- Jean-Francois Guertin
- Eshwar Kedari
- Vinaya Mayya
- Jim McKay
- Chris Moffatt
- Doug Quinton
- John Raub
- Josh Reimer
- Andrew Rice
- Jim Robertson
- Sayee Srinivasan
- John Watson
- Patrick Yoho
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)
- Simplifying security configuration
- Migrations and bulk load support and tools
- API data out performance
- 10 minutes - roadmaps
- 20 minutes - Q&A from TAG
3. TAG priorities activity and discussion (30 min)
- 5 minutes - TAG member sorting of items
- 25 minutes - discussion - Open discussion of top priorities for TAG for the list of 10 possible topics
4. Actions on topics already identified as top priorities (via Slack discussion) (5 min)
- Convene a small TAG group to discuss how to action Open source community development – any volunteers?
- Convene a small group to look at the problem of Community evolution and when to “break” things – any volunteers?
- Convene a small group to look at the problem of Operational context – any volunteers?
5. Signoff / reminder to sign attendance sheet (5 min)
Notes
Tooling and Data Out
- Claim Sets
- 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.
- Data Out
- Can improve simply by allowing 1000 records max per request instead of limiting to 100 records max. ODS-1856 - Getting issue details... STATUS
- 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.
TAG Priority Activity and Discussion
- SSO: would like 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.
- Certification: concern about difference 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.
Existing priorities - requested sign-up for those interested in following up (via Eric Jansson) on those priorities.
Those who were unable to attend can still register a vote for the priorties and indicate interest in side-conversations on three current priorities. Please do so using this Google Sheet.
- "When to break things" - add a bullet point - version support matrix / timelines.