Community health initiative/Dashboards used by admins to track reports of harassment
This page documents a feature the Wikimedia Foundation's Anti-Harassment Tools team may build. Development of this feature has not been decided or prioritized.
🗣 We invite you to join the discussion!
One theory of why harassment reports do not get resolved quickly (and some reports are never resolved) is that there are limitations the the available methods to monitor all ongoing reports of harassment. If true, this is likely exacerbated by the fact that there isn't an established group of admins who are responsible for monitoring all cases.
The primary dashboard for all of Wikipedia. It collates ongoing discussions across all of Wikipedia — talk pages, user talk pages, noticeboards, and the Village Pump. It is built of templates which are updated automatically by bots. (Legobot)
The dashboard is very comprehensive, which is simultaneously a pro and a con: the dashboard doesn't just focus on content it brings an equal weight to user conduct as well. But the long list can be difficult to cipher through.
The dashboard topics are sorted by most recent activity. This means that ignored topics are pushed further down the list. But it does show all open conversations and a count.
Centralized discussion is a template that is transcluded on multiple high-profile pages on English Wikipedia (e.g. the Dashboard.) It is curated by admins (or privileged contributors?) with a few links from various places on Wikipedia — talk pages, project pages, Village Pump, etc.
Not really used for tracking reports of harassment.
Not really a dashboard — just the noticeboard. All sections that have no activity in 72 hours are archived by a bot so the table of contents itself could act as a dashboard of "current reports." It is not a dashboard of "reports that have not yet been resolved." This is by design — things posted to the noticeboard will not necessarily be responded to at all.
ArbCom reviews all requests and votes to accept or deny. ArbCom hears few cases concurrently and each case has a set timelines, meaning a dashboard is easy to build and use. The dashboard is built of templates that are hand-edited by ArbCom members.