-
Notifications
You must be signed in to change notification settings - Fork 106
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
Design endpoints - names, filters, output fields, data structure, sort capability #4175
Comments
Draw.io link: https://www.draw.io/#G108WMWi2-V0EOjRuKer8m0uzOu_aJK9M8 Option 1
From @fec-jli: the initial thought we may need 5 endpoints. I just put endpoints list here, after we create issue, we can put inside the tickets. /* Option 1 */ 5 endpoints:
(left side cand list; right side summary; Expenditure Tab ):
===========================================================
(national map circle per candidate): (view on DISCLOSURE.PRES_CA_CM_SCHED_A_JOIN_20D / _16 Filter: cand_id, cycle
===========================================================
(national map right side contribution size)
===========================================================
(dateThrough) (DISCLOSURE.PRES_NML_FORM_3P_20D / _16)
===========================================================
(State Map) get all candidate list
=========================================================== Option 2/* Option 2 */ 5 endpoints:
combine state data with national data
(left side cand list, national and state wide get all candidate list) Include rounded and original totals
(right side summary; Expenditure Tab ): -- TODO: Determine financial summary fields, use readable column names
===========================================================
(national map right side contribution size) TODO: Consider using "size" filter like /schedules/schedule_a/by_size/ instead (in addition to? ) contribution_range_id The total all contributions in the following ranges: -0 $200 and under
===========================================================
(national map circle per candidate):
===========================================================
(dateThrough) (DISCLOSURE.PRES_NML_FORM_3P_20D / _16) --TODO: Bring in 2016 data
=========================================================== |
As a team, we decided we'll go with option 2. I updated the SQL, endpoint numbers, and the draw.io drawing (https://www.draw.io/#G108WMWi2-V0EOjRuKer8m0uzOu_aJK9M8) based on some conversations. Some additional work noted as TODOS. PRES_CA_CM_SCHED_STATE_20D From @fec-jli: the initial thought we may need 5 endpoints. I just put endpoints list here, after we create issue, we can put inside the tickets. Per @patphongs, use /* Option 2 */ 5 endpoints: =========================================================== 1) /presidential/contributions/by_candidate/combine state data with national data
(left side cand list, national and state wide get all candidate list) Include rounded and original totals
=========================================================== 2) /presidential/financial_summary/(right side summary; Expenditure Tab ): -- TODO: Determine financial summary fields, use readable column names. Maybe bring them all over as readable columns in case we need others later
=========================================================== 3) /presidential/contributions/by_size/(national map right side contribution size) TODO: Consider using "size" filter like /schedules/schedule_a/by_size/ instead (in addition to? ) contribution_range_id The total all contributions in the following ranges: -0 $200 and under
=========================================================== 4) /presidential/contributions/by_state/(national map circle per candidate):
=========================================================== 5) /presidential/coverage_date/(dateThrough) (DISCLOSURE.PRES_NML_FORM_3P_20D / _16) --TODO: Bring in 2016 data
=========================================================== |
What we're after:
Design endpoints - names, filters, output fields, data structure, sort capability
Let's work with front-end team and @fec-jli to see if there's any gaps in the endpoint design.
Initial design concept
see research here: https://app.zenhub.com/workspaces/website-project-559bfc62e61e8f964c1ca7de/issues/fecgov/openfec/4170#issuecomment-580795643
Within endpoints include:
Completion criteria
The text was updated successfully, but these errors were encountered: