Right now PII is off by default, however we have 2 dashboards (Individual Learner and At-Risk) that rely heavily on that data and look broken without it. The Username, Name, and Email fields are all empty and it is not possible to filter to only one user, which is the whole purpose of the Individual Learner dashboard. Clicking on a user's username/name/email selects all users (since they all have the same username/name/email).
We have 2 choices that I can see to address this:
1- Turn those dashboards off when PII is off (but allow overrides)
2- Replace the PII with some kind of placeholders
Complications for 2:
- In order to make the cross filters work they would need to be unique somehow per user, but not in a way that exposes PII
- Any strings like "unknown" or "hidden" that we might need to use would need to be translatable, which can be a challenge
A possible way to do this is take some part of the user's per-course UUID and use that when the PII isn't present, but that does get hard to read and unless we hash it somehow will potentially expose enough of that key to be a privacy concern.
We should try to come up with a solution for this in the short term as it's a pretty painful issue.
Right now PII is off by default, however we have 2 dashboards (Individual Learner and At-Risk) that rely heavily on that data and look broken without it. The Username, Name, and Email fields are all empty and it is not possible to filter to only one user, which is the whole purpose of the Individual Learner dashboard. Clicking on a user's username/name/email selects all users (since they all have the same username/name/email).
We have 2 choices that I can see to address this:
1- Turn those dashboards off when PII is off (but allow overrides)
2- Replace the PII with some kind of placeholders
Complications for 2:
A possible way to do this is take some part of the user's per-course UUID and use that when the PII isn't present, but that does get hard to read and unless we hash it somehow will potentially expose enough of that key to be a privacy concern.
We should try to come up with a solution for this in the short term as it's a pretty painful issue.