2023-03-01 Meeting notes

Owned by Dina Meek
Last updated: Mar 07, 2023
3 min read

 Date

Mar 1, 2023

 Participants

  • @Dina Meek @Greg Dean @John-Paul Navarro @Tolbert, Nathan L @Andrew Pasquale Qltd (Christine, Emily, Matt)

  • Style Guide - from the agency

  • Analytics 

    • Once the new dashboard is set up we will make sure that all the folks have access:

      Allocations: Rob Light/Nathan Silver

      Support: Andrew Pasquale

      Operations: JP

      Metrics/xmod: Ryan Rathsam

      access-ci.org: Dina and Ron (and at the moment Q LTD team)

  • Universal footer navigation

    • Privacy Policy

    • Conduct (J. Towns working on)

    • Acceptable Use (created by the IAM group)

    • Dina to bring Support's Privacy, Code of Conduct to ACO to determine if we can use this, make adjustments etc.

      • Then bring back to the group to make sure we all have the same verbiage/links in our footers

  • Resource Provider Page - JP, Julie, Greg, Nathan, ACO - Ron/Q

    • There will be a subgroup to put together a decision tree to help new researchers decide which resources they need

      • Support

      • Allocations

      • Operations

    • Ruth and Tom Maiden - sources of truth for RP logos/page

    • Dina to get RP copy into the drive and share link with the team asap

      • Team to review RP copy by 3/8

    • Q did a very high-level layout based on JP’s team’s outline

    • We need to run by a small focus group of RPs before we do much more

      • We need to determine what makes the most sense to show on the page - the Resource Provider names or the actual resources (Bridges) page

      • We may need to link off to a subdomain that has a list (dynamic pulling from dbase) of all the resources

    • Draft copy

      • Group discussed purpose of page

        • we all agree that this is to make the RPs more visible

        • The questions at the bottom are how people take action

          • The various service areas need to help us determine what the questions are and what the links are

        • The Resource Types will be done away with and that info will be brought up into both the intro (explaining the different types of resource) and then fleshing that out a bit under the blurb that will come under whatever the “levels” titles becomes

          • Ron has info on how “Levels” are now described within ACCESS

      • Vet through RP forum

        • NEXT STEPS: ACO will share updated draft copy based on above with this group for feedback before giving to Q to re-lay out

        • Once team is satisfied with copy and layout, Dina and Ron will bring to the RP Forum small focus group

For future:

  • User Interface

    • Refinements focusing especially on:

    • Universal navigation dropdown (Login or My ACCESS TBD for future)

      • Do we want dropdowns

        • open on hover? open on click?

        • what do underlines mean? Active?

      • Q says its most simple to use “Login” on all the sites in the Univ nav bar

      • All sites aren’t handling login the same;

      • where we need all sites to go is to CiLogon

      • We will defer this piece - for the ACO site - until we’ve got style guide finished

    • Subdomain navigation and drop downs

      • Subdomain footer refinements

    • Breadcrumbs

      • “Home” means different things

      • So replace that in breadcrumbs with subdomain name

      • “Home/Tools” would change, for ex, to “Support/Tools”

    • Would like to add a style - like the inpage navigation (see “Tools” in Q’s layout) - for inpage content boxes

  • And…

    • Adding blurb to Contact page with link to ticketing system for allocated users

      • Dina shared text with Q 2/8

    • Universal navigation, dropdown menu for “About”, includes file distribution to all
      subdomains via GitHub

      • Determine if there should be dropdowns

 Action items

  • @Dina Meek and @Ron Payne to meet to determine best way to organize decisions/actions for group to follow

  • Q would share XD files with the team

  • Dina to share RP page copy with team by 3/8

  • Julie to form subgroup to create decision tree for new users to determine where they need to go from RP page: Allocations, Support, Operations (Metrics?)

 Decisions

Style Guide - Team decided we would all now work to implement the styles and then determine if anything more was needed.

RP Page - Team decided purpose of the page is to make the RPs more visible; links will give people a path for further action.