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

Auto tag authorities that have received no/very few requests #7361

Closed
FOIMonkey opened this issue Oct 13, 2022 · 6 comments · Fixed by #7363
Closed

Auto tag authorities that have received no/very few requests #7361

FOIMonkey opened this issue Oct 13, 2022 · 6 comments · Fixed by #7363
Labels

Comments

@FOIMonkey
Copy link
Collaborator

Similar to the auto tagging of missing emails, this would enable us to suggest users make requests to these authorities and/or offer suggestions as to what they could ask for.

@FOIMonkey
Copy link
Collaborator Author

Related to #7362

mysociety-pusher pushed a commit that referenced this issue Oct 14, 2022
Automatically apply and remove a tag to bodies that have a low number of
public requests, so that users can find them via a public search to help
bootstrap basic transparency/site content, and admins can add a
tag-based note to suggest generally useful first requests.

The changelog suggests a one-shot script to mass-apply the tag to
existing bodies that are missing an email.

Fixes #7361
@garethrees
Copy link
Member

Yep, this was pretty trivial #7363.

A couple of questions:

  1. What counts as "very few"? I've gone with "under 5". Feels about right?
  2. What do we want the tag to be called. I've gone with not_many_requests, but it's an easy change if we can think of something a bit better.
  3. I've ignored the fact there may be 100s of currently-private requests. Do we want the tag applied if that's still the case, or do we only want it applied where there are very few requests total (rather than very few currently public requests)?

@FOIMonkey
Copy link
Collaborator Author

  1. I think less than 5 makes sense for now, we can always up it later.
  2. not_many_requests is perfect.
  3. I'm fine ignoring embargoed requests. The chances of there being tons made to a tiny parish meeting somewhere is negligible, and it keep the appearance of any note consistent with what the average user/visitor can see.

mysociety-pusher pushed a commit that referenced this issue Oct 14, 2022
Automatically apply and remove a tag to bodies that have a low number of
public requests, so that users can find them via a public search to help
bootstrap basic transparency/site content, and admins can add a
tag-based note to suggest generally useful first requests.

The changelog suggests a one-shot script to mass-apply the tag to
existing bodies that are missing an email.

Fixes #7361
@WilliamWDTK
Copy link
Collaborator

I'd agree with only counting public (non-embargoed, non-reduced-prominence) requests, such that the presence of the note is consistent with the body's public page.

Regarding number, do we have means/medians/etc for the number of public requests to bodies with which this could be compared?

mysociety-pusher pushed a commit that referenced this issue Nov 10, 2022
Automatically apply and remove a tag to bodies that have a low number of
public requests, so that users can find them via a public search to help
bootstrap basic transparency/site content, and admins can add a
tag-based note to suggest generally useful first requests.

The changelog suggests a one-shot script to mass-apply the tag to
existing bodies that are missing an email.

Fixes #7361
@garethrees
Copy link
Member

Potential source of good questions https://clairemiller.net/blog/2013/01/a-great-big-list-of-foi-ideas/

@garethrees
Copy link
Member

FDS have a great list of suggested requests based on authority category https://fragdenstaat.de/hilfe/erste-anfrage/anfrage-ideen/

gbp pushed a commit that referenced this issue Oct 20, 2023
Automatically apply and remove a tag to bodies that have a low number of
public requests, so that users can find them via a public search to help
bootstrap basic transparency/site content, and admins can add a
tag-based note to suggest generally useful first requests.

The changelog suggests a one-shot script to mass-apply the tag to
existing bodies that are missing an email.

Fixes #7361
@gbp gbp closed this as completed in b12b788 Nov 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants