Survey tool: Monitor forum participation
Description
Per TC discussion on July 8
Gear icon under My Organization, add link for Generate CSV for Vetting coverage
Permission level should be Manager roles and above (I think that’s TCs, Managers, and Admin)
Include the following columns
Rows should be the main locales and child locales if the organization has coverage for them. (e.g. es_MX, es_419)
Locale | Abstained votes by my organization in expected coverage level
| Missing/Provisional & we haven’t voted.* | Total request + discussions initiated in this release | Error counts in this locale | Forum: Requests with status Open | Forum: Discussions with status Open | Forum: Requests and Discussions initiated by my organization | Forum: Needing action (Requests and Discussions my organization has not responded to) |
Spanish (es) |
|
|
|
| ||||
Es_MX |
|
|
|
| ||||
Es_419 |
|
|
|
| ||||
English | 0 | 0 | 0 | 0 | ||||
En_CA |
|
|
|
| ||||
En_GB |
|
|
|
| ||||
Thai |
|
|
|
| ||||
Korean |
|
|
|
| ||||
Swedish |
|
|
|
|
xpath
locale
Activity
Based on TC discussion, I made a PR for a table with only those cells that can be generated quickly, for now:
Screenshots:
Note that the example above uses a local db that isn’t up to date with the current db on production.
Also I shortened the headings, and changed the order of what is now the 3rd column, whose only difference from the 2nd column is that it’s for one org instead of all orgs. The last two columns are also only for one org.
I added the “Needing attention” column in
Testing on smoketest looks OK.
Since the “Needing attention” column takes a minute or so, there needs to be feedback on the client while loading, so I employed the “special” mechanism, adding a new file special/forum_participation.js. I did this reluctantly, since the existing “special” mechanism’s implementation depends on legacy js/dojo features incompatible with modern js modules. I’d rather minimize dependence on it until we modernize it.
It was decided to make a separate ticket for the non-Forum columns, which might go in a different table accessed by a different command. That separate ticket is:
Priority
