Agenda
Review the new guidance for states as they write their Ed-Fi aligned data specifications ß this was the outcome of the action from our last meeting – see Guidelines and Expectations for States Using Ed-Fi Standards
Awareness of proposed changes to Ed-Fi Certification – see Best Practices under Ed-Fi Certification
Ed-Fi research support: how SIS systems are doing multi-year data sends
Notes
Review new state guidance
Feedback: seems oriented in the right direction.
Can we add examples? Yes, Alliance is happy to do this, feedback is always welcome
What about descriptors?
Should provide advice to use state values. We confirmed with the SIS systems that this is a best practice, and confirmed that this results in increased efforts for SIS system.
Action: Add section on descriptors as a next step - just use state descriptors and link to
Other question: do SIS systems allow for configurability of descriptors, or is this in programming? Should this impact state behavior? Need to research and resolve this over time.
Proposed certification changes
Feedback: looks good as a direction
Timing? Will go through the TAG and GAT and looking to implement starting for next year.
How to handle multi-year to SEA APIs - how do SIS systems support this?
Generally SIS systems seem to set up a configuration for each year
Keeps them open for each past year
Results in a lot of training for staff to understand the rules and processes around correction of past years
Some discussion of course transcript came up - is a lot of data
Idea: asking states to add a year dimension to the extensions - would that help manage the code?
Follow-up: can you describe the basics of SIS rollover processes? Processes seem similar: give LEAs the option to copy forward configuration and similar base date from the prior year in a structured process