2025-8-6 Agenda and Meeting notes

Zoom link: https://folio-org.atlassian.net/wiki/spaces/ERMSIG/pages/47776470/eHoldings+subgroup#Zoom

 Date

Aug 6, 2025

 Participants

@Zorian Sasyk @Becca Banach @Lars-Håkan Herbertsson @Catherine Tuohy

 Agenda

1. Housekeeping

2. ERM/eHoldings - Brainstorm

3. Misc (if time)

   1. eHoldings User Story backlog review - https://folio-org.atlassian.net/issues/?jql=project%20IN%20%28UIEH%2C%20MODKBEBSCO%2C%20MODKBEKBJ%29%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20updated%20ASC%2C%20created%20DESC

4. Actions

 Discussion topics

Notes:

1. Housekeeping

   1. Feature updates:

      1. Package-Title record search-within and titlelist table conversion in Sunflower, libraries should see functionality by Fall 2025

      2. Trilium will be longer release - Provider-package record search within and titlelist conversion aiming partially for Trilium, partially for Umbrellaleaf

      3. Analysis work being done on implementing updated HoldingsIQ API endppints in eHoldings - https://folio-org.atlassian.net/browse/MODKBEKBJ-698

2. ERM/eHoldings - Brainstorm

   1. What are the pain points/frustrations of using eHoldings in FOLIO?

      1. HLM is “easier” to use, “more sorting and browsing options”

         1. Group discussed further the general problem that finding exactly what package or title to turn on in HLM or KBs in general is not always clear, and is more an “art” than a “science”; it cannot really be solved fully via the UI, since the problem is ultimately an upstream data issue (publishers/vendors sales' teams call products one thing, the metadata teams at said entities that send the kbart files that become HLM packages call them another thing, and the customer is left to reconcile those to find and activate an eresource)

         2. HLM currently displays more information on its package list and titlelist screens than eHoldings does, this data includes crucial data points like publisher, coverage, ISSN etc that librarians check for to do the above “reconciliation” to locate the write eresource to activate. This is possibly why many FOLIO libraries bypass eHoldings in favor of HLM for activation currently.

         3. However, the group indicated that the recent changes asked for and then implemented in Sunflower at the package-titlelist level (MCL table display) goes a long way towards resolving said discrepancy

      2. Prefer to use eHoldings for initial activation (right after acquisitions process/ordering is done and agreement has been made), HLM for troubleshooting/management. Keeps Acquisitions-Activation steps of ERM Lifecycle completely within FOLIO

         1. Additional question: would further integration of eHoldings with the orders app (specifically the POL record page) be beneficial?

            1. Currently, order of workflow (Orders - Agreements - eHoldings activation via AGL) is primarily dictated by how FOLIO is currently designed/functions.

            2. Would be open to new possibilities via more cross-app integration

               1. Idea - In POL record creation/edit page, have search functional similar to current title-inventory linking search, but for eHoldings and for linking POL to eHoldings/AGL (could generate Agreement from this as well?)

               2. Idea - Sync POL subscription from-to date fields with Agreement period start-end dates or AGL start-end date

      3. Encouraged group to keep thinking about this topic, discuss with library colleagues, and provide feedback to eHoldings SIG chat

3. Misc (if time) - DID NOT DISCUSS

   1. eHoldings User Story backlog review -

4. Actions

Action items:

-eHoldings SIG members continue thinking about topic, take back to libraries to discuss, provide feedback to SIG/Zorian