Eliminate data gaps and human error by provisioning roster information directly from source systems.
Roster data is critical to most education technology solutions. But when school districts and state agencies have to manually extract and share their roster data via spreadsheets, the process is fraught with inefficiencies and human error. It’s not only less effective for your technology, it’s also time-consuming and frustrating for your customers.
According to LearnPlatform, school districts use more than 6,700 education technologies, many of which require roster data.
Almost 12,000 school districts across 32 states have adopted the Ed-Fi Data Standard.
Thousands of school districts across 32 U.S. states have adopted the Ed-Fi Data Standard.
"When decisions get made in silos around what reading intervention program we’re going to buy or what curriculum we’re going to use or what lottery system we might shift to, without speaking about interoperability and Ed-Fi, that’s how we end up with this fragmented vendor system."
All of Ed-Fi’s technologies, tools, and resources are free to access and use. Implementing the Ed-Fi rostering tool will require technology vendors to devote time to development and testing.
The Michigan Data Hub (MiDataHub) is one of the largest users of Ed-Fi’s rostering tool.
Yes, when planning Ed-Fi development, include the need to have multiple versions of Ed-Fi supported.
Ed-Fi has a robust governance process that manages the Ed-Fi Data Standard from input submitted from the Ed-Fi Community. Joining the Ed-Fi community is free and open to anyone in education.
Ed-Fi Certifications allow product developers to demonstrate a product’s fidelity to Ed-Fi standards and guidelines, and for purchasers or users to be confident that a product conforms to those same Ed-Fi standards and guidelines.
Ed-Fi Badges allow product developers to demonstrate support for Ed-Fi standards and technology, particularly in areas that are not yet covered by an Ed-Fi Certification.
Yes, at api.ed-fi.org.
These steps are an overview of what you’ll need to do in order to have a fully native Ed-Fi Roster integration within your software platform.
At this initial stage, you will need to determine the specific data elements that are necessary to properly provision the target platform. Once the specific data elements needed by the target platform have been determined, next you will go through the process of identifying the Ed-Fi source for each of those elements
In this step, you’ll take the outputs from the previous step and use them during the development to transform the data retrieved from the Ed-Fi API to the persistence layer in the target platform. Also, additional functionality will be developed to ensure better usability by the end user.
The Ed-Fi Alliance has observed that the most successful Ed-Fi based native platform integrations have come out of working with a client partner for the final stages of development. In this step, you’ll find a client partner and iterate the solution based on actual client usage feedback.
At this stage, development has been rounded out through actual customer usage and integration with a client partner has been promoted to the production environment. Once this is achieved the developed functionality of the target platform is eligible for an Ed-Fi API Consumer Badge.
Share this information with others in your organization.
The Ed-Fi team is standing by. Reach out to us at anytime.