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

Consider changing contributor_aggregate_YTD #5765

Open
cnlucas opened this issue Mar 15, 2024 · 0 comments
Open

Consider changing contributor_aggregate_YTD #5765

cnlucas opened this issue Mar 15, 2024 · 0 comments

Comments

@cnlucas
Copy link
Member

cnlucas commented Mar 15, 2024

What we’re after

contributor_aggregate_ytd is per cycle if it's a Form 3 since 2000, but the field is the same for all other receipts where the field is actually per calendar year. This is a bit confusing and inaccurate for our users. We should consider having a separate field for cycle YTD. We should, if we can't do this, consider adding something to explain this issue.
https://api.open.fec.gov/v1/schedules/schedule_a/?two_year_transaction_period=2016&recipient_committee_designation=P&per_page=20&api_key=DEMO_KEY&sort=-contribution_receipt_date&sort_hide_null=false&sort_null_only=false

the form change information is here (thanks Dorothy!)

Related ticket(s)

(Include the tickets that either came before, after, or are happening in tandem with this new ticket)

  • [ ]

Action item(s)

(These are the smaller tasks that should happen in order to complete this work)

  • [ ]

Completion criteria

(What does the end state look like - as long as this task(s) is done, this work is complete)

  • [ ]

References/resources/technical considerations

(Is there sample code or a screenshot you can include to highlight a particular issue? Here is where you reinforce why this work is important)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 🔨 Pre-refinement
Development

No branches or pull requests

1 participant