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.

Sign up for GitHub

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

Jump to bottom

Figure out how to carry through expenditures #29

Closed
tdooner opened this issue Sep 19, 2016 · 0 comments
Closed

Figure out how to carry through expenditures #29

tdooner opened this issue Sep 19, 2016 · 0 comments
Assignees
@monkeyhippies

Comments

@tdooner
Copy link
Member

tdooner commented Sep 19, 2016 •
edited
Loading

If Committee A gives money to Committee B which then spends the money supporting a ballot measure, we might accidentally double-count that money in support of the measure. (i.e. Just Cause vs Committee To Protect Oakland Renters)
@tdooner tdooner changed the title TODO figure out how to carry through expenditures Figure out how to carry through expenditures Sep 19, 2016
tdooner added a commit that referenced this issue Sep 19, 2016
@tdooner
Add Form 497 to ReferendumSupportersCalculator
4aef139 
This is a somewhat complicated implementation, but out of necessity:
Form 497 rows do not contain the "Sup_Opp_Cd" column needed to bucket an
expenditure into either supporting or opposing a ballot measure. So we
must guess.

Also, I suspect this will double-count in some cases like Just Cause --
they gave money to a committee that is basically themselves. I don't
think we should count this money twice. I opened #29 to track this.
@tdooner tdooner mentioned this issue Sep 21, 2016
Closed
tdooner added a commit that referenced this issue Sep 29, 2016
@tdooner
Merge pull request #43 from monkeyhippies/dedup_expenditures
42458f0 
Fixes #29 dont count expenditures to other committees
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@monkeyhippies monkeyhippies

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@tdooner @adborden @monkeyhippies