Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Participants

  • Audrey S
  • Ben M
  • Britto A
  • Chris M
  • Daniel Hornsby (NEFEC)
  • Greg Petras
  • Jen D
  • Jill A
  • John R
  • Mike D
  • Sherod K
  • Tarun V
  • Tim C
  • Veronica A
  • Eric Jansson
  • Chris Moffatt
  • Shannon Kerlick, Ed-Fi Alliance

Agenda

1.Revisit the January question of student identification / rostering

Rostering discussion returned to the January topic. Most respondents noted that there are likely minimal levels of technical integration already in place for the student ID issue to be worth resolving. In other words, if a products rostering is current just based on student entering their ID, should we have any expectation that such a product would directly communicate with an API to pass back results. The TAG opinion seemed to  be "probably not."

2. Record-level security (AZ)

Arizona DOE presented the concept of record level security: recording a submitting EdOrg id for all records. This design can help solve issues related to authorization and ownership, but was being proposed as an optional addition to the overall ODS API tech solution. This design was seen as similar to designs under way or being considered in Indiana and Michigan, but with some difference in use cases. The Alliance took an action to convene a body to review the records.

3. Technology roadmap for 2019 – TAG feedback

The roadmap was reviewed, but there was little time for commentary.

4. Emerging questions on standardization of enumerations

Not covered - to be addressed in a future meeting.

Materials


  • No labels