Versions Compared

Old Version 2

changes.mady.by.user Andrew Pasquale

Saved on

compared with

New Version Current

changes.mady.by.user Dina Meek

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

Owner

Topic

Discussion/Update

Actions

Dina

Dina

Dina/Q

All

All

All

Andrew?

NSF Brand Changes

Charter

Resource Provider Page

Tagging/Tracking/GTM/Google Analytics

Integrating CITAP

SC23 Support Feedback Forums

Recommender / Discovery Systems

Will affect headers and footer

Shawn Strande is OK with being our EC sponsor

Update on changes

Andrew will check who has access to Clarity; everyone send Andrew the emails you want associated with the tools in Slack

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

Questions:

  • where does this make the most sense?

  • how do we make this work across the board?

  • https://webflow.com/blog/mega-menu-examples

  • Glossary might be good for use across the sites; one primary glossary

  • How do we make it easier to find the Trainings? People not finding in the hamburger in user testing

  • What about a sitemap?

It would be helpful to have a page describing the recommender systems, the differences between them, and who they are most likely to be helpful for.

  • resource advisor is one for newer users

  • allocations one (filter)

  • Operations has a chatbot

  • Metrics is also developing a tool

  • various tools like this in development

  • Software discovery tool (all RPs will have to install it)

ACO and Q working together to update header and footer; all sites will have to update too; we’ll put logos, etc. in Github

With Shawn for review before he, as our sponsor, brings to the EC

Nathan said we could possibly do something with APIs to automatically update, but work

Could glossary go in the footer when we update the footers

Nathan said we could possibly do something with APIs to automatically update, but work

Per Lissie, at this point they all have their own use cases; in the future how can we help the user know which one to use when

  • Dina to suggest to ACO organizing next quarterly meeting that we have a breakout session to discuss best uses and how to organize info to help user understand what to use (need buyin from leadership)

  • short-term solution would be for us (this team) to come up with guidance for the user

Review Decision Tracker

✅ Action items

  • Tolbert, Nathan L to run dropping “My” from “My Allocations” in post-login menu (team was concerned it would be confusing, but worth a try) (approved by allocations team)

  • Dina Meek Code of Conduct - Dina working on reviewing some discrepancies.

  • All remove intermediate log on pages so logging in takes visitor directly to CILogon page

  • All change Hex Value per 7/19 notes (in GitHub - noted at top)

  • Icicle video - Support might be able to create something along these lines - but perhaps next phase of “How to ACCESS” - and/or help set up video templates for researchers who want to share how ACCESS assisted with their research

...