Context
Is your proposal related to a problem?
In the Decidim platform, there are different ways to classify content (resources) and organize information, mainly intended for navigation through filters.
Initially, to meet the needs of Decidim Barcelona, it was decided that this would be done through scopes (at the instance level) and categories (at the process level). Later, classification by areas was also added, which was a copy of the scopes model to define taxonomies not necessarily geographical. By navigating through the initial user stories, one can understand the logic behind this need:
#264
#293
But this has recurrently generated confusion, and has long been an unresolved issue:
#3540
Over time and with the platform's evolution, other needs/requests have emerged that are directly or partially related to how content is classified/filtered within the platform, for example the need to classify/filter processes or assemblies by types.
Describe the solution you'd like
As an admin, I would like to be able to create different taxonomies at the organisation level, which I can then associate to both spaces and components.
Prototype
Figma prototype
Issues
Out of the scope / for the internal backlog
Glossary
- Taxonomy: A structured system for categorizing and organizing content.
- Taxonomy Filter: A feature that allows participants to filter content based on the hierarchical structure of the taxonomy.
- System Filter: A mechanism that allows participants to filter content based on various system-defined criteria.
Context
Is your proposal related to a problem?
In the Decidim platform, there are different ways to classify content (resources) and organize information, mainly intended for navigation through filters.
Initially, to meet the needs of Decidim Barcelona, it was decided that this would be done through
scopes(at the instance level) andcategories(at the process level). Later, classification byareaswas also added, which was a copy of the scopes model to define taxonomies not necessarily geographical. By navigating through the initial user stories, one can understand the logic behind this need:#264
#293
But this has recurrently generated confusion, and has long been an unresolved issue:
#3540
Over time and with the platform's evolution, other needs/requests have emerged that are directly or partially related to how content is classified/filtered within the platform, for example the need to classify/filter processes or assemblies by types.
Describe the solution you'd like
As an admin, I would like to be able to create different taxonomies at the organisation level, which I can then associate to both spaces and components.
Prototype
Figma prototype
Issues
Out of the scope / for the internal backlog
Glossary