Consider including superstar users as a report - to flush out regional issues
- Dominant language
- Python
- Stars
- 53
- Forks
- 16
- Avg merge
- 14d 5h
- Merged PRs (30d)
- 14
Description
The project as defined includes a single report (with different views) over measures of activity for organizations. This is good because we can make that report available in regional and global approaches to reporting.
However, because it can be viewed in both of these contexts it does not do a good job of flushing out details for reports which _cannot_ be viewed in a global context.
We believe a report which has sensitive data in it should be included to flush out these details.
## Super-star users
We believe there is an interest in finding very high activity users, or teachers assigned to very high activity groups in order to contact them as potential promoters within organizations.
_If this is not a report anyone wants, we should see if there are others that fit the bill._
This would require:
* Activity information very similar to the organization information, but at a per user level
* Exposing the name or contact details in able to allow Sales to use this information
## A random idea
Let's say the following are true:
* You **can't have** one / both of the users real name and email address in a global store out of region
* You **can have** a non-reversible opaque anonymised identifier
* Non-reversible and opaque in the sense that giving the information to someone tells them nothing
* I.e. not an MD5 of sensitive data which could conceivably be reversed
* It would still be associated to the real data in region
* We aggregate data out of region, but use the anonymised identifier only
* Regional LMS's have an end-point which is in region and can show you the users real details based on the anonymised identifier
The flow might look like this:
* Sales users use the global reports to find users of interest based on their metrics
* Sales users can click on a link in that report to be redirected to LMS
* LMS requires them to login with Google auth
* The end-point then displays the details required to contact the user
This would mean:
* We could facilitate contacting individuals without their details ever leaving the region
* This would not facilitate downloading lists of user details (perhaps this is good?)
## What we might learn
* We might find that such reports are unacceptable for us to produce, in any fashion, and therefore are not a concern
* We might find they are required and we must accommodate them
* By seeking to accommodate them, and abide by regional information restrictions, we might find additional constraints on the design
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.