2023-09-20 Meeting notes: UI options for "save" button | part III

2023-09-20 Meeting notes: UI options for "save" button | part III

Date

Sep 20, 2023

Meeting Time:   12 pm ET / 5 pm UK / 6 pm CET

Zoom

Meeting URLhttps://zoom.us/j/869183544  - Password needed: please see here.

Recordings Mondays (since February 2022)

Housekeeping

  • Convener and notes @Martina Schildt 

  • Next meeting: Sep 25, 2023 

Discussion items

  1. UI options for "save" button | meeting with UX/UI designers and Stripes team members to agree on a way forward (@Gill Osguthorpe @Kimie Kester @Zak_Burke )

    1. Mock-ups by Gill

  2. Responsive text fields UXPROD-4431: Implement responsive text fieldsDraft

  3. MCL: export complete lists

    1. is a Spike created?

    2. are there possible ways from a technical perspective to export full MCL list to excel?

      1. possibly create a Spike if not yet existing

  4. further MCL agreements: UI / UX agreements across apps → if no tickets existing → Martina will create them

 

Minutes

UI options for "save" button

Mock-ups by Gill

Results

A | 1st question - pattern - single choice
B | 1st question - pattern - after adding the alternative choices from the comments section
C | 2nd question - options to change primary Save button
D | Comments

Requirements

Requirements 

Notes

Requirements 

Notes

A keyboard shortcut for each save function should be implemented as well. Perhaps ctr+alt+R for save and close (release record from editing)?

 

Save & keep editing: record should stay in edit mode, not refresh the page

just save data

Save & keep editing: no long loading times

 

Save & keep editing: editing should continue where the user "left" the record

 

Fixed buttons

 

Confirmation: green toast / banner to confirm that data is saved

 

Showing the time of the last save in edit mode | close to the save button | administrative data

 

Meeting notes

  • in general the community voted on 2 buttons, the shorter labels were preferred

  • Martina  will create an umbrella ticket, the different teams can create subtickets, that can be cloned

  • there will be separate tickets for:

    • save button option taht community agreed on

    • customisation option that is preferred

  • reason: the more complicated development on customisation should not stop the UI for save buttons to be implemented across FOLIO

  • Owen will present the UI agreement for save buttons in a PO meeting

Requirements

  • different event handling

  • question tbd: is it possible to share a form template

Responsive text fields

UXPROD-4431: Implement responsive text fieldsDraft

  • we should do a poll to learn whether

    1. this change should apply to all text fields and should be applied globally

    2. or whether it is a field by field decision | attributes can be added individually per text field

@Martina Schildt to create a poll on repsonsive text fields

MCL: export complete lists

  • is a Spike created? → no

  • are there possible ways from a technical perspective to export full MCL list to excel? → yes

  • possibly create a Spike if not yet existing

  • how do we handle handle too many rows to export? →

    • add a warning?

    • reject the download

    • do the download via data export → submit data (UUIDs) to data export

  • what is a reasonable amount of data? - needs analysis

  • Kristin in chat: You can download every single order in FOLIO right now.

  • in orders: it is requesting 25 IDs at a time

  • filtering afterwards ine xcel is easier than filtering in FOLIO and then exporting

  • Kristin sometimes exports 50.000 records - takes time, but that is okay

Next steps

 

Chat

18:01:20 From Martina Schildt | VZG To Everyone:
    AI Agenda for today: 2023-09-20 Meeting notes: UI options for "save" button | part III
18:02:17 From Charlotte Whitt To Everyone:
    Interesting diagram 😊
18:02:32 From Martina Schildt | VZG To Everyone:
    Reacted to "Interesting diagram ..." with 😊
18:07:06 From Dung-Lan Chen To Everyone:
    I'm noting attendance in case you wonder what I'm updating the page on
18:10:37 From Kristin Martin To Everyone:
    BRB
18:13:44 From Kristin Martin To Everyone:
    back
18:16:21 From Dung-Lan Chen To Everyone:
    I think answering the questions from the survey is a great idea
18:32:15 From Kimberly Pamplin To Everyone:
    Currently it looks like save & keep editing in inventory will kick you back to the top of the record.
18:33:04 From Kimberly Pamplin To Everyone:
    It's fixed
18:35:36 From Dung-Lan Chen To Everyone:
    Yes, confirming an action happened is helpful!
18:36:15 From Gill Osguthorpe To Everyone:
    Showing the time of the last save would be nice.
18:53:23 From Kristin Martin To Everyone:
    You can download every single order in FOLIO right now.
19:00:01 From Kimie (Keemee) Kester To Everyone:
    Thank you, Goodbye
19:00:04 From Kristin Martin To Everyone:
    Thanks!

Attendees

Present

Name

Home Organization

Present

Name

Home Organization

x

Amanda Ros

TAMU

 

Ann-Marie Breaux

EBSCO

 

Brooks Travis

EBSCO

x

Charlotte Whitt

Index Data

x

Dennis Bridges

EBSCO

 

Dung-Lan Chen

Skidmore College

x

Gill Osguthorpe

UX/UI Designer - K-Int

x

Heather McMillan Thoele

TAMU

 

Ian Ibbotson

Developer Lead - K-Int

 

Jana Freytag

VZG, Göttingen

 

Khalilah Gambrell

EBSCO

      x

Kimberly Pamplin

TAMU

 

Kirstin Kemner-Heek  

VZG, Göttingen

x

Kristin Martin

Chicago

 

Laura Daniels

Cornell

 

Lloyd Chittenden

Marmot Library Network

 

Marc Johnson

K-Int

x

Martina Schildt

VZG, Göttingen

 

Martina Tumulla

hbz, Cologne

 

Maura Byrne

Chicago

 

Mike Gorrell

Index Data

x

Natascha Owens

Chicago

x

Owen Stephens

Product Owner -  Owen Stephens Consulting

 

Patty Wanninger

EBSCO

 

Sara Colglazier

Five Colleges / Mount Holyoke College Library

x

Kimie Kester

EBSCO

 

John Coburn

EBSCO

x

Zak Burke

EBSCO

Action items