Show request prominence counts for users and bodies

[RichardTaylor]

Obvious corollary to

• Add request prominence counts in admin UI #7348

This would be part of proactively and automatically running services more transparently.

Consider avoiding clutter making the material accessible, but not too prominent, as we do with eg. detailed event history for requests.

We might want a linked help page on interpretation/explaining/commenting on any stats we publish, or we could add some text in-line.

We might want to hold off on this until we can do something better than just pull the first iteration from the admin system to the public side.

[garethrees]

Less sure about doing this on user pages as it may be amount to public shaming in some ways (if a user has lots of hidden requests).

[mdeuk]

Less sure about doing this on user pages as it may be amount to public shaming in some ways

+1, there is an obvious advantage, from a management information / ease of administration stance, to having this information available somewhere, but it strikes me that the most appropriate place would be in /admin.

We would need to take specific care, if automatically publishing data, to ensure that it wasn't derogatory - as that could very well be misused in such a way that it causes real harm (thinking, say, of users that have previously made requests that we've hidden data from).

Without very careful presentation, it could also result in a chilling effect scenario, such as that described in a recent ICO decision notice, whereby the Commissioner took a view of how "prolific" a user was, based on their public profile on WhatDoTheyKnow.

I think the data could be presented in aggregate form as part of a transparency report, such as the report WhatDoTheyKnow released in 2021. I would support a more automated way of releasing this data as it may allow for more regular reporting, perhaps even on a rolling month-to-month basis via a dashboard - I wouldn't, however, expect to be able to view that report and identify an individual user.

[HelenWDTK]

This issue has been automatically closed due to a lack of discussion or resolution for over 12 months.
Should we decide to revisit this issue in the future, it can be reopened.