If a student is already on the change request list, don't add another request. Match on WiseId4 votes
Last year we changed the system if there is a pending change request and a new upload creates the same Change Request no new change request is created.
Changing (Updating or editing) a name, DOB or gender should only be performed by users from agencies that have an unconflicted and current association established in a collection.
staff as an example: a contract record should exist in the staff collection that established an association between the person and the Agency before that person can be edited by that agency.
Students would need an enrollment record in the student collection.
This suggestion basically mimics the current behavior of WSLS44 votes
Towards the end of 16-17 we sent a request to SIS vendors to change their downloads of Person Upload data to provide an option or default to only including Students/Staff that are enrolled in the current school year. This should effectively complete the requested solution. If your vendor doesn’t allow limiting your Person Upload to just current year staff/students please submit a help desk ticket with your vendor to remind them to implement this requested change.
Changing (updating or editing) a persons Name, DOB, and Gender would only be editable by users from districts that have established a relationship with that person.19 votes
Any changes to the main name (legal name) and birthdate go through our Change Request approval process. Any district with a Local Person ID attached to the person can deny the change and comment on within 7 days of the original request. Additionally, we have created Notifications in the Notification module for these when they are created.
In order to better leverage benefits provided by the local_row_key and to simplify DPI development efforts is it feasible to require a local_row_key be provided.2 votes
With the expansion of the WISEid Local PersonID is not required by the system.
- Don't see your idea?