I could use an explanation of the different "Categories" I find in FORMS.
The first is accessed via FORMS > DATA LISTS > [module] DISCUSSIONS > FORUM CATEGORIES in which I have 9 values. These appear as expected when creating a new Discussion.
The second would seem to point to the same list, but when I navigate as follows, there are no values. I navigate to FORMS > CATEGORIES > [module] DISCUSSIONS and here I find it is EMPTY. I add a Category with the very distinct name "Cats > Discussions" but I don't see it anywhere I'd expect to.
Am I right to guess that the second Category I describe above is an alternate method that was not completed or implemented by UNA devs? Or is there something I'm misunderstanding?
Comments
The difference is understandably confusing, but both option work and have differences. There are two different fields:
Category
The "category" (singular) field is for attributing content to a single category. So, a Post for example can only belong to one "category". This is useful if you're organising posts into distinct, folder-like sections.
Categories
The "categories" (plural) field is for attributing content to multiple categories. Say, a Post can be linked to a few categories, and will show up in the browsing in those categories. Multiple categories can be useful for organising content that can belong to more than one section.
Note, that the data sets for Category and for Categories fields are independent of each other. In most cases you are ment to use only one of those fields, but if you choose to use both fields for same content type it would be critical to rename at least one of them and make sure that semantic groups don't overlap. For example, you could use "Category" for something like post types: Tutorial, Announcement, Research Article, Press Release, Recipe, Guide, etc and name it "Type". And the "Categories" for, topic-like sections where a post can potentially be covering two or more at the same time: Wellbeing, Fitness, Cooking, Nutrition, Sports, etc. named as "Topics" . Then, a post could be associated with Type - Recipe, Topics - Cooking, Nutrition, Wellbeing.
G
Okay. In theory I understand the difference now. In practice, I expect to fumble with this for a long time.
Would have made more sense to apply Type or Tag to one of these from the outset and avoid the confusion. But perhaps you can make it a bit clearer by distinguishing between singular vs. plural in the GUI.
Thanks again for the prompt and thorough response!
I agree - we do need to make is easier to understand and in fact we are working on an awesome new "helper" tool for Studio which will provide AI-guided assistance as you are using working on configuration.
One more thing to note - both Category and Categories are module-specific. Posts will have own data sets in Category and in Categories. Videos will have their own, etc. If you are looking for a way to have global multi-module taxonomy you would need to use Labels. Labels are linked to "Channels" which can aggregate content from multiple modules. For example if you create Labels like "Nutrition" and "Wellbeing" - you can create Posts, Videos, Albums - label them as "Nutrition" and then all those content items will show in "Nutrition" channel.
G
Ah. That's excellent info. I'm seeing this pattern throughout the platform. There appears to be some overlap across a number of methodologies. This gives operators more utility. But as with anything powerful, it takes time to understand and master.
Baby steps..... and labels it is (for me)!
I am going to jump in here on the Videos "categories". If we activate, it makes the field mandatory. Despite hours looking to change to non-mandatory, there is no such ability. You can activate the "category" and set its permissions to non-mandatory but you cannot edit "categories" in the same manner.