2022-06-29 Meeting notes: Implementers topics: UX/UI

• freeze rows

Agreed

• improves overview

• it is difficult to know what the height of each list should be

• will vary, so no general criteria - status: set per app (where it makes sense)

• need to agree on a default behaviour

• there is conflict if we have more and more MCLs with check boxes

• in cases where we have check-boxes, freeze the first 2 columns?

• PO would agree with SIG on how many columns need to be freezed

Agreed

with exceptions

NO

Spike needed

@John Coburn 

• sorting of table headers should be available consistently across apps

• helpful to have a sort indicator, to indicate that a column is sortable

• pageable lists: some columns are not sortable

• all not pageable lists should have sortable headers

• Sara in chat: Just wondering--if not a MCL thing then for the future--just wondering: like in a spreadsheet can I sort on Column A and then on Column B in conjunction

• for paged lists: yes

• for non-paged lists: no

• would be great to have it for paged and non-pages lists

Agreed

YES?

• add line numbers to MCL result lists

• important to have in mind that numbers are usually independant from the line content

• first line will always be #1

• there should be an indicator that it is a row number; because there are some exceptions where it is not

• additionally, numbers could give an ancor for clicking to see more details → no, rather name, barcode (depending on the use case)

• anchored text instead of anchored rows; text that looks like a link

• therefore define columns with click ancor as never hide

• Kimie in chat: If we add line numbers, and then the user drags and drops a row, will the numbers be able to update at the moment of the drag and drop? → John: yes, they have to

Agreed

• full search and sort for the sub-MCLs is needed

• An option to pop out a sub-MCL into its own full screen window with search and filter options

• make available at accordeon level

Agreed

• export option helps as more functionality in Excel

• e.g. export is available for some MCLs in orders

• does not help in every situation;

• but would be nice as an additional option

Agreed

needs confirmation

• Modals or other popups need to move

• should not be fixed in place on the screen

• In various Apps functional Modals be moved out of the way while in use but at the same time cover over information that is needed while using the Modal.

• Modals need to be able to be moved.

• Not all modals are "Look-up" modals, some are "Fill-out" modals and so info is on the screen now hidden

• e.g.: in the Receiving App, the Receiving Note.

• Additionally, I often want to copy and then paste into the pop-up modal info from the screen behind, but no longer can.

• I would hope that if I can move it out of the way, I then would also be able to copy off it to pate into fields in the popup

• my demo example would get be when I am creating a piece in the Receiving App.

TBD

• Ability to change size of modal

• it would be helpful to be able to change the size of the popup

• e.g. enlarge to view more lines / more information

• Warning Modals needed when deleting any record in any App when it is the source of truth for other records

• To avoid dead links, or even disappearing records and information, when deleting a record to which other Apps link or connect or downstream display information regarding, a warning modal should appear informing the user that if they confirm the deletion then the following other records in such-and-such apps will be unlinked or deleted as well

• In the User Management SIG today (6/29/2022) it was discussed that it would be convenient to have the ENTER key perform the Primary button function on a modal. 

STCOM-1041: Spike: Modal (non-form) accessibility | Default focus to the primary action button ClosedPreview

• Wildcards (truncation marks) need to be standardized across all Apps

• Currently depending on what App either % or * is the truncation mark to use. 

• How Dates are formatted and entered

• Example: In Inventory 'extra' spaces are eliminated,

• while in Orders they can exist and impact search & retrieval:

  • From Orders: Newspaper  of  extra  spaces  becomes Newspaper of extra spaces in Inventory.

• If you copy Newspaper of extra spaces from Inventory to search in Orders by Orders Lines, you retrieve nothing, until you add the spaces back

• Use of lowercase vs CAP re: searching not consistent,

• barcode example (in my case, B891369-MHC vs. B891369-mhc) or

• KW in Inventory searching for something that is an Identifier for example, in my case (MHeb* works but not (MHEB* ... ... different in other apps

Ann-Marie Breaux

EBSCO

Brooks Travis

EBSCO

Charlotte Whitt

Index Data

Dennis Bridges

EBSCO

Dung-Lan Chen

Skidmore College

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

Kirstin Kemner-Heek  

VZG, Göttingen

Kristin Martin

Chicago

Laura Daniels

Cornell

Lloyd Chittenden

Marmot Library Network

Martina Schildt

VZG, Göttingen

Martina Tumulla

hbz, Cologne

Maura Byrne

Chicago

Mike Gorrell

Index Data

Owen Stephens

Product Owner -  Owen Stephens Consulting

Patty Wanninger

EBSCO

Sara Colglazier

Five Colleges / Mount Holyoke College Library

Kimie Kester

EBSCO

John Coburn

EBSCO

Zak Burke

EBSCO