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

Add pabulib export format for budgets #13671

Draft
wants to merge 12 commits into
base: develop
Choose a base branch
from

Conversation

ahukkanen
Copy link
Contributor

@ahukkanen ahukkanen commented Nov 15, 2024

🎩 What? Why?

The pabulib export format (.pb) allows calculating the participatory budgeting results with the Method of Equal Shares.

This PR adds the possibility to export PB voting results separately for each budget in the pabulib format.

This export can be provided for the following tool to compute the results according to this algorithm:
https://equalshares.net/tools/compute/

Further reading:
https://pabulib.org/Pabulib_A_Participatory_Budgeting_Library.pdf

Created as a draft PR because tests are currently missing.

Testing

  1. Go to budgets
  2. Go to manage the projects within a budget
  3. Click the "Export all" dropdown
  4. Select "Projects as Pabulib"
  5. See the export screen to define the metadata for the export
  6. Click the "Export" button after defining the metadata
  7. See a .pb file being downloaded
  8. Drop the .pb file to the Equal Shares Online Computation Tool
  9. See the results of the voting using the Equal Shares algorithm

Note that currently the pabulib format is specific to one budget. Therefore, the export functionality is added inside a budget.

📷 Screenshots

Export dropdown:
The projects export dropdown

Export screen:
The export screen

@ahukkanen ahukkanen changed the title Add paulib export format for budgets Add pabulib export format for budgets Nov 15, 2024
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This pull request does not contain a valid label. Please add one of the following labels: ['type: feature', 'type: change', 'type: fix', 'type: removal', 'target: developer-experience', 'type: internal']

@ahukkanen ahukkanen added the type: feature PRs or issues that implement a new feature label Nov 15, 2024
github-actions[bot]
github-actions bot previously approved these changes Nov 15, 2024
github-actions[bot]
github-actions bot previously approved these changes Nov 16, 2024
github-actions[bot]
github-actions bot previously approved these changes Nov 16, 2024
github-actions[bot]
github-actions bot previously approved these changes Nov 16, 2024
@andreslucena
Copy link
Member

Hi @ahukkanen
Do you have a Metadecidim proposal for this? Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature PRs or issues that implement a new feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants