/
Recommendations

Recommendations




SEARCH
Make the search box the first thing you see after clicking on the search icon in universal nav. Users consistently passed by the bot. - COMPLETED

UNIVERSAL NAVIGATION

  • Home page icon - move to left of ALLOCATIONS within the universal nav. Some users are missing the icon (obscured by Find info for you and search icon).

  • Change “Programs & Organizations” to “CI Community” (Collaborators, Community Members, SysAdmins, Support Personnel, Campus Champions, etc.)

  • Either add chevron to Find Info for You or show the dropdown upon mouseover

  • Footers

    • Update to CI Community

    • In universal footer make “contact us” bigger

    • Adjust spacing on universal footer: glossary link and other footer links blocked by QA Bot

    • Add “Report a Security Incident” to small footer links, make links alpha order

    • Small ACCESS logo at bottom left links to ACCESS home page

TBD: Should Systems Status button or RP links appear with universal nav or add to Resources page.

For All Tracks

  • Ask all sites to create breadcrumbs so people can see exactly where they are

  • In track mega footers add title so it is not confusing for user – e.g. ACCESS SUPPORT

  • Global navigation, in breadcrumbs use track name – e.g. SUPPORT


FINDING COST INFO

  • Add the “at no cost to you” language to the intro paragraph on each page such as:

    • About (main) - COMPLETED

    • Allocations Policies?

    • Events & Trainings (“Like ACCESS, trainings are at no cost to you.”)


POLICIES: CYBERSECURITY

  • NEEDS DISCUSSION: What happens to data on the systems? Is there a clear policy link for each system?

  • Operations cybersecurity page access: Cybersecurity | Operations

  • Added cybersecurity link to About

  • Add report a Security Incident to:

    • Persona quick links - COMPLETED

    • Footer

    • As a radial button on the Support Help page, opens a separate report a security incident ticket


VIDEO YEAR 4 PLAN

  • NEEDS DISCUSSION: Add video links or video embeds on key content areas - how to log in, allocations, resources, etc.

NEWS/ANNOUNCEMENTS

  • Discussion: People prefer to get updates for news/outages/opportunities/trainings emailed to them (via newsletters/affinity groups/etc.)… don’t necessarily come to the website to get this information.

TABLET/MOBILE FUNCTIONALITY

  • Discussion: Most users are on desktop. One user had trouble with some features on a tablet. Waiting for their input.

CONTENT YEAR 4 PLAN

  • NEEDS DISCUSSION for future improvements:

    • Avoid repeatable content across tracks – e.g. Get Involved, About content

    • Avoid “walls of text” create scannable text using H-tags, bullet points, etc.

    • Review global navigation


RECOMMENDATIONS BY TRACK

ALLOCATIONS CROSS-TRACK:
RESOURCE CATALOG

MY: While addressing these recommendations, I want to keep us focused on the primary purpose of the resource catalog, which is to help researchers in selecting resources.

  • Move list of RPs in the filters down as people are less likely to care about that than what the resources can do

  • Consider adding more links to this page since many users go to the Resources page to find information:

    • Changing “Browse resources” yellow button to “Search software”

      • MY: I agree that we should include a software search, but I’m not sure that I want to eliminate the “browse resources” button. The analytics data from Clarity shows that some users are clicking that button. Ideally we should integrate the software search into the catalog instead of sending users away to the SDS page, but that will take some effort.

    • Link to information for Resource Providers: https://access-ci.org/get-started/for-resource-providers/ - CG: Let’s no do this since Operations are making changes to the RP pages.

      • MY: My concern about adding RP links/information to the resource catalog is that it may confuse or distract researchers, who are the primary audience for the page. If we want to have RP-specific information included in the catalog, I think it needs to show up only when an RP user is logged into the site.

    • Link to “systems status” on this page

      • MY: Current and future system outages are already shown on the resource pages under “Announcements and Events.” I think what’s needed is an affirmative indication that everything is good in cases where there are no outage alerts.

    • Link to “credit exchange calculator: https://allocations.access-ci.org/exchange_calculator

      • MY: Like the software search above, I think it makes more sense to integrate this functionality into the catalog rather than sending users away to a separate page.

  • Make sure Resource descriptions at the top level are helpful – what is the system and what type of projects is it good for.

    • MY: I agree that some of the resource descriptions could be improved. I’m not sure who is the best person to work with the RPs on updates.

  • Add tool tip or link to understand what OnDemand means: https://access-ci.org/glossary/#OnDemand

    • MY: Adding descriptions to the filters is planned as part of the integration of Operations badges later this year.

  • On individual resource pages consider button text change from [Get Started with OOKAMI] to [Get Started] or [Get a Project/Allocation/Credits] etc.

    • MY: We need to be careful about the language here, because not all resources in the catalog are ACCESS-allocated. (For some, clicking the “Get started…” button takes you to the RP’s website.) Eventually, I’d like to have smarter behavior for the ACCESS-allocated resources that does different things depending on whether the user is logged in, has an existing project, etc.

  • DISCUSS ON 4/23 CALL NEEDS DISCUSSION: Is there other explanatory text that would be helpful with wait times section in Resources catalog? Currently reads: These metrics describe activity from ACCESS projects. Many resources have additional projects that are not part of ACCESS. – RP

    • MY: Getting users to understand the wait time metrics has been tricky. The current text is meant more as a disclaimer than an explanation. (Some RPs were concerned that it looked like their resources were not busy, when in fact, many have non-ACCESS projects that aren’t represented.)

  • Do we have copy about process if needed software is not installed on a Resource? - which RPS would install for you or let you install?

    • MY: I think this is going to be different for every RP. My suggestion would be to direct users to the resource’s user guide for instructions on bringing their own software.


ALLOCATIONS:
PROJECT TYPES

  • In project type comparison table “Supporting grant duration or 12 months” consider “12 month or (supporting) grant duration”

ALLOCATIONS:
NAVIGATION

  • Remove HOME from Allocations global navigation.

ALLOCATIONS:
POLICIES

  • Could the eligibility requirement be summed up, in a table or checklists? Hard to get info quickly

  • Clarify eligibility text for Discover, Explore related to students and staff.

  • This information gets lost for users:
    You can have financial support from any funding agency or source and still be eligible for an allocation.
    Even if you don’t have any funding, you are still eligible for an allocation. However, PIs without funding are only eligible for one allocation, while PIs with funding awards can receive as many allocations as they have awards.

  • Remove hyphen in graduate-student on Eligibility CG: This is correct: Yes, "graduate-student level" should be hyphenated when used as a compound adjective modifying a noun, as in "a graduate-student level course". 

ALLOCATIONS: YEAR 4 PLAN
CREDITS

  • NEEDS DISCUSSION: Be sure to use consistent language regarding Credits and Units throughout. If they are the same thing, only use one of those words.

  • NEEDS DISCUSSION: Provide better guidance for first time users on next steps after they receive an allocation/credit. Make it clearer how/when to exchange credits for Resources - particularly post-login

  • Provide better guidance for experienced user on how to manage a Project upgrade and remaining credits. Current language is confusing. “The initial allocation for the access credits will be half the total amount for the new opportunity, minus the amount consumed at the smaller scale.”

  • Are start up credit no longer available (like on xsede)? - CG from RP interview at SDSC, individual resources may have a “try for free” before signing up with ACCESS

METRICS: YEAR 4 PLAN
XDMOD

  • NEEDS DISCUSSION: Create more pathways to XDMoD – particularly post-login

  • Add more information/instructions on how to use this tool since it is complex for educator/grad student/researcher - CG: user tour and manual is under help

  • A lot of sysadmins/RPs use this on their phone

 

OPERATIONS:
RESOURCE PROVIDERS

  • RPs may have the perception that the site is not for them, and this may make it harder for them to find the information for them. How can we make a more findable place for RP info? Link from Resources? -CG: Operations developing new dashboard

  • RPs can use clear and concise documentation about distributing news

  • RP staff may need better ticketing documentation. If RP staff is recommended to use RP ticketing form we need to make sure they are finding it easily. - CG: Add Open RP help ticket to RP pages

  • We should make RP Slack space easier to find - CG: considering Support Community slack page

  • Simplify how an RP joins the RP Forum – is the RP Forum an Affinity Group?

  • How can we make integration roadmap less confusing, or at least guide the right audience there but not confuse new people who are still getting the basics. - CG- Operations working on dashboard

  • Improve content on the Get Started RP pages clear steps on requesting to become an RP, what happens after you create a log in

  • Note for operations to check video here to see if there's a redirect issue (1:02:02) - Lissie to clarify




SUPPORT:
RESOURCE ADVISOR

  • Very popular with users. Libraries misspelled. LF: Done

  • Results go to Operations results vs. Resources page LF: Done

SUPPORT:
SOFTWARE DOCUMENTATION SERVICE

  • When using search it is unclear you are viewing results – highlight keyword search in yellow

  • Connect this functionality to Resources


SUPPORT:
COMMUNITY

  • Should all volunteer/get involved activities happen under “Community”? Users having trouble finding volunteer/get involved activities (users may not really have the bandwidth to volunteer with ACCESS). LF: We can add a section to the Community Overview page that links to Get Involved.

  • No Educator Affinity group (Educator user would like one) - LF: I have been wanting an Educator Affinity Group, but need to find a person or people to be the group coordinator. I asked around a bit last year but didn’t find someone to Champion this group.

  • Can we improve search-ability of Affinity Groups by anticipating what keywords RPS(and others) may be searching with? LF: Support will add tags to indexing

  • Users need a clearer understanding of the different ACCESS slack channels available. Should this be a page under Support > Community > Slack Channels? LF: Are there channels beyond Internal ACCESS and RP Slack Channels?

  • NEED DISCUSSION: Add some text to differentiate skills vs interest on community personas. - Lissie to clarify LF: Will add a little explainer text: My Skills (have some expertise in) My Interests (things I would like to learn more about)

SUPPORT:
SEARCH

  • See where we can improve keywords for typical user searches. LF: We are currently analyzing
    search queries to spot trends and make improvements.


ACO:
ABOUT PAGE YEAR 4 PLAN

  • Consider changing “Acknowledging” to “Citing” if that’s the more common term. - Dina to check with her communications team

  • Should “get involved content” live in Support > Community? - Discuss with tracks, note duplicate Get Involved content with Allocations

  • NEED DISCUSSION: Should the ACO About page include information about each track, track’s won’t need an About page? - Discuss with tracks, note duplicate About pages


ACO:
GET STARTED PAGES YEAR 4 PLAN

  • FOR RPs: Implement new updated RP and Become an RP pages per Esen/Operations egokpina@iu.edu

  • Get rid of “How to get started” accordion. This is just about getting an ID. Incorporate this as a step within the “How do I integrate my resource” and then make it clear what is the next step after logging in, requesting to become an RP, open a ticket to become an RP? - work with JP to improve next steps for RPs see comment above under Operations RPs work with Esen - COMPLETED

  • FOR ALL: Consider logging in Step 3. Why log in when you don’t know about resources and the ACCESS process. Will not implement

  • FOR ALL: Move quick links to top of the page for experienced users. - Will look at changing verbiage at top of page – If you already have an account welcome back. Login or find helpful quick links below. - COMPLETED

  • Consider Research Support persona, If we are not considering a 6th persona consider adding some thing like this to the Community Persona intro “supporting other people's research” This may be addressed with the new persona name CI Community - Dina to check in with her team CI Community.

  • NEED DISCUSSION: Add video links when possible, for login example - Q to create video icon link, check in with Lissie on video learning center, who owns videos?

  • NEED DISCUSSION: Better wording (to include software, on demand, etc.) for “Are there tools available to run projects?” - work with Lizzie

  • NEED DISCUSSION: Do we want to include more Case Study Stories for a variety? Videos? More educator user stories would be helpful. - point user to news stories? work with Lizzie

  • TBD: Perhaps add Glossary links elsewhere on the site, such as in quick links on each landing page, the Get Started page. - add to quick links? - COMPLETED

  • NEED DISCUSSION: Include “how to” language on Get Started persona pages about credits – ie. “Once you've got some ACCESS Credits in hand, you can submit an exchange request from the true My Projects page” ACCESS Allocations: Exchange Calculator - work with Allocations


INFOGRAPHICS FOR ACCESS YEAR 4 PLAN

NEED DISCUSSION:

  • Consider infographics for users to more easily digest ACCESS processes

    • From login to get a resource?

ACCOUNTS YEAR 4 PLAN