Rethinking person data (Person Manager)
New capability for Experience
Centralize person information and THE source for person information - person matching and merging
General theme of bad data
lack of data mgmt system/protocols
lack of understanding of who’s managing data
Effects of bad data
makes your job harder - mistrust of the data
takes away your time
sets you up for uncomfortable experiences w/students or faculty
possible data breach
Committee
Legal, Finance, HR, event mgr, alumni/adv, fin aid, reg, adm
Protocol questions
what’s needed to create a person
limit personal info while collecting enough
sources, rethinking duplicate rules
share only if there’s a business need - are they authorized to have it?
Managing person changes
who reviews changes?
students who are employees
When to purge data
establish data retention policy
what can be purged and after how long
which attributes can be purged
archive vs. delete
right to erasure/to be forgotten
Data quality audit to:
validate business case
reduce data faults
compliance w/data regs
discover new data
Auditing
learn about processes
where is data stored
identify valuable data
evaluate accuracy
find problems with existing processes and improve to improve data quality
How to enforce consistency
communicate
explain value
set deadline
extend grace
explain why
review data
establish data policy
enforce data policies
continuous review of policy
ID numbers should never be released via ticket, phone, or email. Students can access their ID numbers via Gibson. Students needing ID numbers for transcript orders can enter their SSN or 9 0's in the ID number field.