2023-09-11 Meeting notes: UI options for "save" button | part II
Date
Meeting Time: 12 pm ET / 5 pm UK / 6 pm CET
Zoom
Meeting URL: https://zoom.us/j/869183544 - Password needed: please see here.
Recordings Mondays (since February 2022)
Housekeeping
- Convener and notes Martina Schildt
- Next meeting:
Discussion items
- UI options for "save" button
- Mock-ups (Gill Osguthorpe )
Minutes
- Background to why we discuss this topic:
- The need for a "save" button / a just "save" option has been raised in different SIGs and has been discussed in the App Interaction SIG
- there is already work going on in Quickmarc to have a "save & keep editing" button
- but there are more options when it comes to saving, such as "create another" which is a checkbox at the moment
- important: there should not be too many buttons
- to have a good and consistent UI Gill Osguthorpe has created some mock-ups with different options
- MM SIG had presented some suggestions in a previous meeting, but was absolutely fine to continue with Gill's mock-ups
- Gill demos the mock-ups and the different options
- Zak: we need to establish a pattern of how things are displayed - implementation is done by the various development teams themselves and is done per app
- each feature such as "save and keep editing", "save and duplicate" needs to be implemented for each application separately
- the pattern is supposed to be a pattern across all apps
- immediate votes in the call on Gill's mock-ups
- A1 +1
- B2 +3
- C2 +2 - set action and have it persist
- general feedback: any of the options is fine, it would be great to have a separate save option and consistency
- Phil: If we choose option A - "save & close" and drop-down icon: it would be good to have the buttons be displayed in the same colour for it to be obvious that both buttons are selectable and clickable
- Thomas in chat: The solid background is usually used for the ‘default’ option, so I can see that.
- Gill presents one more option that is not part of the survey:
- Instead of having a primary button, the button displays "Actions" and a drop-down - from the drop-down list all available save options can be picked
- Feedback: Having an actions button and then display the options seems too much clicking to the group - the group votes for having a default option - so that at least one action can be performed with one click
- Autosave is raised as an alternatove or additional option for the save button
- Phil in chat: Would an autosave after 60 secs and every minute after be an option for 'save and continue'?
- Laura in chat as a response: Some of us don't want autosave, as we like the option to back out if we have made errors
- Jackie agrees in chat: Exactly!
- Thomas in chat: Agreed.. I fell it would be risky without a roll back feature
- Laura in chat: that is, just close to revert to previous version
- Phil: the need and "risk" may be different in different apps - e.g. Licenses (yes/no change) vs. Inventory (complicated cataloguing changes)
- Owen in chat: The “save & keep editing” option might need some thought as I understand in quickmarc there are some issues with the screen refreshing on save
- Raegan agrees: reloading takes a lot of time - you need to scroll back to the accordion/information where you have left - that takes too much time
- Zak: we need to agree on a pattern that will then work across all apps
Please vote on your preferred options via this survey: https://forms.gle/uvpA6VjZ1yENTyvm7. The survey can be shared. Deadline end of day.
The results, requirements and next steps will be discussed on .
Next steps
- discuss results of this meeting and votes on preferred way forward with UX/UI designers and stripes team members.
Chat
18:01:45 From Martina Schildt | VZG To Everyone:
2023-09-11 Meeting notes: UI options for "save" button | part II
18:05:20 From Laura Daniels To Everyone:
I'm happy to see so many of my MM colleagues here today.
18:10:49 From Maura Byrne To Everyone:
I like the idea of a “Save” button and a “Save and…” button. Could they have keyboard shortcuts, so we wouldn’t have to use a mouse?
18:12:53 From Thomas Trutt To Everyone:
Replying to "I like the idea of a..."
If so a variation like CTL+ S for Save and CTL+SHIFT+S for save and —, would be nice and hopefully easy to remember.
18:13:05 From Laura Daniels To Everyone:
Reacted to "If so a variation li..." with ➕
18:13:08 From Maura Byrne To Everyone:
Reacted to "If so a variation li..." with ➕
18:14:26 From Thomas Trutt To Everyone:
Actually in another meeting a while back someone suggested a ‘dumb’ system for users preferences. It would be a new app but basically just a datastore.
18:17:04 From Phil Adams To Everyone:
Thanks for the presentation. I easily understand 'Save' as meaning 'Save and continue, keep editing'
18:17:51 From Laura Daniels To Everyone:
I'm also a fan of the short labels (might be easier to translate also?)
18:17:59 From Maura Byrne To Everyone:
Reacted to "I'm also a fan of th..." with 👍
18:18:03 From Phil Adams To Everyone:
Reacted to "I'm also a fan of th..." with 👍
18:18:23 From Thomas Trutt To Everyone:
Reacted to "I'm also a fan of th..." with 💯
18:18:36 From Gill Osguthorpe To Everyone:
Reacted to "Thanks for the prese..." with 👍🏼
18:18:41 From Gill Osguthorpe To Everyone:
Reacted to "I'm also a fan of th..." with 👍
18:18:45 From Jackie Magagnosc To Everyone:
Reacted to "I'm also a fan of th..." with 👍
18:18:46 From Phil Adams To Everyone:
Save and copy might be another useful option
18:18:56 From Maura Byrne To Everyone:
Reacted to "Thanks for the prese..." with 👍🏼
18:20:26 From Jackie Magagnosc To Everyone:
Having consistent options and behaviors across apps would be such a huge gain.
18:20:50 From Laura Daniels To Everyone:
thank you for keeping our expectations realistic, Zak
18:21:24 From Maura Byrne To Everyone:
Reacted to "Having consistent op..." with 👍
18:21:27 From Natascha Owens To Everyone:
Reacted to "Having consistent op..." with 👍
18:21:29 From Phil Adams To Everyone:
Reacted to "Having consistent op..." with 👍
18:21:35 From Maura Byrne To Everyone:
Reacted to "thank you for keepin..." with 💯
18:21:50 From Phil Adams To Everyone:
Reacted to "thank you for keepin..." with 👍
18:21:56 From Dung-Lan Chen To Everyone:
Reacted to "Having consistent op..." with 👍
18:23:44 From Dung-Lan Chen To Everyone:
+1 to Laura
18:24:08 From Natascha Owens To Everyone:
I am just a bit unsure about how long the list might get depending on how many options we introduce and then have that repeated in the Primary button action list
18:24:51 From Maura Byrne To Everyone:
Big Yes for Thomas’s point
18:26:07 From Thomas Trutt To Everyone:
The solid background is usually used for the ‘default’ option, so I can see that.
18:28:12 From Dung-Lan Chen To Everyone:
Yes, reducing clicking is important to my staff.
18:28:20 From Thomas Trutt To Everyone:
Replying to "I am just a bit unsu..."
To Zak’s point it I think this would depend on each app and probably each form. What options are added by the devs for that app/form.
18:28:26 From Kristin Martin To Everyone:
Reacted to "Yes, reducing clicki..." with 👍
18:28:31 From Jackie Magagnosc To Everyone:
Reacted to "Yes, reducing clicki..." with 👍
18:28:35 From Laura Daniels To Everyone:
Reacted to "Yes, reducing clicki..." with 👍
18:30:06 From Kristin Martin To Everyone:
Save and Keep Editing feels like it should be the primary option.
18:30:19 From Jackie Magagnosc To Everyone:
Reacted to "Save and Keep Editin..." with 👍
18:31:48 From Thomas Trutt To Everyone:
Agreed.. I think it also follows patterns already out there.
18:32:14 From Phil Adams To Everyone:
Would an autosave after 60 secs and every minute after be an option for 'save and continue'?
18:32:57 From Laura Daniels To Everyone:
Replying to "Would an autosave af..."
Some of us don't want autosave, as we like the option to back out if we have made errors
18:33:07 From Jackie Magagnosc To Everyone:
Replying to "Would an autosave af..."
Exactly!
18:33:18 From Thomas Trutt To Everyone:
Replying to "Would an autosave af..."
Agreed.. I fell it would be risky without a roll back feature
18:33:19 From Laura Daniels To Everyone:
Replying to "Would an autosave af..."
that is, just close to revert to previous version
18:33:38 From Maura Byrne To Everyone:
Reacted to "that is, just close ..." with 👍
18:34:12 From Owen Stephens To Everyone:
The “save & keep editing” option might need some thought as I understand in quickmarc there are some issues with the screen refreshing on save
18:34:24 From Laura Daniels To Everyone:
Reacted to "The “save & keep edi..." with ☝️
18:35:32 From Natascha Owens To Everyone:
I'm sure I would be happy with any of these options but would love for my coworkers to get a chance to vote--is voting open to anyone?
18:36:35 From Maura Byrne To Everyone:
Replying to "I'm sure I would be ..."
Maybe you can show the mockups to your staff, and see which they prefer, and you can have a “departmental” vote.
Attendees
Present | Name | Home Organization |
---|---|---|
Amanda Ros | TAMU | |
Ann-Marie Breaux | EBSCO | |
Brooks Travis | EBSCO | |
x | Charlotte Whitt | Index Data |
Dennis Bridges | EBSCO | |
x | Dung-Lan Chen | Skidmore College |
x | Gill Osguthorpe | UX/UI Designer - K-Int |
Heather McMillan Thoele | TAMU | |
Ian Ibbotson | Developer Lead - K-Int | |
Jana Freytag | VZG, Göttingen | |
Khalilah Gambrell | EBSCO | |
Kimberly Pamplin | TAMU | |
Kirstin Kemner-Heek | VZG, Göttingen | |
x | Kristin Martin | Chicago |
x | Laura Daniels | Cornell |
Lloyd Chittenden | Marmot Library Network | |
Marc Johnson | K-Int | |
x | Martina Schildt | VZG, Göttingen |
Martina Tumulla | hbz, Cologne | |
x | 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 | |
Kimie Kester | EBSCO | |
x | John Coburn | EBSCO |
x | Zak Burke | EBSCO |
x | Thomas Trutt | |
x | Phil Adams | |
x | Jackie Magagnosc | |
x | Catherine Tuohy | |
x | Jean Pajerek | Cornell |
x | Raegan Wiechert |