Post contact lists for NSACs, KSMALs to static site

[jadudm]

Nov 2024 Update

• As an auditor/grantee, I need to see a contact list of:
  • cognizant and oversight agency contacts, so that I know who to contact for technical audit advice and liaison assistance to auditees and auditors, extensions, and questions about indirect costs.
  • National Single Audit Coordinators (NSACs) for technical audit questions.
  • Key Management Single Audit Liaisons (KSMALs) for questions about administrative requirements applicable to agency programs.
  • Program contacts for program-specific questions.

Links

• Figma Design

Tasks

Beta Give feedback

1. Create new Contact page with a list of NSACs and KSAMLs and a list of cognizant agency contacts
2. Review designs with Leigh, Dan, James M for copy, and James P for dev
3. Develop Contact page with contact lists on static site #4442
   eng +1
   
4. Remove Federal agency program contacts page from website

Archive

Aug 28, 2024

At a glance

In order to get answers to questions about my audit
as a submitter or member of the FAC
I want an easy reference to NSACs, KSMALs, and program contacts.

Acceptance criteria

In keeping with M-22-23 (Delivering a Digital-First Digital Experience, PDF), we want to provide critical information to our users in an accessible, HTML form wherever possible. More specifically...

Shepherd

• Design shepherd: @Leighdiddy

Background

A branch that makes a start on this exists in our static site repository.

https://github.com/GSA-TTS/FAC-transition-site/tree/jadudm/contacts-helpdesk/src

In the omb directory...

• nsacs.md provides the NSAC list
• ksamls (WHICH IS NAMED INCORRECTLY---OOPS) provides the KSMALs list
• program-contacts provides the program contact information.

All of these are data files in the repository.

https://github.com/GSA-TTS/FAC-transition-site/tree/jadudm/contacts-helpdesk/src/_data/omb

• nsacs.yaml -- YAML was used because the information was variable enough, as provided by OMB in the supplement, that variable fields (and variable rendering) were required to capture all of the information. It might be able to be normalized into CSV. 🤷 I chose to represent the information faithfully as-is.
• ksamls.csv was clean enough to represent as a CSV.
• program-contacts.yaml is a complex mess. That data is not well organized. I created a repeatable YAML structure to encode the data, and used & references where appropriate to avoid repeating data entry.
• We have no starting point (yet) for the extensions list; it must be provided by OMB.

Styling/design work is needed for the rendered pages, but much of the data we need is present. 100% of the NSAC and KSMAL data is present; it would represent a good "first step." The programmatic data is needed, but requires more data entry work (the hard way---manually).

Security Considerations

Required per CM-4.

No known security concerns; this is static content for the static website.

[Leighdiddy]

@analynd as we discussed today: Let's define what we are sharing in the short term (PDF pg. 2048-2074 from the UG), where it lives (helpdesk, by request for feds only), and how + where are we sharing instructions for users. Next steps: Draft instructions for how to request the contact PDF, include explanation that it's for feds only. Determine where we share this on the site, mock it up in figma!

[Leighdiddy]

Work is currently blocked pending clarification from OMB, call scheduled this friday.

There are now two contact lists, a new cog contact list from OMB (@danswick has it) and the existing NSAC/KSAML from UG (see attached). They can both be distributed following the same method. Waiting on: Explanation of when to contact your cog vs. nsac/ksaml, explicit permission to share contact lists publicly
Agency_contacts.pdf

[analynd]

Synced with Leigh to update task list:

Notes from convo (reframing user stories so I can better understand context):

• Create new Contact page under "Policy & Compliance" tab with the two lists
• As a user, I need to see a contact list of cognizant agency contacts, so that I know who to contact in regards to my question about extensions.
• As a user, I need to see a contact list of NSACs & KSAMLs, so that I know who to go to for questions about my audit.
  ("NSACs can answer technical audit questions, KSMALs, can answer questions related to the administrative requirements applicable to an agency program(s), and program contacts can answer program specific questions.")
• Remove Federal agency program contacts page from website

[analynd]

Design of new Contact page is ready for review!

Routing to several people for review, please mark complete here and unassign this ticket to yourself when done:

• - @Leighdiddy @danswick I know the ask was to just post the 2 contact lists, but what do yall think about creating a new Contact page to replace the “Helpdesk” link in the Nav? More info in Figma design, but gist is consolidating ALL of the contact resources for our users in one place on the site instead of digging around and guessing where to go for various info.
• - @James-Paul-Mason Can you please help me by finessing the copy in the designs? Thank you!
• - @jperson1 Can you please review the overall design from a dev POV? I had a comment in there about tables, too. Thanks!

[James-Paul-Mason]

@analynd I should be able to get this done tomorrow! Quick question: would you like comments directly in the Figma file? I assume yes, but just wanted to double check.

[analynd]

@analynd I should be able to get this done tomorrow! Quick question: would you like comments directly in the Figma file? I assume yes, but just wanted to double check.

@James-Paul-Mason Yes, commenting in Figma and tagging my email would be perfect. Thank you so much!

[danswick]

Done!