2024-02-06 BELA Meeting Notes

Housekeeping

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

• Please respond to the survey for bulk editing instances. The deadline is next Friday, February 16th.

• Who can take notes today?

 Quesnelia release update

• Bulk edit (Kanban Board) 

• Bulk edit demos:

  • Uploading a file with 300 users - you're now able to see the entire record set via pagination, as well as see the top 10 errors

    • Pagination through records continues through all screens

    • the errors accordion can be collapsed to see the preview full-screen

    • Feedback: under actions - download errors should be renamed to 'download all errors' since it's not limited to the top 10 errors that are displayed

    • Question: does the preview of records matched contain records with errors? in this case,, the provided records had 'no match found' and therefore would not be included in the matched records

  • Backend integration with Lists backend is almost complete for the 'Query' portion of bulk edit

    • Demo using 'Users' where you can create your query, test the query and see results. 'Run query' doesn't work yet as there's still some additional front-end work required.

    • Initial support for building Bulk Edit for 'Users' and 'Item' records. Once the backend work is complete in the Lists app, 'Holdings' and 'Instances' will also be supported

    • Question: Will there be a possibility of mixing and matching of records for Bulk Edit? Not in the Q release, or in the next few releases. There are, however, some fields that cross records when searching/building a list.

• Lists app

  • No demo as much of the recent work has been backend work to enable upcoming functionality 

Searching for null/empty values - follow-up

Implementation of a new 'Is empty/null' operator: https://folio-org.atlassian.net/browse/UIPQB-76

Errors and warnings  - continued

1. Field level errors vs record level errors

   1. agreement that there should be info at both the record level and the field level

2. Errors vs warnings

   1. desire to provide a better summary that will differentiate between errors and warnings

   2. agreement that that fields that don't change in value should appear as warning rather than errors

3. Before or after committing changes

   1. Idea to introduce messaging prior to committing changes - Are you sure - # of records changed, # of field value changes, # of fields with no value changes

Current implementation: Error message consistency: field level errors and warnings vs. record level errors and warnings (from Slide 4) 

Notes:

• Need enough info to understand how to troubleshoot these errors. @Magda Zacharska created a page that provides additional info: Bulk Edit error and warnings  

• Concrete error message that let the user know what the issue is would be the most beneficial, and especially if we’re able to get that information now. Making it friendly is great, but not if we means we can’t get any info for several releases.

• Question: Does the report show what the previous fields were, and what the updated fields were? No.  This might be useful to have in the report, rather than on the other screen. Notice the options from the logs. There’s not a summary but you can export several CSVs (see screenshot) – if there are errors, you can see that information 

  
  
  

Bulk edit queries - follow up from Slack chat

Bulk Edit Queries Examples

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

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?