Development Updates
Phase 8 Development Items
New Development Items Approved - Phase 8 - The MiDataHub Advisory Committee has approved a new batch of development items that will increase the functionality of MiDataHub. Collectively, those items will make up the 8th development phase over the 5 years of the project. The items are summarized below:
- MiDataHub - One Statewide "HUB" - Currently the data for each hub is stored on servers in its own region. This work will consolidate the data to one data store that will be replicated for fault tolerance. Each hub will still serve as a portal to that data, but a district will be able to access via any hub in case one of the hub regions is offline for any reason.
- Implement Ed-Fi ODS/API from current version to v2.3 - MiDataHub relies on the Ed-Fi Alliance data model for its work. A new version, v2.3, is available. This will update the data hub and allow us to work with vendors on getting to the new version. This is a short-term step to version 3.0, which will be more involved.
- Renaissance Learning / STAR Assessments CSV integration - For MiRead and other uses, we’ve identified that the Renaissance Learning assessments would be valuable. Since there is not yet an Ed-Fi API to load that data, we are taking the short term step of loading that data as we have for other assessments like DIBELS and AimsWebPlus.
- SWIS CSV integration - An integration for SWIS is one of the most commonly requested connections. Since the SWIS team is not yet ready to send back discipline referral data via API, we will be working to read in their CSV format. This will be immediately beneficial for the dashboards and Early Warning System.
- OneRoster API Assessment 'write' capability - Our initial read-only implementation of OneRoster is taking off rapidly. We have now had a few assessment vendors ask about the ability to write data back via OneRoster API, so this item will address that need.
- UserName/LoginId management - ability to schedule creation of student.loginId field (assumes uniqueness only within district) - One of the items most requested by system vendors is to get a student login from the data hubs. This will allow for each integrated product to have its own login id, managed by district users setting up rules for login id creation. Utilities such as AD integrations will benefit from this.
- Display API and Inbound Integration statistics - We currently have no convenient way for districts to monitor how often their data is used via API. This will add the capability to get statistics to see how much their data is being read from or written to by a connected system.
- Skeleton for integration statistics and dashboard (assumes DataHub staff carrying out dashboard development) - Currently we maintain a spreadsheet of the status of all districts. This will create the basis to replicate that work in a PowerBI dashboard, allowing for getting a variety of statistics in convenient interface. One the skeleton is created by our developers, it is expected that MiDataHub staff will be able to tailor the dashboard to our needs.
- At-A-Glance Report enhancements - The At-A-Glance report is in need of more information for things such as discipline, grades, and to differentiate between daily and period attendance. It also is in need of an “as of” date to allow the report to be beneficial during periods when students are not enrolled. During the summer, the report is often blank or showing very few students due to exit dates.
- Dashboard testing - We have often encountered inconsistencies in the way the Ed-Fi dashboards are showing the data that is housed in the district database. This would provide for testing for 5 districts, one each from our 5 main integrated SISs. That will allow us to work out any SIS specific issues and to ensure the dashboards are providing the best data possible.
