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 Current »


Participants

  • Ben Meyers
  • Britto Augusting
  • Jill Aurnad
  • John Raub
  • Jon Hickham
  • Michael Discenza
  • Scott Gutowski
  • Shrerod Keen
  • John Raub
  • Tarun Verma
  • NWEA rep for Greg Petras  (sorry I failed to capture the name!)
  • Eric Jansson
  • Chris Moffatt
  • Sayee S

Agenda

  1. Ed-Fi Events API review

  2. Follow-ups from Technical Congress: unfinished business needing more attention
    1. Data Quality (Britto's session); what are next steps or how does this long-term vision continue moving forward
    2. Certification; what are we going to do to support domain specific vendors, SEAs not implementing all end points, Private school vendors with small footprint......but still uphold the integrity of certification
    3. Creation of V3 Ed-Fi/SEA/SIS working group
    4. /studentEducationOrganizationAssociation; consideration of additional properties for V3
    5. Plans for Finance and Assessment work teams

Notes

The Events API was briefly discussed butTAG discussion will occur next month.

Item 1: Data Quality actions from SIG and Technical Congress

The actions to take following the Technical Congress discussion of a Level 2 "validations API" was discussed, which could route errors back through a vendor system, rather than through a separate agency portal (see slides on Validation API below). The TAG members at the session reported widespread agreement on this as a good idea, including by vendors in attendance there. The plan is for the Alliance assisted by the TAG to move forward with design, and when we have such an overview to see if any agency is interested in leading an implementation. If not, it can be prioritized in the Alliance roadmap. 

We also noted that we need to re-open the question of Level 1 validations support.

Item 2: Certification. The pros/cons from the Technical Congress were discussed (see materials linked to 2018 Technical Congress). On the core risk of dis-aggregating the SIS certification, the possibility of restricting the dis-aggregated certifications (e.g. just a SPED certification) to vendors who can demonstrate that they are actively doing business in such a fashion was brought up. I.e. a SIS system can't request a SPED certification unless the vendor can demonstrate that it is being actively used in the real work as just a SPED system.

Materials

  • No labels