Skip to content

Implement the “Data export” recommendations from the Interoperable Deliberative Tools Specification (v0.7.1) #13252

@andreslucena

Description

@andreslucena

Ref: MGOV10

Is your feature request related to a problem? Please describe.
Currently Decidim provides a zip file with some “Open Data” files.

These are always available through the same URL, although we don’t have any explanation about which exactly are these files, how to open them and work with them.

Untitled

Describe the solution you'd like
To implement the recommendations from the Interoperable Deliberative Tools Specification v0.7.1. There will be a new page in https://try.decidim.org/open-data with

Describe alternatives you've considered
To add this information to the README file of the zip, but opening a zip file with a file without any other explanation can be too scary for non computer-savvy people.

Additional context

This is based in the https://docs.google.com/document/d/1px14n1qSKdsaqzUeKLfudEZ7LX0nvED09q2guGbRFY0/edit

Data export

A deliberative / governance tool, service, or library (henceforth, just tool) following this specification MUST publish a flatfile such as JSON or CSV at appropriate intervals of the deliberative process.

Tools MUST default to open, meaning that flatfiles generated from deliberative and governance processes are by default accessible without any tokens or prior authentication. If published openly, flatfiles SHOULD be indexable, i.e. all data should be published to a set of stable URLs that are publicly documented.

Tools MAY also provide the option to provide such flatfile data privately, e.g. with an obfuscated URL or URI, or with API tokens or authentication flows.

To facilitate integration, flatfiles SHOULD be accompanied by an appropriate data license and a data card.

Tools SHOULD provide a publicly accessible URL through which users can pull or request flatfiles, e.g. of the most recent state of a deliberative process.

Does this issue could impact on users private data?
No, this is public data.

Acceptance criteria

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

Status

Merged

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions