Hints for tagging requests

[RichardTaylor]

Request tags can be added by administrators.

It would be useful to have some prompts of common tags used, including key:value style tags to encourage consistency.

Showing popular tags, or auto-completing tags, might help.

eg. I just added a "deny_eir" tag to flag a request where a public body had denied being subject to the Environmental Information Regulations. I have no way of easily finding out how other admins have tagged such occurrences.

Potential benefits include better data on impact, better access to case studies for promotion and campaigning, collection of data for a transparency report etc.

Ideally this kind of feature would persist and be improved if request specific tags, and tagging, are ever opened to the public:

• Expose per-request tags publicly and enable searching and browsing using such tags #2302

[garethrees]

Kinda similar to being able to attach notes to tags #387

[RichardTaylor]

Nowhere in the in-line help on the WhatDoTheyKnow /admin/bodies/new form does it currently mention the practice of using ch:[company number] or dpr:[ICO registration] both of which prompt special links to be shown on public body pages.

The importance of tagging schools as school (for different treatment of deadlines) and encouraging adding a "urn" for a school (a reference from https://www.get-information-schools.service.gov.uk/).

Consistent tagging of NHS bodies could also be encouraged/enabled though better hints / notes. There are lots of codes at https://odsportal.digital.nhs.uk/ but we're inconsistent using them at the moment.

I suspect elements of this are WhatDoTheyKnow specific?

One of the potential benefits of good consistent tagging linking to third party databases is that it opens the potential to check our database against official databases, and spot required updates.

[RichardTaylor]

My comment there relates to hints for body tags which is off-topic for this ticket but relates to #4761

[garethrees]

Would be helped by #6992.

[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.