Here is the answer to the above:
We have a dashboard that we have been using since we kicked off the work on review queues. The dashboard lives in a Google Colab notebook and requires access to a private dataset. I believe that it is totally fine to share the final charts with the community. At the same time it is not an easy task from a technical perspective to give you access to the dashboard at any time because of the dataset.
I believe we can recreate some of the charts on Stack Exchange Data Explorer. The two primary the tables to look at are:
ReviewTasks
represents posts in the review queues and their states.
ReviewTaskResults
represents a review task that is created for a user when they visit a particular review queue and clicks “Submit”, “Skip” or any other action buttons.
Here is a question that describes the SE DB schema in more detail.
It is worth mentioning that the Stack Exchange Data Explorer does not have data about users who performed the reviews. It means that, for example, one cannot query the number of reviewers over time. The easiest way to do so is ping me (Nicolas) or post a question on Meta Ask Ubuntu and tag it “status-review”. We will query the data and share the result with you all. -Nic
So it looks like I need to write some queries and on, say, a monthly or quarterly basis post the results. Please someone remind me to do this if nothing has appeared by the end of the year - I am too busy to do it just at the moment.
Here is the answer:
Thanks for the great question - I learned a lot in digging for the answers here. First, I’m sorry that this interface element is causing you disruption. I hate when we break workflows or cause problems on sites because things don’t work as expected.
I’m afraid that I don’t have an answer for you yet, though I promise to dig into it and see if this is something that we could put behind a site setting or something. However, with that said, I think it’s important to point out that the only things that can be sent from the Community user are the default responses - anything custom is required to be sent non-anonymously (and attributed to the user’s account).
It would be helpful if you could let me know (feel free to email me or just comment here) whether you are looking for a feature to remove the ability to use the default comments at all or only to remove the ability to leave them without attribution.
Again, fascinating question. I don’t doubt that this is an issue that’s come up before, but as one of the newer members of the team, it’s always fun to dig into things. (And thanks, Catija, for helping me learn!) -Philippe
Replies from CMs are expected by December 6thI will email Philippe as suggested once I get my thoughts together.