WISEdata Data Collection - Systems/Software
20 results found
-
out of sync label
Can we make the labels be Out of Sync? with question mark? Other wise it looks like the bold label is the status.
1 vote -
Multiple Graduation Plans
Currently WISEdata has only one Graduation Plan per district. Our Online Charter Grad Plan is different than that of our brick and mortar high school’s. For the sake of accuracy, could all the Grad Plans for each school within the district be published with a toggle between them? Thanks for considering the future update.
1 vote -
Export ability (for validation error messages)
For validation errors could an export feature be added? For example, WBSE had 535 errors of 6766 due to sections with 0 students. It's tedious to try to copy into excel to go through the data or in turn divide it up and send it to the different schools to work on correctly (with direction)
1 vote -
Export errors and messages from Validation message page
Would like to be able to export errors and warning to excel by individual warning or error from WISEDATA portal validation message page to pass along to team members for updates.
2 votes -
Export Button on Validation Messages Screen
When in Validation Messages and reviewing the warnings and errors, it would save time to be able to export the errors / warnings from the Valdiation Messages area.
Thank you -
1 vote -
Add code for student transfer to a non-wise school
When students transfer to a school not reporting, I don't believe they should be coded as a drop-out. I believe this needs to be changed.
1 votedeclined ·
AdminJaidaa Shafaei
(Vendor Relations Manager, Wisconsin Department of Public Instruction)
responded
An exit type already exists for when a student is transferred to a state or WI not covered by WISEdata.
-
Change Error 6484 (Exit Type expected to be 'Maximum Age' (MA) to a Warning
I suggest changing error 6484 (exit type expected to be maximum age (MA) to a warning because we can still service a FAPE student who turns 21 until the end of the school year, so a warning reminding us that a student turned 21 and the exit type(s) we should use when withdrawing them would be more helpful than having an error code all year until the student is withdrawn.
1 vote -
Wisedata ignore future enrollment records
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 votesThis 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.
-
Child Count Export Report
Child Count, when you export the child count could it please only pull the eligible students? It pulls all the students and then you have to sort. Seems like that is something programming could manage.
11 votesHey Everyone,
For now I’m going to decline this as I haven’t heard enough complaints from the field and this export is a source to compare the ‘Enrollments not qualifying for Count Date’. Changing the logic might cause complaints from other LEAs so I’m going to leave as is for now. Thanks for the input and keep it coming.
Thanks!
John Raub
Product Owner/Scrum Master – WISEdata Ed-Fi Integration
Applications Development and Management
Division of Libraries and Technology
Wisconsin Department of Public Instruction
E: John.Raub@dpi.wi.gov -
Child Count Date
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 -
Keep Local Withdrawal Codes
I suggest making the 6478 message a warning instead of an error, unless related to a DOS code.
11 votesnot doing for now
-
OPAL
Enhance OPAL so that we can communicate back and forth via the email with the other district. Currently the only option is accept or reject with no reply explanation available.
16 votes -
Lock data for previous year after last snapshot is taken
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 votesAs 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 should be a Warning.
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 votesError Code 6597 is an error as schools must take action to resolve this message. that data cannot remain as is
-
Change attendance collection to more accurately reflect absenteeism
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 voteThe 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.
-
Discipline Behavior Detailed Descriptions
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 voteI 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.
-
Message Code
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 votesRule 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.
-
ISES Portal Access until reports are elsewhere
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 voteThanks 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.
-
Change Error:6375 to a warning.
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 votesAssuming 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.
-
ability to delete Enrollment History record
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 records
1 voteThe 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?