/
Lists app - Trillium - Notes on functionality

Lists app - Trillium - Notes on functionality

New features

Lists: query nested values through the Query Builder UI

This feature enhances query flexibility and precision for querying fields within a record (including repeatable fields that are pre-defined, free-text, Boolean, and nested), supporting intuitive operators and more accurate search results.

Documentation on fields: Trillium - Nested fields that can be queried

User-defined entities with joins, created via API, for use in Lists app

Users have expressed the desire to be able to join different types of data/records within a single list. This functionality provides users the ability to join data across record types, enabling users to turn fragmented data into richer, connected entities. These custom entities (ETs) are created by API and can be utilized in the Lists app UI.

Uses cases for using custom entities vs “built-in” record types within the Lists app:

Custom entities in the Lists app

Built-in entities within the Lists app

Custom entities in the Lists app

Built-in entities within the Lists app

  • custom entities are created via API, then can be accessed through the Lists app

  • provides advanced users a mechanism to combine existing Lists app / FQM data in different ways than what’s provided out of the box with built-in entities

  • good for one-off use cases, or institution specific needs

  • limited to combining existing data sources (can’t add new database sources)

  • out of the box “Record types” available in the Lists app

  • provides pre-defined combinations of relevant data from FOLIO modules into a single list/query (composite entity)

  • designed to support a variety of common queries/use cases

  • added/supported by FOLIO development teams; only mechanism to add data from new database sources 

Related Jira: https://folio-org.atlassian.net/browse/UXPROD-4863

Related documentation: https://folio-org.atlassian.net/wiki/x/HIBIWg

Enhancements and bugfixes

Support more types of custom fields

All types of custom fields are now available in the Lists app. This includes custom fields on User records, as well as on Orders/Order lines.

Types of custom fields added in Trillium:

  • Multi select dropdown

  • Date picker

  • User custom fields in other record types, such as loans

Multiselect and date.mp4

Related Jira: https://folio-org.atlassian.net/browse/UXPROD-5126

Query Builder UI is now full-screen

The query builder is now full screen so that users can easily review the records that match the query. The previous modal when building a query does not provide enough space to easily preview all selected columns and requires constant scrolling.

  • The List name now displays in the Header bar

  • The Record type displays above the query

Query builder full window.png

Related Jira: https://folio-org.atlassian.net/browse/UIPQB-65

Improve column headings in export to CSV

In CSV exports of a List the column headers use the same values that display in the UI. In previous releases these column names in the exported file weren’t as user-friendly.

List export headers.png

The Lists app shows data labels in standard readable format in the interface, like

  • User barcode

  • User email

  • User expiration date

In the CSV export, in previous releases the names take this form:

  • user_barcode

  • user_email

  • user_expiration_date

New record types in Lists

The following record types were added to the Lists app / FQM in the Trillium release.

Record type name

Description

More info

Record type name

Description

More info

Authority

CATALOGING

each row is a combination of the authority record that is stored in source record storage (MARC) and the mod-entities-link (FOLIO)

querying most MARC field tags/indicators/subfields is not supported, with the exception of Leader position 05 and 008 position 11.

https://folio-org.atlassian.net/wiki/x/EwBcWg

https://folio-org.atlassian.net/browse/UXPROD-5219

 

Instances with MARC bibliographic

CATALOGING

enables users to query select MARC bib fields that map to FOLIO instance fields, most FOLIO instance fields, and to view and export data from both records, including the full MARC JSONB blob for the record

querying most MARC field tags/indicators/subfields is not supported, with a few exceptions:

  • MARC bibliographic — External HRID = 001

  • MARC bibliographic — Matched UUID = 999ff $s

https://folio-org.atlassian.net/browse/MODFQMMGR-1038

Fee/fine accounts with users

CIRCULATION

each fee/fine account is returned as a row/record in the results; user patron data (including patron group) is returned for results when available. note: user data is not required.

https://folio-org.atlassian.net/browse/MODFQMMGR-906

Users with fees/fines, loans

CIRCULATION

enables users to query patrons by a variety of criteria to determine if users have any outstanding fees/fines. users can appear multiple times - once per fee/fine

query by fields such as:

  • user type, patron group, user custom fields

  • Fee/fine owner, type, payment status, remaining

  • Loan status, due date, return date

  • Item status, notes, tags

https://folio-org.atlassian.net/browse/MODFQMMGR-1074  

Users with manual blocks

CIRCULATION

provides a convenient way to search with users with manual blocks and to export the results to CSV. Supports queries by a variety of user fields (including patron group, custom fields), and manual block fields

Note: once a manual block is deleted, it no longer appears in the Lists app

https://folio-org.atlassian.net/browse/MODFQMMGR-1085  

Users with open transactions

CIRCULATION

provides a useful way to create and export a list of all blocked users. this record type includes a level overview of each users' blocks, indicates any open transactions (true/false), and counts of:

  • Automated blocks

  • Manual blocks

  • Open fees/fines

  • Open loans

  • Open proxies

  • Open requests

https://folio-org.atlassian.net/browse/MODFQMMGR-770

Lost items requiring actual cost

CIRCULATION

returns the equivalent info as the "Lost items requiring actual cost" report in the Users app.

Supports querying by fields such as:

  • User active, patron group, custom fields

  • Loss type, actual cost status, actual cost created date

https://folio-org.atlassian.net/browse/MODFQMMGR-1086

Order - Invoice analysis

ACQUISITIONS

focuses on the following report types:

  • Serials cost projections (ongoing order with no invoice in the current year and an invoice from the previous FY, including vendor, fund and expense class data)

  • A list of unbilled ongoing orders (similar to the above, but simply looking for the absence of an invoice for the current FY)

  • A summary report of amounts paid in a given prior FY (total, per vendor, per expense class…)

  • Continuation funds with unknown future commitments by title

https://folio-org.atlassian.net/wiki/x/rYAcN

https://folio-org.atlassian.net/browse/UXPROD-5202

Receiving pieces

ACQUISITIONS

Each receiving piece is returned as a row in the results; holdings, item, location, order, order line and title information is returned when available

https://folio-org.atlassian.net/browse/MODFQMMGR-943

Receiving titles

ACQUISITIONS

Each receiving title is returned as a row in the results; instance and purchase line order data returned when available

https://folio-org.atlassian.net/browse/MODFQMMGR-970

Performance improvements

Several performance improvements were added in the Trillium release; all changes are in the background and seamless to end users.

Optimized ‘Contains’ and ‘Starts with’ operators

  • The Lists app now uses the optimized "contains" and "starts-with" operators, replacing inefficient regex patterns and improve the performance of list processing in the system.

Indexes added for Instance records

Indexes were added for Instance records; these indexes enable more efficient queries for the fields listed below. Important notes:

  • users don’t need to take any action to use the indexes; queries will automatically use them whenever possible

  • the UI does not indicate which fields (and/or) operators potentially use an index

  • indexes won’t be used for queries that use the ‘Contains’ or ‘Starts with’ operators

Field name

Index name

Field name

Index name

Instance — Created date

instance_creation_date_idx

Instance — Cataloged date

instance_cataloged_date_idx

Instance — Publications — Publication date

instance_publication_date_idx

Instance — Subjects — Subject headings

instance_subjects_values_idx

Instance — Format names

instance_format_ids_idx

Instance — Identifiers — Identifier

instance_identifiers_values_idx

Instance — Notes — Note type

instance_notes_instancenotesnotetypeid_idx

Related Jira: https://folio-org.atlassian.net/browse/UXPROD-5127