Ref: MGOV04

Is your feature request related to a problem? Please describe.

All Decidim installations have a functionality for downloading open data in CSV format, to facilitate the study of the platform's public content for researchers who do not have a high technical level.

Since there has been a constant development adding new features, there are cases where some data is not published in this file. Another shortcoming of this functionality is that it is not documented what each of the files corresponds to, as well as the headers (columns) of the CSVs.

This is closely related to #13197, as it is similar, but the focus is different:

• Update of the CSV open data for components #13197: its focus is on components and metrics/statistics
• Add spaces to the CSV open data file  #13248 (this): its focus is on spaces

Describe the solution you'd like

Add new fields to the Open Data file, so it’s updated with all the participation data that the platform generates.

Additionally, these files and fields will be documented so that they can be understandable to researchers when downloaded, without having to study the platform in-depth.

• Add a README file to the export file, this text file should have a definition of all the fields that are downloaded.
• Add to the Open Data file:
  • Participatory processes
  • Assemblies
  • Initiatives
  • Conferences
  • Participatory spaces metrics (Metrics of each space)

It needs to take into account the different states in each case: an unpublished participatory process, a private assembly, a private but transparent assembly, a created but not approved initiative, etc.

• Current Open data file
  • proposal_comments
  • proposals
  • meeting_comments
  • meetings
  • projects
  • results
  • result_comments

Describe alternatives you've considered

We could add other formats for the ZIP file (as JSON) but we prefer to have leave it easy for researches without advanced computer science proficiency to know how to work with the information from these files. For people with programming and advanced usage we already have the GraphQL API (/api).

Additional context

As mentioned in the description, this is complementary with #13197.

Does this issue could impact on users private data?

No, this is public data already. We only need into account the different statuses of the Spaces.

Acceptance criteria

• Given that I’m a visitor
  When I download the Open Data file
  Then, I get all the CSV files and a README file with the definition of all the concepts downloaded, so I can easily understand the data.
• Given that there’s an unpublished Participatory Process
  When I download the Open Data file
  Then it isn’t available in it
  And there’s a spec for this specific use-case
• Given that there’s a private Participatory Process
  When I download the Open Data file
  Then it isn’t available in it
  And there’s a spec for this specific use-case
• Given that there’s a public Participatory Process
  When I download the Open Data file
  Then it is available in it
  And there’s a spec for this specific use-case
• Given that there’s an unpublished Assembly
  When I download the Open Data file
  Then it isn’t available in it
  And there’s a spec for this specific use-case
• Given that there’s a private Assembly
  When I download the Open Data file
  Then it isn’t available in it
  And there’s a spec for this specific use-case
• Given that there’s a private and transparent Assembly
  When I download the Open Data file
  Then it is available in it
  And there’s a spec for this specific use-case
• Given that there’s an public Assembly
  When I download the Open Data file
  Then it is available in it
  And there’s a spec for this specific use-case
• Given that there’s a public Conference
  When I download the Open Data file
  Then it is available in it
  And there’s a spec for this specific use-case
• Given that there’s an unpublished Conference
  When I download the Open Data file
  Then it isn’t available in it
  And there’s a spec for this specific use-case
• Given that there’s an Initiative with state “Created”
  When I download the Open Data file
  Then it isn’t available in it
  And there’s a spec for this specific use-case
• Given that there’s an Initiative with state “Discarded”
  When I download the Open Data file
  Then it isn’t available in it
  And there’s a spec for this specific use-case
• Given that there’s an Initiative with state “Validating”
  When I download the Open Data file
  Then it isn’t available in it
  And there’s a spec for this specific use-case
• Given that there’s an Initiative with state “Open”
  When I download the Open Data file
  Then it is available in it
  And there’s a spec for this specific use-case
• Given that there’s an Initiative with state “Rejected”
  When I download the Open Data file
  Then it is available in it
  And there’s a spec for this specific use-case
• Given that there’s an Initiative with state “Accepted”
  When I download the Open Data file
  Then it is available in it
  And there’s a spec for this specific use-case