Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Participatory budgeting offline votes upload interface requires CSV data, can't find why it differs from the manual #4774

Open
jorgebg opened this issue Feb 3, 2022 · 2 comments

Comments

@jorgebg
Copy link
Contributor

jorgebg commented Feb 3, 2022

User Story

As a poll officer, I want to upload the offline votes during the "Reviewing voting" phase of a participatory budgeting, so that these votes are added to the total vote count of each of the projects.

Why is this Needed?

The poll officers interface is requiring me to present the data in CSV format (this page, via this link). According to the Consul Administration Guide (page 40), I was expecting to have an interface with an input for each project. And I've been unable to find any documentation about it. I guess I am probably missing steps, but I can't figure out why I'm getting a different interface from the manual.

Description

Type: Feature

I'm missing documentation explaining how the CSV data field of the new ballot sheets form works (what kind of data is expected, and the behavior when uploading it), and why is the interface for participatory budgeting different from the one showed in the Consul Administration Guide (page 40).

Current Behavior

The poll officers interface is requiring me to present the data in CSV format:

image

Expected Behavior

According to the Consul Administration Guide (page 40), I was expecting to have an interface with an input for each project:

image

Steps to reproduce

Create a participatory budgeting as explained in the Consul Administration Guide, activate the "Reviewing voting" phase, and try to upload offline voting results from the poll officers interface.

Definition of Done

List existing documentation that explains how the CSV data field of the new ballot sheets form works (what kind of data is expected, and the behavior when uploading it), and clarify the difference of the interface for participatory budgeting in the Consul Administration Guide (page 40).

I guess I am probably missing steps, but I can't figure out why I'm getting a different interface from the manual.

@jorgebg jorgebg changed the title Participatory budgeting offline votes upload interface requires CSV data, and it differs from the manual Participatory budgeting offline votes upload interface requires CSV data, can't find why it differs from the manual Feb 3, 2022
@javierm
Copy link
Member

javierm commented Mar 21, 2022

Hi, @jorgebg 😄.

The documentation doesn't show the case for budget polls; only for "regular" polls. Sorry for that! 🙏

The expected CSV data format is something like 1,2,3;4,5,6 or 1,2,3\n4,5,6, where 1,2,3 are the IDs of the investments the first person voted for and 4,5,6 are the IDs of the investments the second person voted for.

This was the required format because we only knew about one place using (or planning to use) physical ballots during the final voting of participatory budgets (Madrid) and they had CSV files using this format, generated by an OCR which read the physical ballots.

I'm now going to look at the pull request where you mention there's a problem recounting these votes.

@coslajohn
Copy link
Contributor

I have also been looking at this issue.

We have examples of offline budget ballots which only generate totals and it would be good to be able to include those in the same way as the offline votes for regular polls

Would it be possible to choose the method of loading offline votes?
Choose method from

  1. upload per project totals the same as regular polls
  2. enter csv ballots the way it works at the moment
  3. upload csv file of ballots

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants