rubyforgood
Distributions by county report
Summary
Essentials banks need a breakdown of their distributions by county to support quarterly grant requests
Each partner serves one or more counties (or equivalents). Each partner will provide the list of counties they serve, and the estimated percentage of items that will go to each county.
The information needed in the report is county(state), number of items distrubuted, and dollar amount of distribution.
The report would look roughly like this (translated to HE's style, of course)
To support this, we need to add counties/equivalents served to the partner organization page -- both for the partners and the banks -- allowing for multiple counties. The counties added would each have a percentage associated with them (said percentages have to add up to 100). In the report, the distributions will be allocated to each county according to the percentages entered by the partner. It is permitted to have no counties. In that case, all that partner's distributions would be in the "Unknown" category in the report.
Things to Consider
There is a list of all the us counties/equivalents at https://en.wikipedia.org/wiki/List_of_United_States_counties_and_county_equivalents
Criteria for Completion
- [ ] Add counties/equivalents (multi-select) to the partner organization edit. Having no counties is allowed.
- [ ] The partners counties have a percentage associated with them which adds up to 100
- [ ] Add a report for the banks that reports the distributions by counties over a date range
- [ ] Add tests proving that it all works
This is currently waiting for some feedback from Caitlin on the best way to handle the counties/equivalents selection.
Has been discussed by the developer group in the office hours of Sept 18, 2022. Approach to county data -- do it naively, and we'll see if we have to do something else for performance. The actual input, we think, should be informed by the very soon upcoming turbo/stimulus addition issue.
Grabbing this, at least long enough to the initial creation of the counties table
This issue has been inactive for 248 hours (10.33 days) and will be automatically unassigned after 112 more hours (4.67 days).
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue has been inactive for 368 hours (15.33 days) and is past the limit of 360 hours (15.00 days) so is being unassigned.
Still working on this -- making good progess, though I'm now at the point where I need to learn things I don't know to make it work!
This issue has been inactive for 248 hours (10.33 days) and will be automatically unassigned after 112 more hours (4.67 days).
This issue has been inactive for 368 hours (15.33 days) and is past the limit of 360 hours (15.00 days) so is being unassigned.
This issue has been inactive for 253 hours (10.54 days) and will be automatically unassigned after 107 more hours (4.46 days).
This issue has been inactive for 249 hours (10.38 days) and will be automatically unassigned after 111 more hours (4.63 days).
This issue has been inactive for 369 hours (15.38 days) and is past the limit of 360 hours (15.00 days) so is being unassigned.
This issue has been inactive for 248 hours (10.33 days) and will be automatically unassigned after 112 more hours (4.67 days).
This issue has been inactive for 367 hours (15.29 days) and is past the limit of 360 hours (15.00 days) so is being unassigned.
This issue has been inactive for 252 hours (10.50 days) and will be automatically unassigned after 108 more hours (4.50 days).
This issue has been inactive for 372 hours (15.50 days) and is past the limit of 360 hours (15.00 days) so is being unassigned.
This issue has been inactive for 372 hours (15.50 days) and is past the limit of 360 hours (15.00 days) so is being unassigned.