Page Comparison

...

• Greg Dean John-Paul Navarro Nathan Tolbert Dina Meek

• Website Focus Group

• (intro about roadmap hopes, efforts)

• Ask WG what questions they want to ask the group about their landing page

• Nathan - We have a few new interfaces that we want to suggest might belong in the "my access" dropdown in the header, across all of access, so we'd like to propose those to the group.

  • Add two items to My ACCESS dropdown (you have to login to see the “My ACCESS menu)

    • Share with ORCID

    • My Publications

Andrew said they are changing My Engagements to link to Community Persona

• Style Guide - https://client.qltd.com/access/index.html

  • Per JP, there are things the header/footer team decided that are missing - please identify

  • January 18 meeting notes

  • Dina met with the agency and they are at a loss because they believe the guidance is in the Style Guides as they exist today

    • If you find you cannot finalize your site because something is missing, please send me an email with the exact thing you’re looking for and not finding and I will share with the agency; they may be at our next meeting.

    • We need a definitive list of what our menu options should be

      • We need a document created - we can start from scratch

        • Will also show links for the footers

      • We can pin it to the top of our channel

      • Nathan will do first draft; asks for everyone to contribute (ACO may not bcs it won’t have the login)

      • Doc will live in the WG Google Drive

• Analytics 

  • Everyone should have access to the Google Analytics shared dashboard

    • I think we still need to add XDmoD

      • They already use Google Analytics and not sure if they can also run Google Tag Manager

      • JP wanted documentation on:

        • Service Description

        • Where will the documentation live

        • Ticketing - what queue and how is that processed

        • Outages - how might we communicate that

I’m thinking that since this is a Google product the above isn’t really applicable.

Per JP - he means documentation for how this will be used by ACCESS so…

Let’s add to the existing document we have that explains

...

Who uses it

...

How it’s used

...

Universal footer navigation - all sites should point to:

• Updated privacy policy: https://access-ci.org/privacy-policy/ 

• Updated acceptable use: https://access-ci.org/acceptable-use/ 

• Code of Conduct: this is being reviewed by ACO Community Outreach per request by EC

  • https://access-ci.org/access-code-of-conduct/

RP Page - https://access.qltdclient.com/resource-providers/

...

I presented the RP page last week to the RP Forum

There was a fair amount of feedback

...

Some on the language being to high level and generic

...

Also about how many clicks it takes people to get to where they need to go when looking for resources

...

• Other Page Updates

  • ACO will be adding to our News page a link to a subpage with info on how to submit events, trainings, news items, etc.

    • This has been a joint project between members of ACO, Support and Allocations

    • We thought we might add a section about Operations news, per JP’s suggestion; however, as this is more external facing (soliciting news from outside ACCESS and pointing people to news) we think we’re already guiding everyone to Ops news (it’s all pointing to Support’s site anyway)

    • Change headline to just Share Your News

  • Also planning pages for:

    • Getting involved with ACCESS

    • Collaborating with ACCESS

...