[MODBULKED-24] Bulk delete users Created: 05/Feb/22  Updated: 16/Jun/22

Status: In Refinement
Project: mod-bulkedit
Components: None
Affects versions: None
Fix versions: None

Type: Story Priority: P3
Reporter: Magda Zacharska Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
defines UXPROD-3230 Bulk delete user records In Refinement
Relates
relates to UXPROD-2728 Delete user through the API with chec... Closed
relates to MODUSERS-229 Bulk DELETE API for users Draft
Sprint:
Development Team: Firebird
RCA Group: TBD

 Description   

Purpose/Overview:

Delete users and corresponding data based on provided list of users.  The record deletion should honor existing business rules that prevent deletion of the user with open transactions. 

Assumption: dependencies are implemented on the backend and can be used by bulk edit.

Requirements/Scope:

  1. User records and depending data (loans, requests, fees/fines, proxies, manual blocks) 
  2. Users with open loans open requests, unpaid fees/fines, unexpired proxies and manual blocks are not deleted and those records are reported in the logs. T
  3. The log contains record identifier, first and last names and the reason why the record could not be removed:
  • If the deletion was triggered by submitting user barcodes the logs identifies records that could not be deleted by barcode
  • If the deletion was triggered by submitting usernames the logs identifies records that could not be deleted by usernames
  • If the deletion was triggered by submitting user external Ids the logs identifies records that could not be deleted by external id
  • If the deletion was triggered by submitting UUIDs the logs identifies records that could not be deleted by UUIDs
  • The log contains the reason why the record could not be deleted (open unexpired proxy, open loans, open requests, open blocks)
  • Only users with the "Bulk Edit - Delete - User records" permission are able to delete user records

Approach:

Acceptance criteria:

  • User records without open transactions are deleted
  • User records with open transactions are not deleted
  • Records that cannot be deleted are reported in the error logs 
  • API and unit tests are written

 Additional information:
The existing APIs for deleting user records handle dependencies but this will need to be verified


Generated at Thu Feb 08 22:30:36 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.