2024-10-24 Meeting notes

Website Feedback

User Testing

PY3 Plan

Quarterly updates

From the EAB Meeting:

• We need to make “How to Cite ACCESS” more visible

• Landing pages are good, but people are still getting lost once they get to the individual sites

From NSF POs:

• Some pages across the web presence aren’t displaying the new top navigation

• We’re pointing to three different places when we point people to the ticketing system

do we want to do holistically as our full web presence?

• How do we want to recruit?

  • Sign up at SC?

  • Something like Allocations did: https://support.access-ci.org/announcements/opportunity-participate-access-feedback-forum ?

• Anything, other than User Testing, you think we need to build in?

  • Tagging content?

    • Measure effectiveness of the nav/landing pages

    • Analytics

  • Duplicated content

• RP page

• Glossary

• Site Map

Q to put in footer

Everyone: please check your pages

• Support has a couple pages they’re updating now

• For researcher-facing subsites, top nav isn’t necessary but the ACCESS/NSF logo must be at the top; if we want the user to go back to the service team home page, the service team should be in the logo

Ticketing - there are ongoing discussions about the “doorways” to the ticketing system. Dina and JP to bring this back to NSF PO discussions - these entryways are by design.

Small pool works well; CCEP funding (about $1k each) available as incentives - Lissie to check on what’s available

• by Personas

• Not all track reps should attend each so it’s not overwhelming for the users

• Lissie/Support can assist

• perhaps 3 of each, new vs. experienced, for each persona

• Dina to set up planning meeting with Christine and Lissie

All - for next meeting, be thinking about what we want to accomplish by April 30, 2025

JP to check RP page and update anything in Slack

Christine to set up Glossary and Site Map update pages; also, everyone run your link checkers to id broken links

Parking Lot

Tagging/Tracking/GTM/Google Analytics

Megamenus

Integrating CITAP

Allocations new site

Analytics page

Thoughts on deferring this work until after the SGX3 work?

“Get Started” Tagging

• How are people getting to the subpages?

• We need to decide what metrics we’re really interested in tracking

• Looked at tagging the dropdowns on the “about” page of “Getting Started”

• You want to tag things that are actionable by the user

Need to identify goals in order to set metric to measure those goals

• Program-wide goals might be a good place to start

Support will build for their secondary menu and we can follow that if we see a good reason for adding it to main nav

Please add to this list asynchronously and we will check it as we continue to meet

Propose we spend our next meeting reviewing how this impacts the home page’s “Get Started” work

Team agrees we should wait until we consolidate all the web feedback and bring to the EC for direction before deciding how to move forward with tagging for analytics.

Per Dina: still like the idea of organizing our future work around program goals.

Perhaps while SGX3 is doing their work (should be done early May) we can discuss what to tag, but not do any tagging yet.