2024-01-05 BELA Meeting Notes

Housekeeping

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

• Meeting host -  please turn on Transcript option for the meeting.

• Who can take notes today?

  Quesnelia release update

• Bulk edit (Kanban Board)

  • FOLIO Holdings Notes are ready (UXPROD-4020)

  • FOLIO E-Access Holdings - in progress (UXPROD-4008)

    • Find and replace

  • Discovery and Staff suppress Instance notes - in progress (UXPROD-3992)

    • Staff notes appear only in Instances, so there will not be an option to suppress note in Holdings or Items.

• Lists app

  • Working on performance improvement

  • Duplicate a list (UXPROD-4454)

Bulk editing large data sets

• API vs. UI?

  • API - Script used to update large data sets in the back end. Scripting language provided by institution's IT department (likely not librarians). No need to sit, watch, and wait for update to complete.

    • Many of us do not have the programming skills to implement this feature.

  • Many of us prefer doing this in the UI, even for a large data set.

• What would be considered as a large data set?

Discussion - Microservice vs. Monolith systems

Searching for null/empty values

 UILISTS-87 Build queries that search for null / empty values

• Field is null/empty

• Field is not null/empty

• Field is null with another set of values

What should we call this feature?

Should we have separate operators (is NULL; is NOT NULL) or use NULL as a value?

• Group expresses preference for separate operators. However, developer support for additional operators is limited at this time.

• Developers explained that the option of using NULL as a value will not return a record with a NULL field.

  • ex: Query includes user_middle_name != ‘James’ will NOT return records where User's Middle Name is NULL/empty.

  • SQL requires query to user_middle_name != ‘James’ and IS NULL in order to return records where User's Middle Name is NULL/empty.

Bulk edit queries - follow up from Slack chat

Bulk Edit Queries Examples

Bulk Edit - in app approach - statistical codes - (UXPROD-3714)

Out of time...Magda will follow up in Slack channel.

1. What are the most common use cases for editing statistical codes?

2. Should bulk edit cover adding new statistical code types?

3. Should each element of the statistical codes be available for bulk editing?

4. How the data should be presented in Bulk edit forms (UI and .csv files)

5. Should bulk edit concentrate only on adding/removing/modifying statistical codes to instances, holdings and items records?

Errors and warnings 

1. Field level errors vs record level errors

2. Errors vs warnings

3. Before or after committing changes

Current implementation: Error message consistency: field level errors and warnings vs. record level errors and warnings