21 votes3 comments · WISEdata Data Collection - Systems/Software » WISEdata Portal · Flag idea as inappropriate… · Admin →
We are looking to do this in a development cycle in March or April. When complete, we’ll be sure to mention on the Weekly Public Call and it will be in the published release notes.Nathan Papendorf commented
On our end, I'd say Validation Messages and Expected Transfers so only the district's responsible parties can acknowledge warnings & enter the expected transfer responses.Nathan Papendorf supported this idea ·
I think our Change Request process sort of does this. It doesn’t allow updates to the main person fields such as name and birthdate unless they go through the Change Request process which allows other agencies with Local Person IDs on the person to vote on allowing the changes. We don’t have voting on allowing Local Person IDs to be attached by districts. If you wanted that I don’t think most districts would want to do all the work necessary to review these on a regular basis.Nathan Papendorf commented
In a perfect world, the system would be able to facilitate the transfer of all of those data; but realizing that many schools don't house special education/RTI data within their SIS, an accept/reject process for ending primary enrollment with one district and establishing enrollment for that student in another district might be all we can realistically expect.
Ideally, at least some demographic information associated with that WISEid would transfer along with the student when the new district accepts the student. If things like Special Education/LEP flags, could transfer as well, that would be great; but I think the initial desire is to be able to "import" a student from another district and reduce the amount of data entry/chances for clerical errors.Nathan Papendorf shared this idea ·