Versions Compared

Key

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

Participants

Agenda

  1. Review of SIG Origins and Goals
    1. GAT Meeting - 2019-4-11
  2. Open Discussion on Integration Options
  3. Next Steps

...

Notes

Agenda discussion

On the agenda discussion, we added another use case to add to the SIS goals: Data Out from Classroom to Ed-Fi, which was represented as a current LEA pain point

Rostering use case
The need to select schools to integrate makes this problem non trivial: a roster should not just send everything, as that is over-sharing.

Following discussion, the SIG aligned on these options for rostering from Ed-Fi platform to Google Classroom

  1. develop a middle tier to write to Google APIs directly (Google API client; solution to school selection; scheduler, etc.)
  2. develop a middle tier to write OneRoster CSV files, which are then uploaded to Google Classrrom rostering pipeline (perhaps can leverage the existing OneRoster CSV solution in http://exchange.ed-fi.org) 
  3. ask Google to integrate via Ed-Fi APIs

Note that the conversation also broadly considered that this issue is not unique to Google Classroom, and could apply to other to other "LMS" systems. 

Analytics distribution use case

There was less discussion time, but a a few options were explored:

  • Use Announcements in teacher-only sections. In many Google Classroom implementations in LEAs, the LEA will elect to create sections of teachers; these perform peer notification and content exchange roles (e.g. used to distribute announcements or materials to teacher cohorts at a building level). In such implementations, all teachers can also be co-teachers; this gives everyone access to assets.
  • Another option is personalized assignments within "normal" classroom"

Actions

  1. John Raub (WI) to survey district on if they use Google Gradebook
  2. Eric to outline options discussed in meeting and reconvene group