Common Questions

What is the Difference Between Data Warehouses, Student Information Systems, MiSchoolData and the Michigan Data Hub (MiDataHub)?

Everything really begins with the Student Information System (SIS), which houses the most up-to-date (transactional) data on student enrollment, demographics, attendance, courses, programs, services and grades.  

A data warehouse typically receives data from a SIS as well as other sources. Data warehouses typically aggregate data over years for analysis and may house an assessment system for teachers to deliver assessments to students. Data warehouses may not contain the most up-to-date information for current students, although they may have the most recent assessment data for assessments delivered through the product.

MiSchoolData is a very specific type of data warehouse and analysis tool. It feeds off of many state-level data sources, combining state reporting and state assessment data. MiSchoolData has a public side where de-identified, aggregate data is available as well as a private side that has some detailed student level data that is only available to those with authorized logins. Since MiSchoolData works from state data sources, it is only as up-to-date as the last data received.

MiDataHub is a product of the TRIG Data Integration Activity, and serves two purposes.  

  • It serves as a conduit for the exchange of data between data systems (SIS, Special Education, Assessment, Alert, Data Warehouse, Learning Management System, Library, Food Service, Transportation, etc.) based on a standard data format provided by the Ed-Fi Alliance. As such, it works to make sure that the data in all systems is more complete, accurate and up-to-date.

  • It has an operational data store (ODS) database that houses current, up-to-date data merged from multiple systems in a common format. This allows for a number of solutions to be built upon the ODS including reports, a single sign-on, and ultimately state reporting.

Because it houses data in an ODS, MiDataHub can seem to have similar traits to Student Information Systems, Data Warehouses and MiSchoolData.  However, there are differences as well.

  • Similar to a SIS, MiDataHub houses student data and can be reasonably up-to-date and transactional depending upon how data is fed to the ODS. MiDataHub only maintains data for fields that it needs to exchange with other systems or use for hub benefits such as reports, single sign-on, and state reporting.

  • Similar to a Data Warehouse, MiDataHub provides reports in real time based on the most recent data published from a student information system, assessment system, or any other integrated system that provides data. The intent of these reports is to provide actionable information to end users. Reports from the data hub tend to have more real-time time, current-year data rather than aggregated longitudinal data that would be provided by a data warehouse. MiDataHub does not allow users to create and administer assessments. MiDataHub is intended to work with other data warehouses not replace them.

  • Unlike other systems, solutions built on MiDataHub can be easily shared within the state and even between states that use the Ed-Fi Solution. Otherwise, solutions can only be shared by those using the same system (PowerSchool or Skyward, for instance) and only when they use the products the same way with similar data standards.

  • Unlike district-level SIS and Data Warehouse systems, MiDataHub can serve as the basis for a statewide single sign-on that most districts have federated, and all MiDataHub integrated systems can leverage if desired.

At the district level, what information is available on data integration so I can plan for my systems to be compliant/ready?

MiDataHub is currently integrated with five Student Information Systems that have adopted the Ed-Fi API, all are listed below:

Edupoint Synergy
Infinite Campus

If your district uses on one of the systems listed above, then you are well positioned for utilizing the current functionality available in the MiDataHub.

Our team is constantly keeping a pulse on the systems districts use for Assessment, Data Warehouse, Special Education, Alert/Notification, Food Service, Library and Transportation. We continually work to gather the information needed to make sure that integrations are ready for the systems districts throughout use.

If you have any questions on your districts status with MiDataHub please let us know by submitting a help desk ticket to MiServiceDesk.

The Data Hosting Agreement seems to contain a lot of “legal-eze” and hold the district responsible for everything. Should we sign that?

The intent of the Data Hosting Agreement (DHA) is to set the criteria within which each data hub will handle data on behalf of districts. It is primarily geared toward giving the local district the control of what data is shared.

The agreement serves to protect the district and details the restriction and prohibition on what a MiDataHub hosting agency or anyone acting on behalf of the agency can do. Essentially we (data hub hosts and persons working on behalf of data hub) are not allowed to give any information from a district to anyone else without permission of that district. We have to carefully manage, protect and encrypt your data. We have to make sure the data is where nobody else can get to it. If you decide that you no longer want to use the data hub, we have a responsibility to destroy and copies of your data and provide you with a certificate stating as much.  

Unfortunately we agree it is a lot of legalese, but that is for your protection as districts, not for you to be held responsible for everything. We hope that clarification is sufficient, but there is the ability to download a PDF of the unsigned agreement to have your own legal counsel review should you choose. The agreement does not need to be e-signed in order to complete the survey information we are requesting. It is acceptable to hold off on signing (or rejecting) the agreement until your district is ready to begin using the data hub for integration of your district data.

Why are there so many users listed with authorization to my district in the cockpit application?

In order to expedite completion of the survey portion, we went the route of using MTRAx user information to initially assign rights to users. In many cases, this resulted in the correct tech contacts being assigned to districts and has been extremely valuable. Unfortunately, the user information from MTRAx seemed to have a broader set of users than we expected. Typically it included staff from your ISD and possibly other districts in the area. It is possible that those other users had a different access level in MTRAx, but we were unable to determine that in the data we received.

While we would prefer that those users had not been assigned as such, the amount of time that would have been needed to address the issue was significant and the impact is actually rather minor. First, as district tech contacts you are able to remove anyone who you do not wish to have access by clicking the Delete button when you are logged in. That will only take a minute or two to complete. Second, those extra users don’t have access to any data for your district and will not until your district SIS is integrated with the data hub. As part of that process, we will verify that districts have the proper contacts and that they understand how to manage contacts going forward. Finally, there may be some ISD contacts that you want to keep if your ISD provides SIS support for your district. That discussion is best held with your ISD, and any user removed can always be added back at a later time. We appreciate your assistance in cleaning up user access for your district.

Why are Superintendents included as users?

Superintendents are a key part of the process as they are the only ones able to e-sign the Data Hosting Agreement (DHA) for your district as mentioned above. The DHA acceptance enables your district for data integration. Because superintendents frequently prefer not to become involved in that level, there is capability for them to assign a proxy to handle e-signing the agreement. In either case, we would appreciate you reaching out to your superintendent on this process, assisting him/her with creation and use of their login, and advising on whether to e-sign the agreement or to hold off until later. Superintendents can request proxy by submitting a request to MiServiceDesk