1 of 18

FOLIO Bulk Edit�Lotus update and Morning Glory plans

Magda Zacharska – EBSCO

3/10/2022

| www.folio.org

2 of 18

Agenda

Bulk Edit – Pilot project update
Demo
UX Research results
Morning Glory scope

| www.folio.org

3 of 18

Bulk Edit – Pilot Project

Planned for Lotus:

Search by user group, lists of barcodes
Edit: remove permissions, update expiration date, update patron group, update email

Delivered:

Identify records for updates by identifiers (barcodes, external Ids, usernames and UUIDs)
Identify records for updates base on a simple query (by status and patron group)
Update every field from the user record (but not linked records: permissions or fees and fines)

| www.folio.org

4 of 18

Bulk Edit – Pilot Project – Demo

Identify records by list of identifiers
Identify records by query
Download matching records and make the changes locally
Upload the file with the changes and commit the changes
Review errors

| www.folio.org

5 of 18

Bulk Edit – UX Research

The research was conducted by EBSCO’s UX Research, and it included FOLIO’s community members who represented Chalmers, Five Colleges, Stanford, University of Chicago, Cornell and Duke.

Summary of findings:

Long term approach: An in-app editor that cuts through the data-level noise is the best long-term option for user workflow and customer satisfaction

Short term approach: Users are likely to accept a csv-only editing solution IF

It is explicitly positioned as a stop-gap measure on the way to an in-app solution
A few features are put in place to reduce risk and increase feedback

| www.folio.org

6 of 18

Bulk Edit – Morning Glory

UAT of the approach implemented in Lotus
Moving toward in-app approach

UXPROD-3523 Item locations
UXPROD-3469 Item statuses

Performance testing

UXPROD-3543 Bulk Edit performance

Bugfixes of the functionality where CSV and in-app approach overlap

| www.folio.org

7 of 18

Mockups – Bulk Edit Item Records

| www.folio.org

8 of 18

List of supported identifiers for the item record

| www.folio.org

9 of 18

The file Item-barcodes.csv has been matched to 248 records.

A preview of records matched is shown.

Two errors are shown in the Errors accordion.

User proceeds to the “Actions” button.

| www.folio.org

10 of 18

The in app record edit form contains list of options and actions.

Rows can be added or removed

The top of the screen shows how many records will be affected and the name of the file used to identify the records.

The Options drop-down will include: Temporary item location, Permanent item location and Item status

The Actions drop-down will include Replace with and Clear field (for locations only)

| www.folio.org

11 of 18

Location column will let user select location using existing Location look-up plugin

| www.folio.org

12 of 18

The user can narrow down the location starting with Institution, followed by campus and library.

| www.folio.org

13 of 18

Here temporary and permanent location will be updated.

Once the data edits are defined, confirm changes button is enabled.

Clicking the Cancel button will take the user back to the landing page.

| www.folio.org

14 of 18

List of supported item statuses – consistent with Inventory item records updates.

The Clear field action will not be supported for Item status updates.

| www.folio.org

15 of 18

Before the changes are committed to the database, the user will get another notification.

Here the user can see again how many records will be affected.

The Download Preview button and will let the user download the records with the proposed changes before they are committed to the database.

| www.folio.org

16 of 18

Once the changes are saved in the database, the user receives a success message at the top of the record for added emphasis.

Error information regarding the file that they just uploaded is displayed.

| www.folio.org

17 of 18

Bulk Edit – Additional information

https://folio-project.slack.com/archives/C02FSGFL6EQ

| www.folio.org

18 of 18

Questions?

| www.folio.org