Page Comparison

Versions Compared

Version	Old Version 16	New Version Current
Changes made by	Ann-Marie Breaux (Deactivated)	Ann-Marie Breaux (Deactivated)
Saved on	Jun 20, 2023	Jun 20, 2023

Key

This line was added.
This line was removed.
Formatting was changed.

...

Table filter

inverse	false,false,false,false
numbering	Dynamic Ascending
ddSeparator	‚‚‚
sparkName	Sparkline
column	Component,Page type,Questions/notes,Responses
hidePane	Table header
isNew	true
limitHeight	1
sort	Component ⇧
separator	Point (.)
labels	‚‚‚
ddSeparators	true
default	,,,
isFirstTimeEnter	false
ddOperator	,,,
cell-width	,,,
datepattern	dd M yy
id	1687298418806_1728968047
worklog	365\|5\|8\|y w d h m\|y w d h m
isOR	AND
order	0,1,2,3

Component	Page type	Questions/notes	Responses
App Context menu	Inventory:

https://folio-snapshot.dev.folio.org/inventory

Example (login u: diku_admin | p: admin)
eholdings:

https://folio-snapshot.dev.folio.org/eholdings?searchType=providers

Example (login u: diku_admin | p: admin)
MARC Authority:

https://folio-snapshot.dev.folio.org/marc-authorities?segment=search

Example (login u: diku_admin | p: admin)
Licenses:

https://folio-snapshot.dev.folio.org/licenses?filters=status.active&sort=name

Example (login u: diku_admin \| p: admin)	What option should always be included in this menu?
Checklist app
Column chooser	Inventory

https://folio-snapshot.dev.folio.org/inventory

Example

Should this be implemented for all apps including Data import and Data export - https://folio-snapshot.dev.folio.org/data-import

AND Organizations

Detail record footer

quickMARC

https://bugfest-nolana.int.aws.folio.org/inventory/quick-marc/edit-bib/49de617f-e543-4632-a272-e1d0824b08ce?filters=source.MARC&sort=title&relatedRecordVersion=2

Example (login u: folio | p: folio)

Data import -

https://bugfest-nolana.int.aws.folio.org/settings/data-import/job-profiles/create?query=single&sort=name

Example (login u: folio | p: folio)

Finance -

https://bugfest-nolana.int.aws.folio.org/finance/ledger/create

Example (login u: folio | p: folio)

Inventory -

https://bugfest-nolana.int.aws.folio.org/inventory/create/49de617f-e543-4632-a272-e1d0824b08ce/holding?filters=source.MARC&sort=title

Example (login u: folio | p: folio)

Agreements -

https://bugfest-nolana.int.aws.folio.org/erm/agreements/create?filters=agreementStatus.active%2CagreementStatus.draft%2CagreementStatus.in_negotiation%2CagreementStatus.requested&sort=name

Example (login u: folio | p: folio)

Courses:

https://bugfest-nolana.int.aws.folio.org/cr/courses/3d80c287-65fa-49f1-b95d-f6d91ea5d9dd/edit?nreserves=7&sort=name

Example (login u: folio | p: folio)

What is the exact button label for saving and closing the record?

Should we add the ability to Save & keep editing to this pattern?

Should delete action display?

Centralized translation for Save button – we need to encourage folks to use it
Jira Legacy
server System

Jira

JIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key STCOM-1124

Reiterate UX pattern

Remove delete on Edit
Save & keep editing

Expand/Collapse accordions within a detail record

Should the default button when viewing a detail record be Expand all or Collapse all

Users (default: Expand all): Example
Instance: (default: Collapse all): Example
Holdings: (default: Collapse all): Example
Item: (default: Expand all): Example
PO: (default: Collapse all): Example
POL: (default: Collapse all): Example
eHoldings Titles: (default: Collapse all): Example
eHoldings Packages: (default: Collapse all): Example
eHoldings Providers: (default: Collapse all): Example
Finance: (all default to Collapse all): Example

Standard UX in FOLIO is to collapse accordions if they contain no data, and expand them if they contain data.

This inconsistency relates to which button a user should see when first viewing a detail record in FOLIO - collapse all or expand all.

Expand/Collapse panes

Export results

Filter within accordion

Focus - Default search box

Focus - Shift to Results pane

Hide fields

Orders -

https://folio-snapshot.dev.folio.org/settings/orders/order-templates/create

Example (login u: diku_admin | p: admin)

Previous/Next pagination

Inconsistency

Inventory app -

https://bugfest-nolana.int.aws.folio.org/inventory?filters=source.MARC&sort=title

Example (login u: folio | p: folio)
Organizations app:

https://bugfest-nolana.int.aws.folio.org/organizations?limit=50&offset=0&status=Active

Example (login u: folio | p: folio)
Data import:

https://bugfest-nolana.int.aws.folio.org/data-import

Example (login u: folio | p: folio)
Users app:

https://bugfest-nolana.int.aws.folio.org/users?query=smith&sort=name

Example (login u: folio | p: folio) Is there ever a case for "Load more" instead of Prev/Next?

Which component should be used across all FOLIO apps?

Is there a case of inconsistency?

Have all teams - Inventory app - https://bugfest-nolana.int.aws.folio.org/inventory?filters=source.MARC&sort=title (login u: folio | p: folio)

What had been approved for Prev/Next paging is here:
https://folio-org.github.io/stripes-components/?path=/story/components-multicolumnlist--prev-next-paging

Next steps:

Ask users/PO preferred UX.
1. Asked POs
Broader topic: Discuss with Ann-Marie with about DI consistency.

Print detail record

Orders:

https://folio-snapshot.dev.folio.org/orders/lines/view/b9cc5473-bb40-1d61-afc0-d3a5ba0ed0a8?limit=50&offset=0&query=d

Can a stripes component be created? Can it just be enabled on a detail record?

Results list display settings

Settings > Agreements > Display settings:

https://folio-snapshot.dev.folio.org/settings/erm/general

Example	Should this be a setting for all apps?
Search box (show magnifying glass icon or not)	eholdings:

https://folio-snapshot.dev.folio.org/eholdings?searchType=providers

Example (login u: diku_admin | p: admin)
Inventory:

https://folio-snapshot.dev.folio.org/inventory/

Example (login u: diku_admin | p: admin)
Agreements:

https://folio-snapshot.dev.folio.org/erm/agreement

Example (login u: diku_admin | p: admin)
Invoice:

https://folio-snapshot.dev.folio.org/invoice

Example (login u: diku_admin \| p: admin)	Which pattern should be followed?	Looks like the pattern is to show a magnifying glass icon when there are no searchable indexes directly above the entry field. When there are searchable indexes, then the icon does not display. See: https://folio-org.github.io/stripes-components/?path=/story/components-searchfield--basic-usage
Settings - Set up picklists
Settings patterns	https://

wiki

folio

org

26EMBw

CGMV
Sort
Template	Orders -

https://folio-snapshot.dev.folio.org/settings/orders/order-templates/create

Example (login u: diku_admin \| p: admin)
View record in Full pane		What apps can support a record display in full pane at this time?