/
2025-08-19 BELA Meeting Notes

2025-08-19 BELA Meeting Notes

@Attendees (please add your name)

@Jennifer Eustis @Amanda Ros @Kimie Kester @Corrie Hutchinson @Whitney Christopher @Joshua Lambert @Kathleen Moore @Magda Zacharska @Scott Perry @Peter Martinez @Aaron Neslin @Eddie Fournier @Maccabee Levine @Sara Colglazier

Note Taker: Jennifer Eustis

Meeting Recording

Links to Implementers' Topics

Bulk Edit Resource Management Implementation Topics Page

List App Resource Management Implementation Topics Page

Discussion:

Topic

Agenda

Topic

Agenda

1

Housekeeping

  • Attendees - please add your name to the list of attendees.

  • Who can take the notes today? Jennifer. More volunteers would be appreciated.

  • Lola Estelle is taking Christine Tobias spot in the Documentation WG.

2

Lists app

See recording for demo.

Question: If you were using this to retrieve inventory records, is it returning full record? It depends on how you structure the query itself. You can query a subset of item fields in an item record. There are also composite types which pulls in data from other record types.

There’s a difference between storage and business logic. Would you make the analogy that this is one or the other of those? Kathleen will get back to Maccabee on that.

There’s also inventory - view APIs. The idea is to return instance and associated holdings and items. Is this analogous to the composite entity types? Kathleen will get back to Maccabee on that.

  1. Is using the FQM API calls more akin to the /inventory-storage APIs or the (business logic) /inventory APIs, in processing it does before returning results?

    • FQM APIs are closer to inventory-storage, but there's a small amount of business logic, like combining fields together for statistical codes

  2. What are the use cases of using the FQM API for inventory data vs the /inventory-view API that also returns multiple business objects (instance, holdings, item) together?

    • There’s limited use for just inventory data

      • FQM becomes especially useful if you want to mix in non-inventory data, too

      • FQM also allows more fine-grained control over which fields in the record are returned by the query (you can include anything from the full record down to a very limited set of fields) 

    • Inventory storage view API returns instance with associated holdings and items

      • API docs

      • FQM doesn’t currently have an entity-type that would return the equivalent of the Inventory storage view API (the closest we have is the composite items entity that will return item data + associated holdings + instance data)

This has been backported to Ramsons CSP #4 (both on Okapi and Eureka). https://folio-org.atlassian.net/browse/MODFQMMGR-821

3

Bulk edit

  • Demo of creating bulk edit profiles and executing bulk edit job using the profiles: https://folio-org.atlassian.net/browse/UXPROD-4025

  • Continue review of https://folio-org.atlassian.net/browse/UXPROD-4952 by reviewing mockups :

See recording for the short demo of bulk edit profiles. No questions or comments.

See recording for mockups for scheduling jobs. To delete a job, remember that you need to disable it before you delete it.

Question: For the landing page, should there be permissions linked to “Actions” menu? Yes, these will most likely be done by different people. This will be permissions issues. For the moment, we will not split scheduling jobs from managing jobs.

Question: For the scheduling a recurring job, this is a dynamic query which will be run before the recurring job is run.