-
Notifications
You must be signed in to change notification settings - Fork 4
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
System to direct user to fec.gov (Form 1) to edit Committee Account data #130
Comments
@lbeaufort @RyanLanz This is the story for making sure users have the link to their committee's most recent Form 1 as well as the webform to update the Form 1. Can you provide us the links and/or link logic to use? |
Aurelia:
Here are the links/explanation, although Laura can probably provide additional information for the most recent F1.
Webform Form 1: https://webforms.fec.gov/webforms/form1/index.htm
Most Recent Form 1: https://docquery.fec.gov/pdf/539/202110149467253539/202110149467253539.pdf - This link changes for each committee. The numbers in the link are what we call an image number and they are unique for each filing. My assumption is that we have an API that pulls the most recent Form 1, but Laura can probably provide greater insight on that than I can. We display the most recent F1 on a committee's profile page (example: https://www.fec.gov/data/committee/C00001313/?tab=about-committee).
|
Wireframe finalized and added. removing UX/UI attention needed. |
Comments from 3/29/22 Sprint Planning: Options for additional form 1 link:
|
Refinement Meeting 3/30/22: Because we are not yet pulling committee data into FECFile Online, to test, we will need to manually create a Committee Account with a real Committee ID for testing. See example from Ryan above. |
@lbeaufort if memory serves me, the efiling endpoint only has the most recent four months of data. If a committee's most recent F1 is older than that, how do we provide a link to it? Do we need need a way to check both the efiling and processed data endpoints for the most recent F1. Do we need to consider changing how we "prune" the efiling endpoint? |
Passes code review. Sending to QA. |
Verified when selecting "Update committee info using Form 1" the following screen appears: Verified when selecting "View full committee info from Form 1" the following pdf of the most recent F1 filing is displayed. Example using committee (C00277608) link https://docquery.fec.gov/pdf/220/12030992220/12030992220.pdf QA review completed. Moved to Stage Ready. |
Business Reason
As a Committee Administrator, I will see instructions on the Committee Account page telling me to access fec.gov and resubmit a Form 1 to update any Committee Account information so that I can edit the information as needed if it changes.
Acceptance Criteria
Given a Committee Administrator is on the Committee Account page (Profile > Account)
Then I will see instructions directing me to resubmit Form 1 through FEC if edits are needed
And a link to my committee's most recently submitted Form 1
And each link will open a new tab when clicked.
QA Notes
Note: Remove numerous "Edit" buttons.
For example: “You can view your committee's most recent Form 1 here: (link to most recent F1 on fec.gov for that committee). You can update your committee’s official information disclosed on Form 1 here. (Link: https://webforms.fec.gov/webforms/form1/index.htm ).”
Dev Notes:
form_type
starts with F1. We can probably wait until we move this to the API. We can't just use efiling endpoint because it's only 3-4 months of dataDEV Notes
null
Design
null
See full ticket and images here: FECFILE-1289
The text was updated successfully, but these errors were encountered: