Granular content tags

Created on 13 October 2023, about 1 year ago
Updated 16 October 2023, about 1 year ago

Problem/Motivation

As a SM I want to decide where a content tag category should be displayed so I can better target and categorize different entities with specific tags.
Currently we give flexibility to SM to add content tags categories.
Each category is displayed and separate field in the entity creation page and used as filter in overviews and search.
Currently every entity that supports content tags uses the same set of categories.
When a new category is added, it becomnes available for every entity.
This has a big limitation. It is very common that a tag is relevant for events but makes no sense for Groups and the other way around.
Because of this limitation, in the past we had to create ad hoc vocabularies for clients in order to support their migration.
We want to introduce the possibility of choosing in which entity a certain category should be displayed.
The available options are all the entities that are available and that are enabled in the tagging settings here admin/config/opensocial/tagging-settings

Steps to reproduce

Proposed resolution

Add a new field field_category_usage to the social_tagging taxonomy.
Allow SM to choose for which entity a content tag category is available on the taxonomy create/edit page.

Remaining tasks

User interface changes

API changes

Data model changes

New field field_category_usage to the social_tagging taxonomy

✨ Feature request
Status

Fixed

Version

11.11

Component

Tagging

Created by

πŸ‡ΊπŸ‡¦Ukraine kashandarash

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024