The Michigan Data Hub has quite a bit of development work planned for over
the summer and several of the items will have a major impact going forward. The details of those high impact items are provided below. More information on these and other items in development will be available as the work progresses.
Upgrade from Ed-Fi v2.0 to v2.4 -
This work is expected to be completed by the end of June. While the update is minor in terms of vendor integrations and what you will see from the end-user perspective, many of the MiDataHub components need to be updated to work with the new version. That makes the summer time frame ideal to make this change.
MSDS Reporting -
While many items needed for state reporting have been in the data hub infrastructure for years, and MSDS testing is already underway, the process is one that needs to be updated to work with Ed-Fi v2.4. Additionally, changes to address new CEPI elements and rules need to be implemented. Finally, an additional component called the “MSDS Count Day Solution” is being developed to give districts the flexibility and control needed to ensure that data reported is what was in effect on count day, regardless of transactions received after that date. Work is underway to complete these items over the summer, so that MSDS reporting will be functional in the fall for final testing.
Assessment API -
As you may be aware, MiDataHub can currently receive Spring 2016 and Spring 2017 M-STEP results, but the ability to receive more current data has not yet been turned on at the State or Michigan level due to the need of making the process more efficient. Collaborative efforts with CEPI, DTMB and MDE are underway to complete that over the summer and to increase the number of assessments that can be transferred. The goal is to ensure that M-STEP, SAT, PSAT-8, WIDA, MiAccess, the Michigan Benchmark Assessment and AP test result information are all available. While the most recent M-STEP data is expected by the end of the summer, a timeline is still being established for the remaining assessments and will be shared as soon as it is available.
Alerts/Notification Framework -
One of the most important goals of MiDataHub is to provide improved data quality. In order to achieve that goal, we need to move from being reactive to being proactive. Currently, there are a number of options to run reports and queries to help to identify data issues. However, they all require someone to take the time to run them. The goal of this development item is to be able to configure alerts with rules that will look for data quality issues. If an issue is identified, then an identified contact will be notified of the issue via email. This will allow for a district to become aware of data issues as soon as they occur, allowing for the issue to be resolved as quickly as possible rather than when it is stumbled upon.
Single Sign-On (SSO) from SIS -
School employees can currently log into MiDatahub using either a MiDataHub provided login or with a login from their district if the district has configured that connection (called federation). There is a third option that is in development, which will allow a person to click a link in their SIS and connect to the MiDataHub SSO with that account. This type of SSO login is currently used for MDE’s MiLearn System, but will be expanded in functionality so that it can get to the MiDataHub Launchpad and any system that is recognized there. The major component of this will be the ability to register an email address that is tied to the SIS login, with a verification step that ensures that the person completing the work is the owner of that email account. Once that one-time step is completed, the SSO functionality will be enabled going forward. This is seen as a huge step in getting district users to the data hub dashboards, solutions like MiRead and upcoming solutions like MICIP.
