Tags - case sensitivity

When a user enters tags for a dataset, they may begin typing and then select an existing tag for autocompletion, or they may simply keep typing. Data may also be deposited via the api and so autocompletion of tags is not utilised. This leads to situations where you have the same tag being treated as different dependant on the case used when entered.

E.g. I have datsets tagged with 'flora', and others tagged with 'Flora' - and for the purposes of filtering by tag they are treated as different (the tags list at the left of the screen in the 'Data' view (pic below) shows them as separate tags).

It would be nice if CKAN could either a) be case insensitive to tags, or b) be configured (ini setting) to standardise tags as say either lower or sentence case and convert tags on the fly to conform when they are entered.

This could tie in with #68 and ultimately a tag management UI for cleaning up tags (e.g. managing variants of the same tag such as plurals or misspellings.... and fixing in bulk rather than 1 by 1.


No files, tests, or entry points are named, and the repository is marked deprecated. First clarify whether tags should be case-insensitive or normalized through configuration, including API and filtering behavior. Done would require an agreed scope and a documented way to handle existing variants such as “flora” and “Flora”.

Written by the indexing model from the issue text.