Agenda

Materials

These note complement the slide deck above and make the most sense when read along with the deck.

Suggestion to send out a survey, asking for three painpoints / enhancements that would make your life better with Ed-Fi. Intended to capture your ideas and especially to invite input from those who may not feel as comfortable yet jumping into the fray during the regular meetings.
Audience seemed receptive. Stephen/Ann to send out soon.

Q: calendar reference example - is that an API requirement or certification requirement?
A: certification.
Q: are there cases where a student has multiple calendars?
A: not on this call.
Q: does the historical transcript requirement cover K-12 or just high school?
A 1: graduation plan specific, so only covers high school.
A 2: might depend on context - middle school may be appropriate (Ed-Fi staff will huddle to review).
Q: clarify the performance / optimization topic.
A: only re-sync failed entities, not all of the things that just worked (applies particularly to sync operations that are “batch-like”).
Q: will the API integration practices be modified to account for a push model?
A: too early; Project Tanager work group can help define initial best practices.
Concepts get “thumbs up” during the presentation:
- timeType
- detailed availability statements
- performance/optimization
- error handling
- API consumer best practice
- UI/UX best practice

Q: is the intent for a client application to use its own token?
A: yes - submit a token info request with “your own” token to find which operations are allowed.
Q: confusion about what endpoint is being used.
A: the token_info endpoint is not well known, but already exists.
Q: why is this a GET request?
A: following the OAuth2 specification. Can post an alternate token to inspect.

Table of Contents