Project Name | Description | Value Add | Vendor Req’d ? (Yes/No) | LEA Req’d? (Yes/No) | LEA Type (Public, Choice, All) |
|---|---|---|---|---|---|
Pupil Count Report for Membership - Changes to the Residency Information | In an effort to ease LEA administrative burden with reporting PI-1563, DPI will redevelop the SFS Team's WiSFiP application to allow data flow from the SIS to WISEdata and subsequently to WiSFiP.
NOTE: 23/24 is a parallel reporting year for public SIS vendors and interested LEAs. | Recent experience with the School Level Reporting and High Cost Special Education collections in WiSFiP have demonstrated that many districts continue to have a disconnect between finance, enrollment, and special ed/pupil services in terms of data reporting. Integrating those data elements for finance collections will raise the stakes for data quality, increasing collaboration within districts and further improving our data quality. | Yes | No | Public |
School-level First Day of School (FDS) and Last Day of School (LDS) | This project to collect first and last day of schools from the SIS vendors through the WISEdata Ed-Fi integration, specifically the /session endpoint. After the data is sent to WISEdata Portal, it will be used in other applications. | To improve data collection efficiency from LEAs by reducing or streamlining collection requirements. | Yes | Yes | All |
StudentSchoolAssociation (SSA) and studentEducationOrganizationAssociation (SEOA) Changes | This project is to limit the enrollmentTypes data property (under the SSA WI Ext.) into a single descriptor to only allow for one value. Moreover, with the changes related to the membership Pupil count data collection, vendors need to modify both the SEOA and the SSA endpoints. The Resident LEA ID will move from being collected as part of the SEOA endpoint to the SSA endpoint. The SSA endpoint will be modified to collect the Residency Status Information as part of the ResidencyPeriod. | To prevent vendor from sending invalid data to DPI, and to allow LEAs to report changes to the Resident District. | Yes | Yes | All |
This project is to move the digital equity data collection out of the generic student indicator model and collect the data as standard elements on the StudentEducationOrganizationAssociation: InternetAccessInResidence (boolean), BarrierToInternetAccessInResidenceDescriptor, InternetAccessTypeInResidenceDescriptor, InternetPerformanceInResidenceDescriptor, PrimaryLearningDeviceAwayFromSchoolDescriptor, PrimaryLearningDeviceProviderDescriptor, and PrimaryLearningDeviceAccessDescriptor. | As digital equity has become more defined, Ed-Fi and SEAs recognize that this data collection needs to be defined as standard elements on the StudentEducationOrganizationAssociation. This change will help prevent data discrepancies and ensure data is collected accurately from various SIS vendors. | Yes | No (optional) | All | |
The Ed-Fi Alliance is going to deprecate the StudentDisciplineIncidentAssociation (SDIA) endpoint. This project to shift to the new endpoint StudentDisciplineIncidentBehaviorAssociation (SDIBA). The SDIA reference on the /disciplineActions endpoint will need to be updated to include SDIBA. Moreover, the data type max for the 'actualDisciplineActionLength' will be increased to be 4 digits to the left (xxxx.x). | To stay up to date with the Ed-Fi Alliance changes. | Yes | Yes | Public | |
API v6.X (Ed-Fi Data Standard v4.x) Changes | In addition to the changes above, vendors will need to modify the URLs for the 2023-24 SY. DPI will generate a new SDK for vendors. The Ed-Fi Alliance made some enhancements to Change Queries Delete Tracking. For more information visit https://techdocs.ed-fi.org/display/ODSAPIS3V60/What%27s+New+in+v6.0. This change is not part of the vendor certification. | To stay current with the latest Ed-Fi API version and data standard. | Yes | Yes | All |
With the new API version (v6.x), the Finance Ed-Fi model will include minor breaking changes:
| To stay current with the latest Ed-Fi API version and data standard. | Yes (Finance vendors only) | No | Public | |
This project to stay current with the latest version of the SCED 10.0 course codes. | To provide up-to-date and accurate course codes so that SCED remains relevant and useful to LEAs. | Yes | Yes | Public | |
World Language SCED Course Codes for Indigenous Asian and North American Languages | This project to create new world language SCED 10 codes for reporting endangered and Indigenous Asian (Hmong) and North American (Ho-Chunk, Ojibwe, Oneida, Potawatomi, Menominee, and Mahican) Languages in Wisconsin to identify districts within which these languages are learned and by whom. | To build DPI’s capacity to assess and improve equity through:
| Yes | Yes | Public |
studentProgramAssociation (SPA) Metadata Changes - Coordinated Early Intervening Service | The Coordinated Early Intervening Service (CEIS) is collected under the Program Type of “Cocurricular Programs” even though it does not have anything to do with cocurricular programs – for one type of LEA it is academic or behavioral interventions; for the other type of LEA it is addressing the root cause of racial disproportionality in their schools. Co-curricular, on the other hand, refers to programs that have components occurring during classroom time as well as outside-of-class requirements such as music courses with required concerts that happen outside of the normal school day. This term is meant to distinguish those out-of-class requirements from extracurricular activities that are not typically tied to a specific course. Therefore, the 'description' and 'shortDescription' under the ProgramTypeDescriptor have been updated from 'Cocurricular Programs' to 'Coordinated Early Intervening Services'. Additionally, SIS vendor should not roll over the CEIS program association from the previous year. LEAs must verify the data for students served under CEIS every year. | To eliminate confusion as clarity of the description is essential to the assurance of data quality. Also, to avoid overcounting students served under CEIS. | Yes | Yes | Public |
Supporting different API Credentials (key/secret) in different school years | Vendors should have the ability to support different API credentials in different school years, or at least have documentation on how LEAs can switch API credentials to update prior year data. | To regression test vendors' Ed-Fi configuration and ensure that LEAs are able to send data from different school years as needed when they have different API credentials for each year. | Yes | Yes | All |
Student Address on /SEOA: PO Box should not be sent as a Home Address Type | Vendors should separate fields for the PO Box from the Street Number/Name field. LEAs/vendors may use a PO box as a mailing address, but it cannot be used as home address. | To help improve the student address data and to ensure address geocoding matching accuracy. | Yes | Yes | All |
The completedSchoolTerm data property was replaced with the termCompletionIndicator on /SSA in the 2020-21 SY. SIS vendors need to make sure the termCompletionIndicator is being reported to WISEdata Portal as part of the /student SchoolAssociation endpoint when applicable. | To regression test vendors' implementation and to ensure the Term Completion Indicator is reported accurately. | Yes | Yes | All | |
This integration was optional since the 2021-22 SY to help eliminate unnecessary manual LEA administrative tasks. Starting the 2023-24 SY, vendors are required to wire the /parents and /studentParentAssociations endpoints to WISEdata Portal to allow LEAs to report the data when needed. A new WISEdata validation message to require Parent info (Name, Address) for students who qualify for free and reduced priced meals. | Summer EBT is now a permanent program per the Consolidated Appropriations Act. The WI DHS would like to consistently receive the parent(s) or guardian information. | Yes | No | All | |
This integration allows vendors to display the WISEdata validation messages within their product, which in turn will help LEAs to easily identify what the error/warning is and where to fix it. The WISEdata Ed-Fi Validations API is an optional integration, does not require integration testing, and can be completed at anytime during the school year. DPI does require vendors to demonstrate their implementation. | To offer LEAs an improved validation experience that boosts their data quality. | No (optional) | No | All | |
This integration helps LEAs with the retrieval, the potential matches review, and the creation of WISEids for students through their SIS. Moreover, it will reduce the frequency of WISEid file uploads for LEAs. | To allow SIS vendors to build an integrated user interface that provides a more satisfying experience to LEAs. | Yes | No | All | |
This integration helps LEAs to retrieve their students' immunization records from the Wisconsin Immunization Registry (WIR) system and ingest them into the SIS. | To saves significant amounts of LEA’s staff time spent on entering student immunization records into the SIS, and to improve the accuracy of immunization data in the SIS. | No (optional) | No | All |
...