2022-09-07 Meeting notes: Implementers topics: UX/UI

Date

07 Sep 2022

Housekeeping

• Martina Schildt on vacation Sep 8th - 23rd
• next meetings: Sep 12th & 21st - possible topics
  • Khalilah Gambrell to present feedback from WOLFcon meeting → Sep 2st
  • Sep 12th is cancelled
  • Proposal by Owen Stephens for October:
    • UX patterns for common cross-app tasks (e.g. would it be useful to have a UX for a 'quick add' task that could be used in different contexts when you need to create something in another app). I think it would be good to have UX specialists (Kimie, Gill) present for this, and possibly also some Stripes devs (e.g. John C/Zak)
    • Use of shortcut keys and macros for more effective cross-app working  - it also be good to have UX and Stripes/dev knowledge for this discussion I think. I know @Laura (she/they) uses macros so might have insights into the potential for cross-app working
    • Potential for external 'workflow' solutions for cross-app interactions
      • I think 'workflow' is a dangerous term here - in this context it's more about automation than user workflows, although I think there is overlap
      • I was particularly struck by the solution in production at TAMU (Jeremy Huff and Sebastian Hammer presented, the recording is at https://prod-zoom-recordings-openlibraryfoundation-org.s3.amazonaws.com/50dc6c87-3912-43fa-8287-56ec73b12bbb%2Fshared_screen_with_speaker_view%28CC%29.mp4 starting at 3 hrs, 14 min) - I think getting someone from TAMU to talk about how this is used would be v interesting
      • There was also a presentation on the use of a tool called Airflow at Stanford for "bibliographic workflow" but I've not watched that yet so not 100% sure if it is completely applicable - I think the core use case there was systems migration but it may go beyond that

Discussion items

1. Review mockups related to long lists/data density (Khalilah Gambrell) - UX-492 - Getting issue details... STATUS

2. Continue: Implementers topics | Cross-app: UX/UI

   • Modals or other popups need to move–should not be fixed in place on the screen
   • Warning Modals needed when deleting any record in any App when it is the source of truth for other records
   • Wildcards (truncation marks) need to be standardized across all Apps
   • How Dates are formatted and entered
   • Spaces handling
   • Possible: Look-up functionality across apps

Minutes

Review mockups related to long lists/data density (Khalilah Gambrell) - UX-492 - Getting issue details... STATUS

• Slide deck:
• UX design (user story) : UX-492 - Getting issue details... STATUS
• Khalilah brainstormed on feedback from App Interaction SIG and discussed ideas with Kimie and John
• Maura: Can we have first and second sort implemented?
• Zak: Search and sort supports that automatically (needs indicator)
• Kimie in chat: I didn't include that concept in these mocks - didn’t realize that was desired so thanks for mentioning

• for lists, sort is a way to find what users are looking for

• another way: provide search and filter within lists
• search within searches in the same way as eholdings app in search and filter pane
• Zak: had different expectations on behaviour - did not expect backend request
• search within based on what is in the table or search in the complete list
• when searching user wants to search through the complete list; for display, paging is fine though 

• paging makes lists easier to scan through (for display)

• searching everything seems the best approach
• please take a look at the rest of the slide deck

Next steps

• Khalilah will share the request for use cases in App Interaction Slack channel
• Conveners and POs will take questions to their SIGs
• Use cases will be listed on a Confluence page

Chat

18:02:56 Von  Dung-Lan Chen  an  Alle:
    Enjoy your well-deserved vacation, Martina!!
18:10:19 Von  Charlotte Whitt  an  Alle:
    + 1 Maura
18:10:20 Von  Kimie Matsudo Kester  an  Alle:
    That concept is not included
18:10:34 Von  Dung-Lan Chen  an  Alle:
    +1 Maura
18:11:08 Von  Kristin Martin  an  Alle:
    You can export out results for more complex needs.
18:11:27 Von  Kimie Matsudo Kester  an  Alle:
    I didn't include that concept in these mocks - didn’t realize that was desired so thanks for mentioning
18:12:24 Von  Khalilah  an  Alle:
    I agree. Good to know.
18:14:13 Von  Charlotte Whitt  an  Alle:
    I like the icons, Kimie. I clearly see that Last updated is what is sorted on. Maybe a number badge, can illustrate the primary and secondary sort
18:15:00 Von  Gill Osguthorpe  an  Alle:
    I'm here :) This is a great improvement, really like this.
18:16:14 Von  Khalilah  an  Alle:
    Slide deck: https://docs.google.com/presentation/d/1FmSmyVH71wuvaXmQV0gu8B0zKMNm6U_h-ozegh-7-vU/edit#slide=id.g116f1226fe9_1_104
18:16:44 Von  Khalilah  an  Alle:
    UX design (user story) : https://folio-org.atlassian.net/browse/UX-492
18:21:29 Von  Martina Schildt | VZG  an  Alle:
    I see you Zak
18:21:44 Von  Dung-Lan Chen  an  Alle:
    Is changing column display an option in the previous Orders MCL screen, ex. to display "vendor name" instead of "vendor code?"
18:24:55 Von  Sara Colglazier (MHC/5C)  an  Alle:
    Is the Search here only for Expected pieces or for Expected & Received? And I would need it to be for ALL Expected Pieces in the context of this record, and not just for the Pieces being displayed.
18:26:11 Von  Kimie Matsudo Kester  an  Alle:
    Received is its own accordion and would have its own filter box I think
18:26:36 Von  Sara Colglazier (MHC/5C)  an  Alle:
    Ok, thanks, Kimie
18:27:21 Von  Charlotte Whitt  an  Alle:
    Okay, sounds good Zak. Then I’m not worried
18:27:47 Von  Sara Colglazier (MHC/5C)  an  Alle:
    Yes
18:27:54 Von  Charlotte Whitt  an  Alle:
    Yes
18:30:30 Von  Dung-Lan Chen  an  Alle:
    So we can search for a particular issue to see if it was received instead of going up and down the list to look for it, correct?
18:32:19 Von  Dennis Bridges  an  Alle:
    I believe there is still a limit here but it is 3000 or 5000
18:33:02 Von  Dennis Bridges  an  Alle:
    This was based on feedback from users regarding how many of these types of record you might have after 10 years.
18:33:34 Von  Sara Colglazier (MHC/5C)  an  Alle:
    Can we get this for Items in Inventory as well? Is that being suggested to come?
18:33:57 Von  Charlotte Whitt  an  Alle:
    Yes, right now we have paging on items in Inventory, Sara
18:34:12 Von  Charlotte Whitt  an  Alle:
    But it would be great to get the filter/search option too
18:36:49 Von  Maura Byrne  an  Alle:
    +1 Kalilah
18:36:57 Von  Dennis Bridges  an  Alle:
    Yes, we tested with 3000 but there was some concern that if we allowed 10000 it may cause major issues.
18:37:13 Von  Sara Colglazier (MHC/5C)  an  Alle:
    Yes that would be wonderful/super helpful, Charlotte
18:38:00 Von  Charlotte Whitt  an  Alle:
    A limit on 3000 can be really problematic
18:38:27 Von  Charlotte Whitt  an  Alle:
    E.g. has uChicago an instance with 15000+ items
18:38:35 Von  Charlotte Whitt  an  Alle:
    Let me find it i MG bf
18:39:00 Von  Khalilah  an  Alle:
    This is where we need to talk with users to understand their expectations and then figure out a good UX to account for common and edge use cases.
18:40:39 Von  Charlotte Whitt  an  Alle:
    https://bugfest-mg.int.aws.folio.org/inventory/view/2e93db10-f5ce-4e64-8ae5-4a8ac489e5dd?qindex=hrid&query=ho126544&segment=holdings&sort=title
18:41:30 Von  Charlotte Whitt  an  Alle:
    Search and filter across these 16000+ items would be a great UX experience
18:42:39 Von  Charlotte Whitt  an  Alle:
    Splitting up ”Briefs and records of the U.S. Supreme Court.” technical in 6 different instances would be a bad UX experience
18:42:50 Von  Sara Colglazier (MHC/5C)  an  Alle:
    If I uncheck any of the Show Columns, so those are not showing, will they still be searched on and retrieved on?
18:44:04 Von  Dennis Bridges  an  Alle:
    I think it is really critical to acknowledge that this is a filter. You are not retrieving additional things, which might be considered a search.
18:44:20 Von  Laura Daniels  an  Alle:
    +1 to Sara's question and to Charlotte's point about large numbers of items
18:45:02 Von  Owen Stephens  an  Alle:
    My point is that we have both situations and the user experience should be the same in both cases because they don't care and shouldn't care about how it works
18:45:11 Von  Khalilah  an  Alle:
    +1
18:45:13 Von  Laura Daniels  an  Alle:
    I would expect the filter to be across all indexed elements, whether I was viewing them or not
18:46:32 Von  Dennis Bridges  an  Alle:
    Note, there is placeholder text that appears in this field. The text is “filter”.
18:46:49 Von  Sara Colglazier (MHC/5C)  an  Alle:
    Yes & No to kg
18:47:05 Von  Laura Daniels  an  Alle:
    Yes, this pattern meets my expectations/needs
18:47:31 Von  Dung-Lan Chen  an  Alle:
    To Sara's question, I think you'll need to have one filter chosen to render results of the term entered in the box (currently 2020 Electronic)?!
18:48:41 Von  Kristin Martin  an  Alle:
    Maybe that's where we could provide an export.
18:49:07 Von  Charlotte Whitt  an  Alle:
    Didn’t Zak explain that search in the complete list would not be a problem. And mod-search definitely can handle the numbers
18:49:40 Von  Sara Colglazier (MHC/5C)  an  Alle:
    This is only for MCLs, right?
18:50:19 Von  Kristin Martin  an  Alle:
    Completely support that Zak
18:52:05 Von  Laura Daniels  an  Alle:
    if you put it in Slack I can share with others at my institution to get real use cases
18:52:23 Von  Martina Schildt | VZG  an  Alle:
    And then we can collect on a confluence page
18:52:37 Von  Maura Byrne  an  Alle:
    +1 Martina
18:52:51 Von  Charlotte Whitt  an  Alle:
    And we can also share with the MM-SIG and get their feed back
18:53:01 Von  Martina Schildt | VZG  an  Alle:
    that would be great
18:53:05 Von  Charlotte Whitt  an  Alle:
    Also we need to loop in the RA SIG
18:53:06 Von  Dennis Bridges  an  Alle:
    I would say the common use case is. I have a table with lots of data in it and I don't want to spend the time browsing through it to find the row I need to work with
18:53:16 Von  Dennis Bridges  an  Alle:
    Sara, removing columns from the table only has a visual impact. The filter will still see that data and include those pieces
18:53:22 Von  Charlotte Whitt  an  Alle:
    + 1 Dennis
18:54:16 Von  Laura Daniels  an  Alle:
    I agree with Dennis -- from Inventory perspective, I'd be looking for a specific item from a long list by enumeration/chronology or by barcode
18:54:36 Von  Dung-Lan Chen  an  Alle:
    +1 to Dennis "I have a table with lots of data in it and I don't want to spend the time browsing through it to find the row I need to work with"
18:55:16 Von  Charlotte Whitt  an  Alle:
    And also there is no specifik common use case. The search and filter actions will vary depending on the given app, the given title, and the given staff type (RA, Acq., MM, Tech staff etc.)
18:57:59 Von  Charlotte Whitt  an  Alle:
    Yes, great point Dennis. Search and filter in the Settings tables would be good.
18:58:27 Von  Charlotte Whitt  an  Alle:
    Settings > Data Import has implemented some kind of filtering  already
18:58:35 Von  Owen Stephens  an  Alle:
    Apologies I have to dash
18:58:57 Von  Martina Schildt | VZG  an  Alle:
    Thanks Owen
18:59:04 Von  Khalilah  an  Alle:
    Thanks Owen
19:00:07 Von  Dennis Bridges  an  Alle:
    I need to drop as well. Good conversation all. thx!
19:00:20 Von  Martina Schildt | VZG  an  Alle:
    Thanks
19:00:42 Von  Martina Schildt | VZG  an  Alle:
    Thank you so much Khalilah!
19:00:47 Von  Sara Colglazier (MHC/5C)  an  Alle:
    Thanks!

Attendees

Action items