Propose new functionalities for Decidim software
#DecidimRoadmap Designing Decidim together
Is your feature request related to a problem?
When an organization has a lot of scopes (let's say more than 200), the scopes index page in BE takes time to load. In general, the scopes are not scalable (i.e. in my interests in user account).
As Decidim is being used by more and more institutions (cities, counties, etc.), the scope will need to adapt to new areas, with more and more scopes needed. For exemple, a county might want to have all of its cities displayed as scopes, but with more than 1000 scopes, the scope index page is crashing.
Describe the solution you'd like
To solve this scope scalability problem, it would be useful to add pagination to the /admin/scopes page, so that in case of a lot of scopes, the loading of the page is not impacted.
Additional infos
In our use case, this feature would be used to display an interactive map with geocoding available with this module : https://github.com/OpenSourcePolitics/decidim-module-homepage_interactive_map
Describe alternatives you've considered
Add this feature to the module.
Does this issue could impact on users private data?
No
Funded by
OSP
This proposal has been accepted and is under development
Report inappropriate content
Is this content inappropriate?
5 comments
Conversation with Pierre Mesure
Regarding the map, an inspiration could be CONSUL which has a clickable map to show the various districts of a city and enable people to choose their area and see its proposals.
https://consul.demokratiskastader.se/proposals/map?locale=en
We have a plugin that allows to easly configure sensible areas in a map https://github.com/Platoniq/decidim-module-navigation_maps
Yes, it looks really promising, I haven't tried it yet.
Thanks for your answers!
I didn't know the Consul map, it's nice! And I tested the navigation maps module, it's really cool but I think it's better for other use cases (with drawable tiles).
In our case, the map is related to scopes and assemblies: scopes are the different neighbourhoods (delimited by Geojson tiles) and assemblies are the neighbourhoods spaces. You can see what it looks like at the bottom of this homepage: https://jeparticipe.toulouse.fr/
May be my proposal was not clear enough, it's more about the scalability of the scopes. If we want to have a lot of scopes, the scopes page can become fast unmanageable.
I think there could be potentially a lot of related problems, just to be clear, what we could easily agree is in this one:
As it doesn't scale for sure and for consistency, we should implement that. The "happy path" here is to use the "child scopes" feature. For instance, in Barcelona we have 73 neighborhoods but only 10 districts, so the first levels of scopes is 10 and then the neighborhoods belong to these scopes.
What I'm afraid, and I think it would be more difficult to reach a consensus as they're multiple difficulties/solutions for having 200 scopes is the other pages, just in the top of my mind:
proposals/meetings filtering
select scope modal in proposal creation
(almost every place where we show the list of scopes)
So, on every one of these places we should discuss the solutions as I think are not so easy to solve.
Add your comment
Sign in with your account or sign up to add your comment.
Loading comments ...