2025-02-18 BELA Meeting Notes

2025-02-18 BELA Meeting Notes

@Attendees (please add your name)

@Magda Zacharska @Kathleen Moore @Jennifer Eustis @Amanda Ros @Corrie Hutchinson @Christine Tobias @Kim Wiljanen @Linh Chang @Kimie Kester @Sara Colglazier

Note Taker:

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?

    • Corrie volunteered.

2

Bulk edit app updates

  1. Ramsons update:

Ramsons was released on February 7th. The preliminary Ramsons bulk edit performance tests results:

image-20250214-164152.png

Recommended max volume for bulk editing MARC instances is 50 000 records. The team is working on improving performance for the next release.

  1. Sunflower update: https://folio-org.atlassian.net/jira/software/c/projects/UXPROD/boards/21?quickFilter=188

    1. Two features in progress : editing MARC bib records, modifying errors & warnings

  2. Questions:

    1. MODBULKOPS-445: Logs tab: Additional column containing name of the file or query used to trigger the bulk edit jobClosed

      1. Raised in Ramsons UAT and previous BELA discussion. Adding the file name helps when the file is no longer available for download due to expiration.

      2. Proposal : add a new, last column with header ‘File or Query’ containing file name or query (using FQL) ; can be sorted alphabetically

      3. Feedback :

        1. Instead of the name, could it be just a the name ‘File’ or ‘Query’ with details available upon download?

          1. Concern : more on the screen to scroll, lengthy queries

          2. Problem : a user might need to download multiple files/queries looking for a particular one.

          3. Workaround : use Developer Tools for more details

      4. Expiration date of files is a configurable value

      5. Topic tabled until Peter can join the discussion

    2. MODEXPW-564: Preventing bulk editing corrupted MARC instances through error handlingClosed

      1. Background : looking into how to avoid time wasted waiting for the entire process to know that the underlying data is corrupted

      2. Proposal : Address 3 instances with corrupted data : MARC instances without SRS, one MARC associated with multiple SRS record, and one SRS associated with multiple MARC records. If BE encounters corrupted data, it will be reported under ‘Errors & warning’ after the user has submitted the query.

        1. Wording for 3 types of errors discussed. Magda’s proposals were accepted with minor adjustments.

      3. Will be included in the Sunflower release.

3

Lists app updates

Sunflower update:

4

Lists app FYI

If an instance record is staff suppressed, you cannot retrieve the record by barcode in Inventory. Encountered while retrieving records via the Lists app.

  • Issue is with Inventory app, not Lists app

  • ‘Instances - Staff suppress’ is an available column in output as of Ramsons.

  • Staff without permissions to view Staff-suppressed materials in Inventory can still see those items in the Lists app.

5

Implementation topics

Bulk Edit:

  • Follow up on the discussion from the last meeting:

    • Extracting optimistic locking errors to a separate file:

      • would have a negative impact on the overall performance

      • will require additional development on the backend (larger scope) and frontend (smaller scope)

    • As a workaround, we can use Excel’s sorting or filtering functionality.

Lists App:

  • List for Finance & Acquisitions. How do these fall into the roadmap?

  • Kathleen just started to look into the feedback more this week. Will be reaching out to individuals to discuss.

  • Many were added by the Five Colleges. Sara willing to help with these items.

Related content