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
Is your feature request related to a problem? Please describe.
Currently, the Decidim export files for administrators do not offer all the data collected by the platform, due to the addition of new functionalities in recent years that generate new data. Therefore, it is necessary to update the CSV export files functionality so that it can collect all the available data on the platform.
As there are lots of modules and features, this issue will be focused on CSV exports for components.
Describe the solution you'd like
All models and their fields within the platform's administrator interface will be reviewed, and a comparison will be made to determine which of these are currently available in the CSV export files. If any fields are found to be unavailable, the addition of these models and/or fields to the CSV files will be developed.
Describe alternatives you've considered
To have some kind of contract in the models/schemas that could ease-up this kind of discovery of new fields.
To have a better review process when we introduce new fields.
To have a CI mechanism to detect when there’s a new table/column in the database so we can allow-list this new field (after it was added in the CSVs/API).
To regularly make this same task (yearly or every two years)
Additional context
This is related to BSC06 and MGOV06, as the problem is the same. The main difference is that:
Does this issue could impact on users private data?
No, as this is private data for administrators we don’t have private data.
Acceptance criteria
Given that I’m a reviewer,
I have a CSV file for each module with all the fields from the generated db/schema.rb of the development_app
With the columns table, column, csv_published, csv_to_be_published.The modules:
Given that I’m an administrator,
And I go to the admin interface for Accountability
And I click in the “Export all” button,
Then I can see new fields in this generated file (if there’s any)
Given that I’m an administrator,
And I go to the admin interface for Accountability
And I go to the Import page
And I import an exported process,
Then I can see new fields in imported Process (if there’s any)
Given that I’m an administrator,
And I go to the admin interface for Budgets
And I click in the “Export all” button,
Then I can see new fields in this generated file (if there’s any)
Given that I’m an administrator,
And I go to the admin interface for Debates
And I click in the “Export all” button,
Then I can see new fields in this generated file (if there’s any)
Given that I’m an administrator,
And I go to the admin interface for Meetings
And I click in the “Export all” button,
Then I can see new fields in this generated file (if there’s any)
Given that I’m an administrator,
And I go to the admin interface for Proposals
And I click in the “Export all” button,
Then I can see new fields in this generated file (if there’s any)
Ref: MGOV06
Is your feature request related to a problem? Please describe.
Currently, the Decidim export files for administrators do not offer all the data collected by the platform, due to the addition of new functionalities in recent years that generate new data. Therefore, it is necessary to update the CSV export files functionality so that it can collect all the available data on the platform.
As there are lots of modules and features, this issue will be focused on CSV exports for components.
Describe the solution you'd like
All models and their fields within the platform's administrator interface will be reviewed, and a comparison will be made to determine which of these are currently available in the CSV export files. If any fields are found to be unavailable, the addition of these models and/or fields to the CSV files will be developed.
Describe alternatives you've considered
To have some kind of contract in the models/schemas that could ease-up this kind of discovery of new fields.
To have a better review process when we introduce new fields.
To have a CI mechanism to detect when there’s a new table/column in the database so we can allow-list this new field (after it was added in the CSVs/API).
To regularly make this same task (yearly or every two years)
Additional context
This is related to BSC06 and MGOV06, as the problem is the same. The main difference is that:
Does this issue could impact on users private data?
No, as this is private data for administrators we don’t have private data.
Acceptance criteria
I have a CSV file for each module with all the fields from the generated db/schema.rb of the development_app
With the columns
table, column, csv_published, csv_to_be_published.The modules:And I go to the admin interface for Accountability
And I click in the “Export all” button,
Then I can see new fields in this generated file (if there’s any)
And I go to the admin interface for Accountability
And I go to the Import page
And I import an exported process,
Then I can see new fields in imported Process (if there’s any)
And I go to the admin interface for Budgets
And I click in the “Export all” button,
Then I can see new fields in this generated file (if there’s any)
And I go to the admin interface for Debates
And I click in the “Export all” button,
Then I can see new fields in this generated file (if there’s any)
And I go to the admin interface for Meetings
And I click in the “Export all” button,
Then I can see new fields in this generated file (if there’s any)
And I go to the admin interface for Proposals
And I click in the “Export all” button,
Then I can see new fields in this generated file (if there’s any)