Khalilah Gambrell
June 26, 2019
June 2019 User Research Findings
| www.folio.org
1
Overview
| www.folio.org
2
Insights from user research survey
| www.folio.org
3
Key findings
| www.folio.org
4
Scanability: Color contrast and text size
Respondents’ comments
“making sure there is plenty of contrast for those with poor vision and making sure that there are visual/colored cues instead of a screen full of black, white, and grey.”
“I think the type in general is too small and too light for an aging population.”
Recommendations: Implement color contrast and text size changes as outlined in revised UI designs as shown on next slide. Ensure updates are WCAG 2.1 AA compliant.
| www.folio.org
5
Scanability: Improved Color Contrast UI redesign layouts favored by survey respondents
Results List
Detail Record
| www.folio.org
6
Scanability: Three/Four Pane Layout
Respondents’ comments
“most of the results of a search are squeezed into the far right hand third (or quarter) of the screen. I find this extremely frustrating.”
“Currently, I see final results on the very far-right portion of the screen, which is maddening. It requires a lot of scrolling, which means that much of the information at the top of the column gets hidden as you scroll down. I know it's important to be able to see the hierarchy of what you selected, but having the hierarchical selections take up full columns of space makes no sense at all.”
Recommendations: Revise UI to support more working space for a detail record. And ensure design and development support working with multiple records across multiple screens. Implement changes to expand/collapse search pane based on survey results.
| www.folio.org
7
Search Pane Expand/Collapse function: Revised UI design favored by survey respondents
Search pane collapsed
Search pane expanded
| www.folio.org
8
Main toolbar navigation
Recommendations: 1.)Provide libraries details on setting up main toolbar – app order. 2.) Revise current app order requirements to prevent same apps displayed on the toolbar from appearing on the apps dropdown. 3.) User must easily return to an app's default landing page
| www.folio.org
9
Main Toolbar Navigation: Revised UI design layouts favored by survey respondents
Design 2
Design 1
| www.folio.org
10
Detail Record: Actions dropdown UI redesign layouts favored by survey respondents
| www.folio.org
11
Detail Record
Respondents’ comments
“Now it is to many fields on different pages. Fields that we don´t use. It should be so clean and simple that everyone understands how to use it.”
“Also, if a field is required when creating a new record, consider having the accordion in which that field is located, open automatically. We're forcing extra clicks to find a field that is required to complete which will likely cause frustration.”
Recommendations: Implement layout changes based on survey results. UI design and POs define rules for fields and accordions (including placement/components to use). POs evaluate app’s field and accordions. UI should better indicate if accordions contain no information when collapsed and expanded (i.e. follow the Users app pattern).
| www.folio.org
12
Detail Record: Save/Close buttons UI redesign layout favored by survey respondents
| www.folio.org
13
FOLIO Platform: What else do respondents want?
| www.folio.org
14
Insights from Inventory app – Instance record
| www.folio.org
15
Key findings � Instance record
Instance accordions: respondents want title data (64.7%) displayed first by an overwhelming number. Administrative data (11.8%) was second.
What else do users want to see at the top of the instance record?
Provide me item info and tell me if the record has been suppressed
“For circulation and public services staff, the item information is what they will go to almost all of the time, and it needs to be easy to get to.”
“To optimize the view to get a quick understanding of the instance and our holdings including status and requests, when working in the information desk.”
“I like to see if the record is suppressed or not along with date last modified.”
| www.folio.org
16
Key findings � Instance record cont'd
Accordion grouping of fields align with respondents’ expectations!
Only a few fields did not have a clear accordion grouping: Instance HRID, statistical code, system control number, mode of issuance, instance status term
The following fields/values were not well understood by respondents: ASIN, Instance HRID, UkMac, StEdNL, BNB, CODEN, ASIN
| www.folio.org
17
Key findings � Instance record
Respondents’ thoughts about the instance record cont’d
Easier access to item information
“... Circ staff need a different way to get to the item record that isn't nearly so difficult to get to.
“…It is challenging that you can't copy the item barcode easily from the holdings accordion - say, for example, if you're trying to troubleshoot items that may have been misbarcoded, or you want to take that barcode and use it another way (say, an in-app report in requests.)”
Frustration with empty accordions and field values
“Accordion titles that show up even when there is no content in it is problematic….I can understand them being in the edit view, but not in the simple display view…You end up looking at a thing that just looks like it has holes and tons of wasted space.”
“…Fields that are not in use locally should be suppressed from view as well. Lots of empty labels take up screen real estate and the display is not optimized to draw the eye towards the fields that are populated with information.
| www.folio.org
18
Key findings � Instance record cont'd
Respondents’ thoughts about the instance record cont’d
Instance record and MARC
Streamline Administrative data display
| www.folio.org
19
Instance Record | Short term Recommendations
| www.folio.org
20
Instance Record | Short term Recommendations cont’d
| www.folio.org
21
Instance Record | Long term recommendations
| www.folio.org
22
Next Steps
| www.folio.org
23
Questions?
| www.folio.org
24