SWG 2022-03-03 Meeting

Participation

Support

Ann Su - Ed-Fi Governance Support

Meeting recording Link

Refer to the PPT for additional details on the meeting minutes and discussions.

The meeting was held 2022-03-03 1:00Pm -2:15pm CT via WebEx

Agenda and Notes

What’s New in Ed-Fi API v5.3 (see PPT for details)

• •  Authorization based on a newly created Ed.Org subtype like 'PostSecondaryInstitution' is simplified.   
  • Districts now have the ability to consume extensions using the extension plugin approach without having to use the Source Code.  States will have the ability to consume other states' extension out of the box using the extension plugin model without having to download/build/deploy the metaed files. 
• MN’s vision for administering keys and secrets. 
  • Presented by David Reeg (see PPT for details)
  • MN's pain point - MN uses currently the Security Configuration Tool with some custom features.  Initially districts had the responsibility to manage and distribute the key and secret to their vendors.  But that led to confusion, complexity and difficulty in managing the tool for the  district users.  Hence, the State requested the districts to hand over the control to the State, so the state can manage and distribute the keys and secrets.  The initial goal for the next phase of Administration tool is to bulk distribute the keys and secrets to 553 districts.  The notification system needs to be in place as well to notify the districts of their keys and secrets.  
  • What will be the next phase of Admin App?
    • MN shared their vision for administering the vendors/applications/keys and secrets.  They shared the vision based on Ed-Fi's intention of implementing an admin api for issuing keys/secrets.  The administration tool will be an api client and will submit all the vendor/application/profile/ClaimSet information to the admin api.  
    • MN treats districts as vendors in their administration because the key/secret is issued to a district.  The district then distributes it to the actual vendors.  
    • MN creates one or more applications for each of those districts with a specific key and secret for those individual applications.  
    • MN has separate profile configurations - 
      • Base profile - Vendor submitted/certified last year on the base profile and hence we are starting off with the base profile
      • Full Profile - Vendor submitted last year on the full profile and certified on the full profile, hence we are starting off with the full profile
      • Subset data only 
      • Base + additional new requirements 
    • Moving from dual submission to Ed-Fi only
    • Limit level of elements districts can send 
    • Baseline for what can be submitted for the new year
    • Jason - shared high-level requirements 
    •  Thoughts from other SEAs
      • Doris - How are you certifying districts to allow Ed-Fi submission only?
        • Only for main student demographics and enrollment for  school finance
        • district can download Comparison report to clean up errors
        • Doris - So the DQ check is to confirm the data submitted thru both ways match. 
      • Align this work with Ed-Fi building API 
      • Debbie - How are you providing keys/secrets to schools today?
        • David Reeg - @Debbie, we are currently using a customized version of the Ed-Fi Security Configuration Tool in which an authorized user at the district can set up their vendor applications, and issue their key and secret.
• Technical Congress – Q&A
  • Sayee asked states to indicate their plans for attending the Tech Congress. 
    • Members to indicate their plan in column D of SWG roster 
  • Maureen reminded everyone to register and make hotel reservation as soon as possible

Action Items:

• Tech Congress attendance plan - Members to indicate plan in column D of SWG roster 

Next meeting: TBD

Last Update: 03 Mar 2022