Users App (UXPROD-784)

[UXPROD-2728] Delete user through the API with check for open transactions (API, Single user) Created: 05/Oct/20  Updated: 05/Feb/22  Resolved: 24/Jun/21

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Kiwi (R3 2021)
Parent: Users App

Type: New Feature Priority: TBD
Reporter: patty.wanninger Assignee: Annika Schröer
Resolution: Done Votes: 0
Labels: usermanagement
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by MODUSERBL-115 Create a list of open transactions wh... Closed
is defined by MODUSERBL-116 Report on open transactions that prev... Closed
Relates
relates to UXPROD-2904 Run open transactions check w/o delet... Closed
relates to UXPROD-2388 Delete user through the UI with check... Closed
relates to MODBULKED-24 Bulk delete users In Refinement
Epic Link: Users App
Development Team: Leipzig
Kiwi Planning Points (DO NOT CHANGE): 20
Rank: Chalmers (Impl Aut 2019): R2
Rank: Chicago (MVP Sum 2020): R3
Rank: Cornell (Full Sum 2021): R3
Rank: Duke (Full Sum 2021): R3
Rank: 5Colleges (Full Jul 2021): R3
Rank: GBV (MVP Sum 2020): R1
Rank: Grand Valley (Full Sum 2021): R3
Rank: Leipzig (Full TBD): R1
Rank: MO State (MVP June 2020): R3
Rank: U of AL (MVP Oct 2020): R3

 Description   

As a system administrator with API access, I would like to have the Users API verify that only users without open transactions can be deleted. The API must run a transaction check before deletion to detect the following open transactions which are potentially attached to the  single user (with given user id).

 I want to delete:

  • open loans
  • open requests
  • unpaid fees/fines
  • unexpired proxy
  • manual blocks (automated should be covered by open loans or fees/fines)

The user can be active or inactive. Deletion will remove the entire record from the system.

I need a list of open transactions whose presence will prevent deletion for further processing, which is part of MODUSERBL-115 Closed



 Comments   
Comment by Lisa Sjögren [ 05/Nov/20 ]

This will be especially important in the case of e.g. annual deletion of all users who have been inactive for a certain period of time (in order to not store unnecessary personal data), where you will not be able to manually check dependencies.

Comment by Erin Nettifee [ 25/Nov/20 ]

There's already a delete user API - DELETE /users/

{userid}

- how is this different than what exists now? Does that API not check for dependencies?

Comment by Björn Muschall [ 26/Nov/20 ]

Erin Nettifee We already discussed, just for documentation: The API does not check for dependencies at the moment.

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