WISEdata Data Collection - Systems/Software
71 results found
-
Individual WISEdata Student Validation
It would sure be awesome if we could run WISEdata validations per individual student. As we approach snapshot dates, it's difficult to know, in a timely manner, if a change I make to a student in our SIS actually has an effect on the WISEdata or not. Waiting for a whole District validation seems unnecessary.
15 votesLet us know if there is still a desire for this feature. One of the issues is we still have to pull across all the data submitted from the SIS prior to validation. This could include other LEAs and therefore the queue line for validations exist. We did cut down on the number of validation jobs in a cycle by only triggering a single year of validations when you Queue Validation from the Validation Message page (it used to do all active years).
-
ACCESS Scores in WISEdata
Please alert districts via email on the date ACCESS scores have been loaded to student records in WISEdata so that districts can coordinate their data in the SIS side. Timely coordination helps avoid errors in validation.
Future published upload date on a DPI calendar would be helpful.
2 votes -
Name of students awaiting validation
List the student name(s) that are pending data validation changes.
9 votes -
Data check/error message for Choice students that are not marked as such in the SIS/Ed-Fi
We cleaned up our data for the March 11th snapshot and to make sure we were ready for ACT to pull our data for the Choice testing...however, we just found out that the Choice students were not getting sent to the state as Choice students (missed one checkbox in our SIS), so we are now scrambling to get this rectified for testing. Would be nice to compare whom the state has listed as Choice and what is in Ed-Fi and then give us an error report, if applicable.
4 votes -
Error requrest
Is there a way that an error can be posted if a student is being reported in Special Programs in our SIS but not counting for Oct 1st in the wisedata portal? For instance we had a student that has a special program but when we check the child count export from the wiseportal the student is not reporting and states SWOD. We think this has something to do with our dates, but yet we have no error and would not have know about this student unless we double checked SIS export to Wiseprotal export.
10 votesLet me know if you think a new L2 would still be useful. This could be based on primary enrollment spanning Oct 1 and the presence of an SSEPA SPED record spanning that same period and Child Count for Oct 1 = false. It could be false for a variety of reasons but those are clear within the Student Detail.
-
multiple languages for native and primary language field
Is it possible to submit more than one language for native or primary language? Many of our students are simultaneous learners or our refugees come in with multiple languages.
4 votes -
WISEdata Portal - Security by School
Create security for WISEdata similar to all other DPI applications, where rights can be assigned to a user for a specific school, not only district wide.
21 votes -
Ideas from Madison
From Madison:
- DPI program ignores enrollment start dates and end dates that are in the future. Just don't add them to the wise data system
- Ethnicity changes between districts all the time. Have that be a warning not an error.
Need to be able to delete enrollments that are an error or something. Once they are deleted from IC, some are not delete in the DPI site. I have a lot
Getting this error:
Credential type is not expected when the exit type does not equal HSC, High School Completion. For Private Schools, the studentAcademicRecord should be submitted only for…
12 votes -
Drill into Data Metrics for student names (similar to WISEdash)
It would be helpful to be able to drill into the actual graph data, similar to the WISEdash portal, to see the students pulling for specific areas - rather than having to export the file and sort/filter data every time we need to verify our numbers.
19 votes -
Verbose Validation change report
Having the ability to see:
- Errors that occurred on day 1.
- Running the validation on day 2 resulted resulted in: a. X errors from day 1 being resolved (detail) b. Y errors from day 2 still outstanding (detail) c. Z errors new (detail).
Sent to DPI by Jamie Price
8 votes -
Indicate field causing error
It would be great to have the name of the specific field that is causing the error in addition to the error description. So, if we go into WISE, click on the error, click on details, if the field was starred or a different color, or SOME way of indicating what the issue is. The general error descriptions are too broad to be of help in some situations. Thanks!
43 votesThis is a great concept. Not sure how we would execute, but I see the need for it. We’ll think about some options from a tech standpoint. Thanks.
- Don't see your idea?