2024-07-9 BELA Meeting Notes

1

Housekeeping

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

• Who can take notes today? Let’s start selecting the notetaker in the alphabetical order of the first name. We will start with “A” today. If there is no one with the first name starting with “A” we will move down the alphabet.

3

Ramsons release updates

• Bulk edit (Kanban Board)

  • Filtering Instance properties: The only thing that doesn’t work is being able to clear the field by clicking on the x as the x doesn’t appear.

  • Optimistic Locking: There is now a warning message with a link to that record and no changes occured through bulk edit. Right now there is no override. Part of the url is provided in the downloadable csv.

• Lists app (Kanban board)

  • Demo of new functionality in FOLIO snapshot. Select instance fields are now accessible.
    
    

4

Bulk edit MARC Instances vs ETL

What are the expected benefits of using Bulk edit for editing MARC instances? Proposed architecture: Bulk Operations + Data Import integration approach

Bulk Edit will use Data Import to update these fields. Consult the wiki page above on Bulk Operations. A job profile will be created just for Bulk Edit. Field protections will be looked at a little later.

Question about performance: How will these bulk edit jobs that rely on Data Import be handled by the queue? Bulk Edit jobs should wait for single record import. File slicing is a tenant configuration and some institutions don’t do this. There is a problem with 100k records with the slicing. Should we continue to use the ETL approach until Data Import’s performance is improved? There may be a way to disable the funcationlity so that users can continue to use the ETL approach.

Should the errors be on the Bulk Edit page or through Data Import? People would prefer that the errors appear in Bulk Edit. People like the ability to download the reports as a csv. The solution might be a mix with a brief log in Bulk Edit and then more details in Data Import.

5

Bulk edit: Errors vs. Warnings

• Separate errors from warnings: An error is something that prevents identifying the record (invalid identifier, duplicate identifier, no match found, multiple records, tech issues, those that prevent the data from eing saved). Warnings don’t prevent saving changes and contain information about bad data, no change required, optimistic locking.

  • It would be great to have the ability to have a list of records that have the same identifier.

  • Introduce “show warnings” option that will be disabled. Change errors to “errors and warnings” with details on the number of errors and warnings. Errors will be sorted on top.

  • It would be nice to have 2 sections one for warnings and errors.

  • Should we have a new column for error and warning? If we can’t have 2 secitons, then yes.

• Update reported error counts

  • Change the label at the top to include the record type of record. If multiple record types are being changed is to at the top list the instances changed or top level record type. Then the green banner would list the number of each record type changed.

6

Bulk edit statistical codes

Supported actions for updating statistical codes for all inventory record types.

People will have the ability to multiselect statistical codes. Can you add and remove statistical codes in the same Bulk Edit job? Magda will see if this is supported.

Is there a mx length for the stat code names? There might not be a character limit for the name. Some institutions might have longer names than others.