Propose new features
Designing Decidim together
PROBLEM:
In some cases it is required to be able to filter participatory processes by type and subtype. The "processes" module allows creating groups of processes, but does not have a filter field available (as if it exists instead in the "assemblies" module).
SOLUTION:
Add a field and a filter functionality "type of processes" to allow filtering processes by type, as we can do in "assemblies".
ALTERNATIVES:
It is not convenient to use the available global classification systems ("scopes" and "areas") because they don't allow a differentiated application according to the context (show different filters in /processes or in /assemblies or even in /group_process, for example). And they are systems that are too intertwined with many other modules & components.
ADDITIONAL CONTEXT:
In order to create the new process_type feature, we will...
-Create a Decidim::ParticipatoryProcessType model and an optional association with participatory processes.
-Add CRUD management from admin of process types and include the association in the processes form.
-Add a filter to set process_type in the global processes list or current processes group ( /processes & /processes_groups/X ), like the existing assembly_type selector.
With some extra enhancements:
- This filter should not appear if there are no processes with a type assigned.
- The filter should only display the different types of available processes in the context (global processes list or current processes group)
-Make sure to add tests to keep test coverage at required levels.
Could this issue impact on users private data?
NO.
FUNDED BY:
Government of Navarra / Nafarroako Gobernua
This proposal has been accepted because:
- Reviewed by @product and accepted in the main project
- It is funded by Government of Navarra
- Developed by Populate
- Available in release 0.27 via #8583
Related images
Report inappropriate content
Is this content inappropriate?
Comment details
You are seeing a single comment
View all comments
Conversation with Carol Romero
Hi there, @aramgob could you explain the use case a little more? What would be those types of processes?
In this case, the aim is to distinguish between participatory processes and participation in regulations and to be able to filter the processes of each “group” by type, showing only the categories that correspond to each “group” to avoid confusing the user.
The categories of "type of process" in this case will be related to the "type of policies": Laws, Plans, Projects, preliminary consultations, Public policy. But in other use cases it could be used to have the possibility of filtering with specific categories to the processes, regardless of the areas and scopes. And not showing up when not in use.
This new filter "process type" (will show only the categories that have associated processes) can be applied in addition to the global filters (scopes and area).
Global filters (scope and area) affect all participatory spaces (processes, process groups, assemblies, etc.) and in this case they are used as follows:
- Scopes: will be used to filter based on organizational structure with nested categories.
- Areas: will be used to filter by subject areas.
If you want, I can try to explain some other solutions that have been applied in other cases for similar requirements and their “problems”.
@carol Navarra have two types of processes, and for each group they have different categories. And they want to allow users to browse them independently (so categories from type 1 doesn't get mixed with those from type 2). After reviewing many options, we have come to the conclusion that this would solve the problem, with a relative simple solution, maintaining the same standard as in Assemblies, and being flexible for other cases.
For example, this could be used to simplify by much the setup that GenCat has setup to have the /regulations section, which is just a list of processes but with a new "Type" filter.
If our proposal existed, they could just create two groups of processes: one for regular processes, and other for regulation processes. When the processes filter would be shown, in "Type" only categories that are used for processes in that process group would be shown. Also, by using the process group you would get a lot more functionality.
Important to note: this is no more than a more or less elegant hack, without introducing any breaking change and without compromising too much for the future; the more solid solution would be to rethink the classification system to make it more flexible, but that would be a much more complicated projects.
Hi @carol any updates about this from product team? What are your thoughts around this issue? Thanks!
We reviewed it at Product. Ok to the proposal, just keep in mind that the way it is displayed will probably change with the redesign process.
For sure ;)
Great, thanks.
Hi @carol we have realized that could be necessary in order to have consistent user/ participant experience, maintain the same behaviour in "assamblies type filter" as "process type filter":
- Behaviour to reproduce: The options for this filter should not appear if there are no processes/assamblies with a type assigned.
Exampe: There are 3 type of process/assamblies defined, but only 2 of these types have process/assemblies assigned, then the filter will only show 2 type of process/assamblies (hidding this one that has not any process/assembly assigned).
If product give us "ok" we will prepare PR for both solutions when are ready.
Thanks @aramgob, it's fine from @product.
Loading comments ...