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

Agree, document, and make consistent, our use of request tags #1158

Closed
RichardTaylor opened this issue Apr 27, 2022 · 4 comments
Closed

Agree, document, and make consistent, our use of request tags #1158

RichardTaylor opened this issue Apr 27, 2022 · 4 comments
Labels

Comments

@RichardTaylor
Copy link

Use a list request tags already in use (ordered by frequency, descending) to document and improve our policy on our use of request tags.

Wiki page:

https://wdtkwiki.mysociety.org/wiki/Request_tags

This follows the successful review of tags we use to track and highlight poor performance by public bodies:

We sporadically and inconsistently use tags for other purposes eg. noting substantive take-downs, referrals to the ICO etc.

@RichardTaylor
Copy link
Author

We certainly need this ticket if we're going to use request tags effectively. We've used 164 different request tags, and 99 of those we've only used once.

Areas in which we could use systematically use tags:

These could help people find requests of interest and aid transparency over how we run the site.

Consider:

  • Avoid manual tagging of things which are already recorded automatically, or could be recorded automatically.
  • Avoid duplication of work eg. how do we ideally want to record an ICO decision - via a citation linking to a decision notice I suspect - manually adding a tag too would be more work.
  • Do we want automatically added tags? We may already have some of these eg. citation which appears to have fallen out of use?
  • Tagging of requests for research processes doesn't appear to have been done within the system. Do we have tags we could import?
  • Incentives to add tags. Currently they are largely internal only, but it is possible to search by tag. Ticket for exposing tags: Expose per-request tags publicly and enable searching and browsing using such tags alaveteli#2302
  • Do we want to avoid tagging both threads in the inbox and the related request with a similar tag eg. defamation or is that useful duplication? Problem arises as our system of dealing with takedown requests etc. is not the same as the core request making system Bring user support and takedown requests within the system alaveteli#419
  • Request tag related functionality eg. not closing requests referred to the ICO to new responses, or extending the time before closure.

Related:
https://wdtkwiki.mysociety.org/wiki/Request_tags
mysociety/alaveteli#6419

@RichardTaylor
Copy link
Author

For requests where a charge is proposed we could tag eg.

fee_proposed fee_proposed:129.40

There would be an incentive to do this kind of tagging if we had an associated page or pages listing

  • recent requests where the response was to offer the data for a fee
  • requests ordered by fee proposed, descending.

@RichardTaylor
Copy link
Author

RichardTaylor commented Jun 24, 2022

Maybe more of a campaign tag might be offered_to_sell_data rather than fee_proposed .. often the fees aren't fees as under the FOI, but rejections on the grounds information is reasonably accessible as it's sold by the public body.

@RichardTaylor
Copy link
Author

RichardTaylor commented Jun 24, 2022

I'm contemplating a too_disorganised tag for requests where the refusal is on cost limits but really the issue appears to be the body doesn't have its records in order such that it can efficiently provide a response. Tag could be just disorganised

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

No branches or pull requests

3 participants