feat: Add supports_researchers flag to external reports [PT-187221928] #1242
Conversation
The supports_researchers notes if the external report supports anonymized researcher views. This flag is returned in the offerings api result. This commit adds the flag to the mapped external reports data available to the React components but does not add logic to filter out the reports. The new researcher views React components will need to filter out reports in future commits.
There was a problem hiding this comment.
It looks good.
I have a question, though. If the anonymization is done server-side, it could be quite opaque for most reports, correct? They wouldn't necessarily know whether they are displaying real student names or anonymized ones. Then, does this flag exist because some additional customization might be necessary, e.g. feedback in the Dashboard?
|
@pjanik Yes - the current story I'm working on adds a researcher type to the Firebase JWT. This will be used in a future stories so the dashboards can use to change their UI based on the user type. We will also be updating the api controllers to anonymize data based on the portal user type in a future story. This commit is really just to allow us to disable each external report until it has the capability to use the next JWT and we update the controllers. |
dougmartin
deleted the
187221928-add-researcher-option-to-external-reports
branch
The supports_researchers notes if the external report supports anonymized researcher views.
This flag is returned in the offerings api result.
This commit adds the flag to the mapped external reports data available to the React components but does not add logic to filter out the reports.
The new researcher views React components will need to filter out reports in future commits.