Skip to content

WISEid

Please share your ideas and suggestions to DPI on how the WISEid system should work.
Caution: This is a public forum. Do not include any student identifiable information. Inappropriate content will be removed.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

46 results found

  1. Need help - Updating Social Security Number (SSN)

    My staff person says their ssn is incorrect. It was *and it should be *. Can you help me with this?

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  Jeffery Post responded

    The WISEid for staff eliminates the need for DPI to use Social Security Numbers for staff reporting. No correction or edit will be required.

  2. Download files of WISEids should provide Educator Entity/File Number for licensed persons

    To provide additional "Hard" matches for importing WISEid files into the school Districts HR or SIS systems, the Educator File Number should be provided on Persons that have them.

    This could help import data in a number of situations. a specific example is where a district has separate HR and SIS software packages that do not share a local id (Employee or Payroll Number) across them. When either system could generate a state report including Educators, the WISEid will need to be loaded into both systems. DPI is recommending that the HR system be the system of record for managing…

    26 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. Local Person ID should be mandatory

    In order to better leverage benefits provided by the localrowkey and to simplify DPI development efforts is it feasible to require a localrowkey be provided.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  Jeffery Post responded

    With the expansion of the WISEid Local PersonID is not required by the system.

  4. Updating a person should only be done by agencies with an active reporting association

    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 WSLS

    42 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    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.

  5. Updating a person should only be done by districts with a Local_Row_key Association

    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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    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.

  6. Once a WISEid generated it should never be invalid

    Districts should not need to delete or update a WISEid that is merged with other records. Both IDs should remain valid so that school staff are no longer concerned with getting lists of WISEids to change from DPI.

    This would not eliminate all manual updates as splitting an improperly matched WISEid would still require at least one district to update its records. However the localrowkey could be used to assist in those scenarios.

    11 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    We don’t require you to update the deactivated WISEid in the WISEid system. If you search by it or attempt to update it you will get the active WiSEid to make changes. However, WISEdata Collections system does require you to update the WISEid if the person is in the current year’s collections. In WISEid we recommend at least updating current students and staff to the latest update and have reports to find these. However, its not a requirement for the WISEid system to function.

1 3 Next →
  • Don't see your idea?

Feedback and Knowledge Base