Students' enrollment records with an enrollment date in the future should be ignored, and not generate a warning or an error, until the enrollment date matches today's date, or is in the past. When I asked about this on a Tuesday webinar, someone from the DPI said I should contact our SIS vendor. SIS vendor said this couldn't be changed because that logic is part of core Ed-fi functionality, and instead DPI should create logic to ignore future enrollments.10 votes
This is simply a WARNING and can be acknowledged if the enrollment was simply entered in advance. WARNINGs are present to communicate something doesn’t look 100% correct, but it could be depending on process, etc. Therefore, closing this one.
If the child count date was on the 2nd or 3rd Friday of October, it would be easier to count those students who moved on Friday, 9/30 and didn't enroll until Monday, 10/3, as most families move at the end of the month, especially if they are renting.12 votes
Lock data for the previous year after the last snapshot is taken.
We did this with ISES and it worked well.
I see no reason to go back into the previous year to fix new validation errors which popped up because another school district decided to fiddle with their database.6 votes
As of now policy is that data can flow for 3 years to accommodate dropout scenarios, etc. We have heard some in the pro-lock data camp and other that appreciate it stays open. For now it will remain open.
Error Code 6597 is causing a lot of confusion as to why it is appearing. It would be best as a Warning, since it's purpose is to warn the districts that a student will be turning six and a new sSEPA record is due on their birthday with the new Ed Environment.3 votes
Error Code 6597 is an error as schools must take action to resolve this message. that data cannot remain as is
I think that DPI needs to be more vigilant in the attendance that they are collecting. If we have students out on a field trip, yes, they are not in the building but they are in an academic status for a particular class. If we enter exempt, field trip, that should not be counted against a district. I believe that only actual excused and unexcused absences should be reported where the child is not in the building, attending a class. Please consider this as I was told that most districts are facing the same issue our district is a large increase in absenteeism for 16-17.
I think that DPI needs to be more vigilant in the attendance that they are collecting. If we have students out on a field trip, yes, they are not in the building but they are in an academic status for a particular class. If we enter exempt, field trip, that should not be counted against a district. I believe that only actual excused and unexcused absences should be reported where the child is not in the building, attending a class. Please consider this as I was told that most districts are facing the same issue our district is a large…1 vote
The description you provide is exactly how we expect attendance to be reported. Students on field trips should not have the Actual days of attendance value reduced for the time they are participating in a school sanctioned out of classroom activity.
It appears that Discipline Behavior Detailed Descriptions are published for all discipline records in WISEdata. However the DPI description of this field says that it is for firearm-related incidents (and is to be used with tracking behavior types & statistics on weapons in schools). If this is true then, can there be an algorithm or some type of enhancement implemented to keep only those behavior detailed descriptions which are associated to behavior incidents related to handgun, shotgun or rifle, or other firearm, rather than all behaviors being submitted to WISEdata.1 vote
I would contact your vendor to make a code change to only send to the state for the required use case. That is the best solution versus us having a secondary process to delete those when they arrive. I can also contact the vendor if that helps. Thanks, John.
Error Message Code 6478. Please reconsider this being considered an error that a district needs to correct. The corrections make our SIS information inaccurate.6 votes
Rule is turned off and wasn’t re-created for 19/20 and beyond. Ultimately was replaced by 6718. Closing this one. Analysis on dropout L2s currently being looked at and will pass this along.
Make the ISES portal available for us until we can get same reports elsewhere. Discipline data, by school, is not currently available in any system. Having the ability to view all historical data in ISES would be a huge help to us for CRDC reporting and other data requests as they come in.1 vote
Thanks for this idea. The ISES Application has been retired and removed from DPI servers. It just was not possible to keep it running any longer. WISEdash for districts provides much of the data that was available within the ISES reports.
Sometimes we have Sp. Ed. students that are the grade level of our Intermediate School but are actually enrolled in and attending our Jr. High School due to meeting the needs of their disability. It would be much easier if we could just acknowledge this message and report the student at the actual building they are attending. The way it is set up now we either have to give the teacher rights to a building they do not teach in or we have to re-create the student's schedule, attendance, and grades in the other building.2 votes
Assuming the Intermediate and Jr. High have no grade overlap: Schools need to think of the student as enrolled in the age/grade appropriate school and attending a program in the other (higher grade level) school. Only the age/grade appropriate should be sending an enrollment record (SSA) to WISEdata.
Please Discuss with your SIS vendor and/or peer agencies using the same SIS what best practices are for special enrollment cases and impact on State reporting to establish a practice for reporting the scenario you describe without creating enrollments records that would trigger the 6375 message.
delete button on the Enrollment history page in WISEdata IF the student record is associated with your District. Have the ability to ONLY delete our your own records1 vote
The ed-fi API provides a mechanism to delete all record types through the API. SIS Vendors must provide this functionality. Many vendors are working to improve delete handling within their products
- Don't see your idea?