Totally agree but we’re starting to see more large customers with massive architectures that need to be using tags rather than categories at a middle level. It’s a difficult sell if it increases the admin/mod load.
In the first use case above, using tags rather than categories is a more flexible (and scalable) approach. @scombs use case also sounds legit.
Which is why I propose that it’s optional. What’s the downside in your view?
For the record I was surprised to see myself as the colleague who disagreed Now that multiple people have asked for it, if we’re sure a category won’t work for their particular size I am definitely not going to push back against this feature being implemented.
We have a fairly large community focused on a Particular piece of software. This software has many features / modules and creating a category for each one would be exhausting and lead to an unwieldy amount of categories. However we would love to force our users to put at least 1 tag on the post so that we more easily search, find related info / topics.
The software in question is a large ERP system, so there are hundreds of modules, addons and bolt ons that people post about and most other people on the site only have experience in a limited number of those modules. So it would help our moderators / community to know without going into each individual post what the general post is about and if they have something useful or not to add.
Note that the “minimum tag validation” on a category will not happen if:
tagging is disabled globally
acting user is staff
acting user does not have sufficient trust level to use/add tags
The option to enforce tagging is available per category. If the tagging is enabled, the setting Minimum number of tags required in a topic will appear under “Edit Category” modal => “Settings” tab. The setting value defaults to 0.