I'm going to try to clarify what the original purpose of both was, but, TL;DR: yes, probably right now they are redundant and we should just stay with Scopes.

Scopes

Scopes operate at the organization level (tenant) and the goal is to have several territorial layers (city, district, neighbourhood, etc.) which are then used to define the scope of a given participation space (process, assembly, etc.).

The scopes selector is multiple (for example you can filter and select all proposals of District I and District II).

Areas

On the other hand, for Assemblies (following the Barcelona Council use case) we need to differentiate and filter them according to whether they are territorial (city, district, neighbourhood, etc.) or sectorial (Economy, Social Rights, Culture, etc.).

To do this we needed to have some field in the database to build the list by which we would then filter the Assemblies in the general index. When you set up a new Assembly, you see the two fields:

BUT currently the filter is not yet implemented, so this field has no use.
Also, This field Area should be in the configuration of the general index of Assemblies, but it turns out that there are no configuration options at that level, so that's why the field was included in the general configuration tab.

A possible iteration

I believe (please @decidim/lot-core correct me if I'm wrong), with the current Scopes possibilities (you can create scopes of various types, etc.) there would be no need to keep the Area field, and use the Scopes to filter the Assembly types. I'm just not sure if we can use Scopes for different types of filters.

cc/ @decidim/product

Uh oh!

Difference between scopes and areas #3540

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions