2022-07-18 Meeting notes

 Participants

  • @Dina Meek @Julie Ma (Unlicensed) @Ron Payne @Tolbert, Nathan L @Winona Snapp-Childs @James Griffioen @John-Paul Navarro @Stephen Deems @Joseph White @Greg Dean @Rebecca Eveland

 Goals

  1. Review our group’s objective and operating principle:

Quickly reach consensus on:

website design and navigation issues to keep access.org and subdomains on track

brand design as it will apply across all tracks.

We must have representation from each track to constitute a quorum; in the absence of track representation in a meeting, Dina will email the group, asking for that track’s input by a certain date. 

If we do not reach 100% consensus, the issue will be kicked up to the EC by Dina

2. The ACO has suggested our universal navigation might include dropdowns to guide visitors to specific places on the various track sites

Thoughts?

If yes, need to provide Dina with what your dropdowns would be end of week (7/22); Dina will share with agency designing our site.

Limit of five - could expand in the future but want to keep it as streamlined as possible

 Discussion topics

Time

Item

Presenter

Notes

Time

Item

Presenter

Notes

 

Meeting Cadence

Dina Meek

  • Dina to send a Doodle poll for regular weekly meetings - now through Oct 1; possibly later



Sitemap

Dina Meek

  • John Towns is bringing the most recently proposed universal navigation to the EC for some clarifications and approvals

    • Names for “Operations/Cyberinfrastructure” and Metrics

      • Track 3 will provide functional area name during EC tomorrow. Track 4 is good with “Metrics”

    • Approval of “Portal” for the navigation to MATCH (where the login mechanism will live

      • Suggested changes to sitemap reviewed by Julie (Track 2). All approve accepting suggested changes. Julie to send sitemap updates to Dina for distribution to EC prior to tomorrow’s EC meeting.

 

Sitemap

Julie Ma

  • Prioritize Ease of use for constituents vs delineating the tracks? ie, do we name things by track acronyms or by their functions?

    • Functions will be used on “front door” ACCESS.org. Track acronyms will be introduced, if desired, at the sub-domain level.

    • Updated wireframe agreed upon:                

    • Wireframe withe My Account sub-menu items:

  • Basic Concepts for User friendly experience: minimal clicks, logical organization, minimize redundant information (especially if inconsistent)

    • Drop down on main page was agreed to by all tracks. input collection page: input asked from all groups by Friday, 22 July, 2022.

 

August 1 splashpage:

Dina Meek

Dina’s sent first draft copy to the PIs for approval. Hoping to get that through the gauntlet this week so I can get to the agency for production (they’re already working on the design).

 

Group Principles

Julie Ma

Is this working group Collaborative or prescriptive?

  • Working Group is very much collaborative.

 Action items

Add action items to close the loop on open questions or discussion topics:

  •  @Dina Meek to send a Doodle poll for regular weekly meetings - now through Oct 1; possibly later

  • @Julie Ma (Unlicensed) to send Dina proposal for sitemap update

  • @Dina Meek to share updated sitemap along with decisions made by group to John Towns for EC meeting discussion/approval Tuesday 7/19

  • ALL to fill out “input collection page” by 7/22

 Decisions

Type /decision to record the decisions you make in this meeting:

  1. Track 4 is ok with “Metrics” as their navigation name; will confirm in EC 7/19
  2. Group approved @Julie Ma (Unlicensed)'s proposed sitemap update which will be shared with EC 7/19
  3. Group agreed “Track” and track acronyms should not appear on access.org; may be introduced at the various track levels
  4. Group agreed on dropdown menus for universal navigation; will provide those suggested subnavs in the “input collection page” linked above by 7/22