SWG 2022-05-05 Meeting

Participation

Support

Nancy Wilson, Ann Su - Ed-Fi Governance Support

Meeting recording Link

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

Agenda and Notes

• Refer to the Meeting PPT for important information
• API Case Sensitivity Issue

• String matching between database server and API source code may result in failures in API GET operations.  
• This could affect the sync between the SIS systems and the ODS. 
• Issue between SQL server and API code
• Hot fix has been made beginning with Ed-Fi ODS v5.3 and documentation is soon to be published - some states need to add a custom code
• See PPT for additional information
• https://edfi.atlassian.net/wiki/display/ETKB/Advisory%3A+API+Case+Sensitivity+Issue

• States Operational Timeline - when do you take release and how long?

• • New needs to be incorporated in the middle of a school year e.g. natural disasters
  • DE
    • Published specifications to PS end of May and will continue with others
    • Integration testing on 6/30
    • Production at end of July

• • WI 
    • Release specs to vendor usually in March
    • Integration in May-August
    • Switch from 5.1 to 5.3 in January (middle of school year)
    • If it doesn’t appear to be breaking will have May time frame with goal of standing up early in September
    • Deploy often through the year 
      • New optional elements
      • Vendor may or may not have the data
      • Does not act on any data that has not been part of their spec; does not move downstream right away - goes into data specifications the next year
    • Any new requirements are submitted a year in advance to ensure being able to get all out to vendors (whenever possible - on a rare occasion, such as Covid, may have exceptions)
    • From one version to new one (depending on number of model changes) could be a week or two but don’t do everything at once and restrict data on end points not wanted)

• • TX process is similar to DE and WI
  • AZ
    • Same approach as WI - will be able to provide additional information in the future
    • Publish the specifications in January or February timeline.  
    • So far we did not have a need to do midyear api changes.  But for the SY 2022-2023, we are going to have midyear api changes.  
    • This will affect the vendors but the legislative needs are to be implemented for the SY.  The midyear changes are on the CTED planned instructional minutes at the course level on a daily basis and Course Transcript attempted credits for the community college courses.  
  • MN
    • Current structure does not allow us to bring in new Ed-Fi releases easily
    • Want to upgrade in 22-23 and started work in June to get plans in place to update to 5.1.2 and have replaced CID framework 
    • Hope to build more nimble, flexible framework moving forward
    • Second and final release in May - question about changes for the middle - limited to pilot mode items only except for descriptor value changes
    • February specifications become a release
    • End of May ask vendors for their solution.  
    • Have vendors finish implementation in May with vendor integration testing in June/July
    • Once vendors become certified key in allows full access for the year

• Ed-Fi CEDS Pipeline

• • Ongoing dialogue about Ed-Fi/CEDS collaboration but has not always meant technical, real-world application
  • Existing relationships and work with focus on making this collaboration be effective in a true pipeline
  • Will be looking more closely at CEDS model with new data models
  • Not investing further in Ed-Fi Generate Plug-in
  • Looking at CEDS IDS structure per work by several states
  • To land data in CEDS warehouse there are several considerations
    • See PPT for slides - “Intermediate Layer (ODS)”
      • Just adding school year for current states using this approach
    • Extensibility for working with different states - landing data is first but there needs to be a way for states to move the data values there in the extension over to CEDS (for example extensions to extensions)
    • Avoid demanding excessive custom ETL/ELT 
    • Should we have role in determining calculations - need more discussion within our work group for the optimal technical solution
    • Remember cost of change and need for change management
    • Think in terms of time frames - short window while CEDS builds out part of tech stack on their side. Ed-Fi needs to be prepared to deliver to CEDS API. 
    • In the long view, CEDS has an obligation to maintain API and interface to allow version changes on both sides (avoid rewriting pipeline from SIS up). Need to separate ownership and accountability. Negotiation needed on short term and long term responsibilities and commitments.
    • Through this group, what can we reach/accomplish - a sizable goal - do not want to map everything to CEDS. What use case should we take? Could take Ed Facts use and map out between Ed-Fi and CEDS.
    • Some discussions on EIMAC agenda relate directly to this work - some conversations can start at that meeting. Put ideas in a notebook and schedule the first official effort following EIMAC to review ideas that surfaced there - creating timeline and planned accomplishments.
    • Need to set some goals with where we want to be in the future.
    • Start with a small, doable use case.
• New Ed-Fi/CEDS SIG for aligning standards
  • • Dan Ralyea - SC
    • Nicholas Handville - Georgia
    • David Reeg - Minnesota
    • Scott K - DE
    • Andrew Rice

Action Items:

Next meeting: 6/2/2022 1:00-2:15pm CT

Last Update: 26 May 2022