Bulk Edit (UXPROD-868)

[UXPROD-3705] Bulk Edit - User data - in app approach Created: 09/Jun/22  Updated: 19/Dec/22  Resolved: 11/Oct/22

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Nolana (R3 2022)
Parent: Bulk Edit

Type: New Feature Priority: P2
Reporter: Magda Zacharska Assignee: Magda Zacharska
Resolution: Done Votes: 0
Labels: firebird-nolana
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by MODEXPW-232 users in-app approach: Download Users... Closed
is defined by MODEXPW-250 E-mail can be edited partially (not e... Closed
is defined by FEXPCMN-11 users-in-app-update: Create UserConte... Closed
is defined by FEXPCMN-12 users-in-app-update: Update ContentUp... Closed
is defined by MODEXPW-179 users-in-app-update: Create BulkEditU... Closed
is defined by MODEXPW-180 users-in-app-update: Update BulkEditC... Closed
is defined by MODEXPW-181 users-in-app-update: Update ITEMS con... Closed
is defined by MODEXPW-189 users-in-app-update: E-mails bulk-edi... Closed
is defined by MODEXPW-190 users-in-app-update: Content update v... Closed
is defined by MODEXPW-236 Improvements for users in-app approach Closed
is defined by UIBULKED-104 Bulk edit user records - in app permi... Closed
is defined by UIBULKED-105 Bulk edit user records - in app permi... Closed
is defined by UIBULKED-106 Patron group - User records -in app ... Closed
is defined by UIBULKED-107 Expiration date - User records - in ... Closed
is defined by UIBULKED-123 Email address - User records - in ap... Closed
is defined by UIBULKED-124 User-records - confirm changes - in app Closed
is defined by UIBULKED-125 User-records - commit changes - in app Closed
Relates
relates to UXPROD-3225 Bulk Edit - User data - Pilot Closed
Release: Nolana (R3 2022)
Epic Link: Bulk Edit
Front End Estimate: XXL < 30 days
Front End Estimator: Uladislau Samets
Front-End Confidence factor: 90%
Back End Estimate: XXL < 30 days
Back End Estimator: Viachaslau Khandramai (Inactive)
Back-End Confidence factor: 90%
Development Team: Firebird
PO Rank: 0
Rank: Cornell (Full Sum 2021): R3

 Description   

Current situation or problem:
In the Morning Glory release, user records can be updated using the CSV approach ( UXPROD-3225 Closed ) that allows user to download a CSV file with matching records, make locally changes and then upload the updated file. Such approach requires familiarity with FOLIO's data structure and awareness of the impact the changes will have on the system. A simpler approach was recommended by the community and also confirmed by the UX research. This feature will implement In-app approach to for editing selected fields from the user records will guide the user through all steps of the bulk edit in the Bulk Edit app.

In scope
1. Create a permission that is required for bulk editing of user records but is separated from the updates of the singular user records and bulk edits of other record types.

2. Identify records for the bulk edit based on:

  • a list of submitted identifiers (user barcodes, usernames, external IDs, and UUIDs)
  • a simple query

3. Support update of following fields:

  • patron group
  • expiration date
  • email address

4. Bulk edit functionality covered:

  • Identify records for editing by submitting a file with identifiers or building a simple query
  • Edit record(s): add new data, remove existing data, modify existing data
  • Review changes before they are committed
  • Confirm changes to be committed
  • Commit changes
  • Log committed changes
  • Log errors if encountered
  • Handle exception (including notifying users)

5. Modify Export Manager so that the files used in bulk edit (list of identifiers, query results, previews of records before the changes are committed, previews of records after the changes are committed, and list of errors):

  • can be accessed only by the users with required permissions
  • can be filtered by file type, date and time created and the status how the file was generated.

Out of scope
Bulk edits for the following user records related data:

  • User permissions edits - planned for Orchid release (R1 2023)
  • Tags - planned for Orchid release (R1 2023)
  • Custom fields - planned for Queen Ann's Lace (R3 2023)
  • Fees and fines - planned for Queen Ann's Lace (R3 2023)
  • Patron blocks - planned for Queen Ann's Lace (R3 2023)
  • Advanced search (single record) - planned for Orchid release (R1 2023)
  • Cross app queries - planned for Poppy and Queen Ann's Lace releases (R2, R3 2023)

Use case(s)

  1. Bulk update of patron information - use cases like extending expiration dates;
  2. update Expiration date in general (e.g. to make user inactive)
  3. update Patron group
  4. update based on a list of user barcodes, which needs to be uploaded
  5. Change e-mail address for all affected users when the institution domain changes
  6. Bulk edit expiration date for users. Criteria: Patron group, current expiration date, Blocking status, Department, Custom fields, etc.

Links to additional info

  1. Mockups: https://drive.google.com/drive/folders/1jPuVpr9R4F9BCbXRCHSGdan2ePSB_0nz
  2. Prioritized list of the user records fields marked for deletion: https://docs.google.com/spreadsheets/d/138eTmCiZbZ1F-kZL71_GsRR4zePNyuUG/edit#gid=165371240


 Comments   
Comment by Andrea Loigman [ 15/Jun/22 ]

Available simple queries should allow for identification by patron expiration date and patron group.  Should also allow for search for null in specific fields (e.g. create a list of patrons with no email address).

Comment by Taras Spashchenko [ 29/Aug/22 ]

This feature does not require architecture changes for the Bulk Edit functionality

Generated at Fri Feb 09 00:34:09 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.