Bulk Edit (UXPROD-868)

[UXPROD-3225] Bulk Edit - User data - Pilot Created: 19/Aug/21  Updated: 09/Jun/22  Resolved: 20/May/22

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Bulk Edit

Type: Umbrella Priority: P2
Reporter: Magda Zacharska Assignee: Magda Zacharska
Resolution: Done Votes: 0
Labels: bulk-edit-pilot
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: Microsoft PowerPoint FOLIO Proposed Bulk Edits - Short.pptx     File bulk edit - pilot-v0.3.bmpr    
Issue links:
Defines
is defined by UXPROD-3228 Preliminary work for Bulk Edit app Closed
is defined by UXPROD-3229 Identify user records for bulk edit Closed
is defined by UXPROD-3318 User records - bulk edit - pilot impl... Closed
Relates
relates to UXPROD-3705 Bulk Edit - User data - in app approach Closed
Epic Link: Bulk Edit
Development Team: Firebird
PO Rank: 0

 Description   

Current situation or problem:
The functionality of the bulk edit is long overdue in FOLIO but because or its impact on the data integrity we will start with a pilot project that covers some of the use cases related to the user management.

In scope
1. Limited bulk edit for user records:

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

2. Cover all elements related to bulk edit workflow (even if only limited form):

  • Identify records for editing
  • Edit record(s): add data, remove data, update data
  • Review changes
  • Confirm changes
  • Commit changes
  • Log committed changes
  • Handle exception (including notifying users)

3. Review the finished pilot with the community (PC, TC)
4. Recommend implementation plan for other areas

Out of scope

  • Implementing bulk edit functionality for other functional area that will be addressed after the pilot is completed
  • Cross app searches
  • Bulk deleting records

Use case(s)

  1. Change e-mail address for all affected users when the institution domain changes

Links to additional info

Questions
Once the pilot is completed who gives OK for further implementation?



 Comments   
Comment by Erin Nettifee [ 19/Oct/21 ]

Mentioned in the bulk edit WG but also adding here - the permissions edit use case introduces significant complexity to this because permissions users are their own type of record — I think the pilot should focus simply on the user record - the other functions (patron group, expiration date, email) are all on the core user record.

There is also a separate uxprod for permissions management (https://folio-org.atlassian.net/browse/UXPROD-3159) that is relevant to the use case here.

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