You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Context
Currently, as a developer, I can struggle to understand how works the Decidim database.
Indeed, a "lite" decidim installation (ie. with only official modules) has about ~120 tables with ~1200 columns, which can bring some confusion both for :
developers to understand what's the purpose of each table in the global scheme
data workers : analyse and extract data, since the open data rely on such diagram
Solution
It would be great to use a dedicated language to describe relations in the Decidim database.
We could DBML as a first step to describe tables and columns precisely, and embed such diagrams/docs in the current documentation, but I'm open to any other tool that could be relevant, as long as it is versionable on Git
Use of such tools would also ease the process of seeing differences between the different minor versions of Decidim.
Founding
Open Source Politics
The text was updated successfully, but these errors were encountered:
Regarding the visualization, I had also make some tryouts with https://github.com/voormedia/rails-erd, although I have to say that with that many tables the visualization wasn't easy to understand. I guess we would have the same problem with the visualization software used by DBML, do you have any example of an app with this size? This is probably just to say that a default installation of Decidim is too big to understand and we should go to a model where the amount of modules/features on a default installation is smaller than what we have, and then have these kind of graphs but only for a given module (like the ERD diagram of proposals, another for participatory_process, etc)
Context
Currently, as a developer, I can struggle to understand how works the Decidim database.
Indeed, a "lite" decidim installation (ie. with only official modules) has about ~120 tables with ~1200 columns, which can bring some confusion both for :
Solution
It would be great to use a dedicated language to describe relations in the Decidim database.
We could DBML as a first step to describe tables and columns precisely, and embed such diagrams/docs in the current documentation, but I'm open to any other tool that could be relevant, as long as it is versionable on Git
Use of such tools would also ease the process of seeing differences between the different minor versions of Decidim.
Founding
Open Source Politics
The text was updated successfully, but these errors were encountered: