Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Manual WhatDoTheyKnow Transparency Report for 2023 #1536

Closed
HelenWDTK opened this issue Dec 16, 2022 · 3 comments
Closed

Manual WhatDoTheyKnow Transparency Report for 2023 #1536

HelenWDTK opened this issue Dec 16, 2022 · 3 comments

Comments

@HelenWDTK
Copy link
Contributor

A WhatDoTheyKnow Transparency Report was produced in 2021 and 2022.

This ticket is for a 2023 version.

@HelenWDTK
Copy link
Contributor Author

Noting #1535

@RichardTaylor
Copy link

RichardTaylor commented Dec 16, 2022

I'd like to more clearly separate the substantive takedowns from others; substantive being those involving the core substance of a FOI request/response.

We might want to have various levels of "substantive"

  • removing just one or two bits of personal data from a release;
  • when we have to take a significant element of a request/response down (which is very rare)
  • when largely non-FOI correspondence includes, often incidentally / accidentally some element which could be seen as FOI

We know that we go to great lengths to avoid removing FOI requests/responses from public view, and ideally that would be reflected in the report. To-date we've not really been collecting data on takedowns that really enables us to show how we've been able to preserve the archive of requests/responses.

Preserving the archive is one aim, but we also want to do the right thing. Not every substantive takedown is bad. Perhaps if the report did drill down to a handful of substantive cases, we could write a couple of sentences on each one.

Edit: "reflected in report" > "reflected in the report"

@RichardTaylor
Copy link

if the report did drill down to a handful of substantive cases, we could write a couple of sentences on each one.

Ideally we'd already have a blog on each one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants