Sort "cards" in logical or alphabetical order

Cards are sorted differently earch time a user visits a page in both apps.

Example ERM - requirement across folio

Order: j, e, k, e

Open

Order: e, k, j, e

Open

Requirements

• "Cards" should display consistently every time a user checks a record - every time the same order - both in view and in edit mode

• Better: user can define the sort order when creating the "cards" 

• Sorting needs to be editable and adjustable over time - e.g. if a third internal contact is added to a list of two but needs to display as the first contact → ability to re-arrange the sort order 

• need a mechanism - "order by" clauses

• 1st step: get predictability 

• 2nd step: extend to more user based decisions

Sort Inventory items as needed

Inventory items: Ability to reorder (and save the order of) item records

• 
  UXPROD-1625 - Re-order Item records DRAFT

Ideas:

1. specific rank field/column,

2. drag & drop,

3. arrow up/down,

4. sort order as an attribute of holdings

• if there are no other uses cases → continue as a MM SIG discussion

• if cross-app: continue in AI - create cross-app ticket

Sort Inventory holdings as needed

Inventory holdings: Ability to reorder (and save the order of) Holdings records

• 
  UXPROD-1635 - Order/sequencing of holdings on an instance record. Re-order Holdings records DRAFT

• sorting at the moment: order of entry?

• seems like it is always the same order → so different to cards use case

• in general: every query should have an "order by" clause

Comment by @Felix Hemme

Yes, holdings records sort by date created (newest holdings sort at top of the list) in the instance detail view. The German subject group on MM has proposed a new default order, see https://folio-project.slack.com/archives/C20V5L40P/p1668086310716649.

There will be a official proposal created soon. Draft (in German) here: Überarbeitete Sortierung der Bestandsdatensätze (Holdings) - Funktionsanalyse

Edit mode: Add a just "save" button, instead of having only "Save & close" or "cancel"

from discussion 2023-06-28 Meeting notes: cross-app implementers topics

• in some apps there is already the option to "Save & keep editing"

• Available in quickMarc

• Button is called "Save & keep editing" - that is very explicit but very long at the same time

• Will be available for holdings https://folio-org.atlassian.net/browse/UIIN-2404

• and item level: https://folio-org.atlassian.net/browse/UIIN-2456

• as well as instances: https://folio-org.atlassian.net/browse/UIIN-2457

• In Orders and Agreements with have a “Create another” checkbox next to the Save button for situations where you want to save but immediately open another create form

• Needed: consistent behaviour and labelling

• on the other hand we shouldn't have too many buttons

• requirement: consistent behaviour across apps for buttons → checkbox "create another" could be a button as well

• options discussed:

  1. keep UI as is → not consistent across apps

  2. keep buttons and add additional

     1. save & create another, save & keep editing, save & close (bottom right corner) + cancel (bottom left)

  3. change and shorten button descriptions:

     1. save, close, create another (bottom right) + cancel (bottom left)

  4. add an "action" menu or a modal

     1. if there are more than X buttons (number is tbd), display "cancel", "close" and "save & ...", where the user selects via an action menu or a modal which "save-and-action" is desired

     2. the group likes the idea of having a certain number of choices and then a menu

• discussion not finished - need to come back (after WOLFcon)

Responsive text fields

Free text boxes are quite narrow in display and can then be extended. Sometimes the extendability may not be as obvious as needed. It would be helpful to have the free text boxes be responsive.

Example use case:

Inventory holdings: The URI box in the holdings record is really small. It does expand, but I can imagine someone not noticing a URL was really long and only editing part of it and mangling it all up.

Amanda Ros

TAMU

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

x

Kimberly Pamplin

Kirstin Kemner-Heek  

VZG, Göttingen

Kristin Martin

Chicago

Laura Daniels

Cornell

Lloyd Chittenden

Marmot Library Network

Marc Johnson

K-Int

Martina Schildt

VZG, Göttingen

Martina Tumulla

hbz, Cologne

Maura Byrne

Chicago

Mike Gorrell

Index Data

      x

Natascha Owens

Chicago

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