I am trying to investigate how we can set different attributes on stories to implement tag/topic/taxonomy concepts, for navigation, editorial clustering and topic pages. We have a multisite, multilanguage setup, with the need to have different and flexible tags/topics for the different organisations. The different languages (scandinavian languages) is also an issue, as words can be simular, but not exactly the same. The stemming also differs.
So far I have seen taxonomy concept of tags , labels/kickers (can be organised in types and be a kind of taxonomy) , and sites/sections.
My analysis so far
* tags - are global , and does not really have a taxonomy (sections) that can be easily managed by editors. There is also no permissions or per-website concept
* labels/kickers - are globally shared. This concept has somewhat flexible taxonomy that can be configured, and is exposed in composer. But the configuration is somewhat hidden in the composer settings, alongside lots of other configs that maybe should not be widely exposed.
* Sites/sections are set per website, which is good. It is however bound to the actual structure of the site, and may not fit well as a tag concept.
So, what I would like to have is a tag/taxonomy/topic concept that is well exposed for the editor, possible to search and navigate ( create parent child/nodes) , and the tags should be possible to filter/limit to a specific website. Maybe the distributor concept can be used to set correct distribution per tag?
I the composer, the tags hierarchy should be easily searchable, possibly as a popup like the photo center and videos. Displaying the tags for selection in a similar way that kickers/labels in the composer is also an option.
The labels/kickers concept can be leveraged and as a second tag concept. In that case it should be made more easily available to the editor, and it should be possible to limit the labels/kickers per site, or by using distributors.