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

Improve access to AO comment information #5355

Closed
2 of 3 tasks
Tracked by #140
JonellaCulmer opened this issue Aug 3, 2022 · 9 comments
Closed
2 of 3 tasks
Tracked by #140

Improve access to AO comment information #5355

JonellaCulmer opened this issue Aug 3, 2022 · 9 comments
Assignees
@JonellaCulmer
Milestone
Sprint 19.1

Comments

@JonellaCulmer
Copy link
Contributor

JonellaCulmer commented Aug 3, 2022 •
edited
Loading

What we're after:
Improve access to AOR comment information. Several comments (list to follow) from customers interested in providing comments on pending AOs are having trouble locating information to make comments. Some have even submitted their comments via the feedback box, which is not a valid method - and so these voices are potentially going unheard.

Related issues

Considerations:

Completion criteria

  • Recommendations to improve access to AO comment information are made
  • Recommendations are approved
  • Implement changes, if possible, open up followup tickets for any front-end or back-end work
@JonellaCulmer JonellaCulmer added this to the PI 18 innovation milestone Aug 3, 2022
@JonellaCulmer JonellaCulmer self-assigned this Aug 3, 2022
@JonellaCulmer
Copy link
Contributor Author

JonellaCulmer commented Aug 4, 2022 •
edited
Loading

@AmyKort @PaulClark2 @patphongs Below are some thoughts compiled by me and @kathycarothers on how to improve access to the AO comment information, both short and long term. Please let us know if you have any questions/concerns/suggestions or would you like to meet to discuss further.

Short-term recommendations for improvements:

Page improvements:

Need to confirm with OGC:

  • Need to confirm with OGC about the use of fax and hand delivery for AOR and draft AO comments, is that still accurate? If so, that information should be conveyed in the AOR comment section.
  • Need to confirm with OGC, do we need to update the language to say "ten calendar days" for AOR comments?

Need to confirm with devs:

  • Need to speak with devs about automating the AOR comment due date and/or making changes to the system where dates are entered by Jason to add AOR comment due date, and future AO draft comment due dates.

Long-term recommendations:

  • Build a form for customers to submit comments directly through the website. Need to determine what our limitations are with this scenario. I.e. privacy
  • Include links to the new form on individual AO pages.

@PaulClark2
Copy link
Contributor

If we were to implement a form, I think we'd need to include an option for commenters to upload a document. See for example the two comments submitted on 07/12/2022 and the comment submitted on 08/04/2022 related to AO 2022-14.

Would we be adding end of comment period and how to comment to the "pending AO" page? https://www.fec.gov/data/legal/advisory-opinions/. The current button "learn how to comment" is essentially useless.
image

@JonellaCulmer
Copy link
Contributor Author

@PaulClark2 Yes, I agree. That button is currently useless until we can get an anchor link working to that specific section.

I really like the idea of adding the AOR comment due date and potentially a draft document due date on the pending AO section.

I'll eventually open a separate ticket for an AO comment form.

@JonellaCulmer JonellaCulmer mentioned this issue Aug 16, 2022
Open
2 tasks
@JonellaCulmer
Copy link
Contributor Author

@johnnyporkchops @patphongs @rfultz A couple questions for you all:

  • Any issues with fixing an anchor link on the AO page to the AO process page? Right now it takes you to the top of the page instead of the specific section.
    Refer to this comment for more information: Improve access to AO comment information  #5355 (comment)
  • Are we able to automate AOR comment and draft AO comment due dates appearing under pending AOs on the AO page and on individual canonical pages?
  • If we're not able to automate the due dates on individual canonical pages, can we automate a link to the comment section? For example: on all pending AO canonical pages, show a link to the comment section, once it is no longer pending, remove that link to the comment section.

If you have any questions, please let me and @kathycarothers know. We can set up a call.

Once we have these details ironed out, we can reach out to the policy division for their thoughts.

@johnnyporkchops
Copy link
Contributor

johnnyporkchops commented Aug 18, 2022 •
edited
Loading

@JonellaCulmer, @kathycarothers The anchor link would actually be https://www.fec.gov/legal-resources/advisory-opinions-process/#commenting-on-advisory-opinion-requests
....not much of a "vanity" URL, but it works. The only way I can think if to fix that is to stick an html field above each one with the proper anchor link: <a id="commenting"></a>. I think I have seen content team resort to using html blocks like this before. Not ideal, but also not the end of the world.

I don't think we could also reditect /#commenting -to- /#commenting-on-advisory-opinion-requests because we can't redirect anchor links, but @dorothyyeager or @patphongs could correct me on that.

@dorothyyeager
Copy link
Contributor

dorothyyeager commented Aug 19, 2022 via email

@johnnyporkchops
Copy link
Contributor

johnnyporkchops commented Aug 29, 2022 •
edited
Loading

Based on pairing with @patphongs and @JonellaCulmer , we determined we can display the "Comments due...." text from the document_description field for each pending AO.

Questions to clarify:

  • What do we do when there are two separate documents indicating comment due date.
    EXAMPLE: AO number 2022-12 has two documents indicating same due date: Agenda Document No. 22-36-A and Agenda Document No. 22-36-B. Do show both? (data for 2022-12)
  • Are we linking to the due-date docs or just displaying the due date?

@JonellaCulmer
Copy link
Contributor Author

JonellaCulmer commented Aug 29, 2022 •
edited by johnnyporkchops
Loading

@johnnyporkchops Yes, we need to show both/all instances of documents with due dates. What do you mean by due-date docs? The document that the public can comment on, or the wagtail pages with instructions on how to comment?
@johnnyporkchops replied: Thanks for clarification @JonellaCulmer , I meant the document that the public can comment on.

This was referenced Aug 30, 2022
Closed
Closed
@JonellaCulmer
Copy link
Contributor Author

Closing in favor of followup design and implementation work:

@patphongs patphongs mentioned this issue Feb 29, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JonellaCulmer JonellaCulmer

Labels
None yet
Projects
None yet
Milestone
Sprint 19.1
Development

No branches or pull requests
4 participants
@johnnyporkchops @PaulClark2 @dorothyyeager @JonellaCulmer