Versions Compared

Old Version 2

changes.mady.by.user Ann Su

Saved on

compared with

New Version 3

changes.mady.by.user Eric Jansson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Participants


Expand


First NameLast NameOrganization
MattHoffmanAeries Software
OscarOrtegaEdupoint
RonaldPeashaInfinite Campus
JenniferSauroInfinite Campus
JoshBergmanSkyward
AliDeGeoergeSkyward
BradEvensonSkyward
KathleenBrowningEd-Fi Alliance
SeanCaseyEd-Fi Alliance
NateGandomiEd-Fi Alliance
EricJanssonEd-Fi Alliance
JeffPutnamEd-Fi Alliance
MustafaYilmazEd-Fi Alliance

Support: Ann Su, Ed-Fi Allianc

Agenda

  1. Strategies for shared API resources We want to return to this topic as we have some research to share there (thank you Sayee!)
  2. Advising and shaping SEA processes. A topic suggested last time was advising states on their collection processes (thank you Brent!)
    • Related to this topic, we have been following up with some state education agencies and had some questions for the group on how we advise states on the timing and cadence of their collections, and possibly a better way to show this in the SEA implementation Playbook
    • We also made some changes to the Playbook coming out of our SIG meetings last year that we can highlight (SEA-vendor relationships and rethinking SEA processes – see meeting notes)

Notes

Shared API resources

Comments and key points

  • WI solution makes sense and is not causing issues
  • Recommendation should be to consult with vendors and think through which vendors provide/have which data and design the API so as to avoid elements where API resources are shared - Staff vs SEOA
  • Proposed Texas solution: the best solution is to do the above: design to avoid the issue. Participants also pointed out that in the example, 2 of the elements could be calculated (show these)
  • Respondents also said that reading data back out via the API for a second system might be better than the custom solutions for data to be moving from SIS to HR systems

Actions: Ed-Fi to design SEA guidance and surface to SIS systems

Vendor communications

  • The pilot year is a critical year since it is where much of the development is done - these timelines need to be longer
  • SEAs need to understand the goals of pilot, parallel and production years
    • Alliance invites SIS systems to review the SEA Implementation Playbook and submit suggestions for improvement
  • Timing also needs to consider major version updates for Ed-Fi tech/State tech
  • Validation rules should be released early and if possible during the pilot year where both LEAs and vendors can see them

Actions: Ed-Fi to draft updated vendor comms and publish these