Users App (UXPROD-784)

[UXPROD-2388] Delete user through the UI with check for open transactions (UI, Single user) Created: 21/Apr/20  Updated: 19/Sep/22  Resolved: 30/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 UIU-1971 Delete user through the UI with check... Closed
is defined by UIU-2192 Delete user through UI: change dialog... Closed
is defined by UIU-2193 Delete user through the UI: confirmat... Closed
Relates
relates to STCOM-882 Additional functionality needed for m... Closed
relates to UXPROD-2728 Delete user through the API with chec... Closed
relates to UXPROD-2904 Run open transactions check w/o delet... Closed
relates to UIU-1079 Not able to delete inactive user thro... Closed
Epic Link: Users App
Development Team: Leipzig
Kiwi Planning Points (DO NOT CHANGE): 21
Rank: BNCF (MVP Feb 2020): R2
Rank: Chalmers (Impl Aut 2019): R2
Rank: Chicago (MVP Sum 2020): R5
Rank: Cornell (Full Sum 2021): R3
Rank: Duke (Full Sum 2021): R2
Rank: 5Colleges (Full Jul 2021): R4
Rank: GBV (MVP Sum 2020): R2
Rank: Grand Valley (Full Sum 2021): R3
Rank: Leipzig (Full TBD): R1
Rank: MO State (MVP June 2020): R4
Rank: U of AL (MVP Oct 2020): R3

 Description   

As a service staff membe*r with the proper permissions I wants to be able to delete *a user through the UI.

When the user has no open transactions attached to it, including open loans, open requests, open fees/fines, unexpired proxies or blocks, the user can be deleted.  The list of relevant open transactions is defined in MODUSERBL-115 Closed .

Otherwise an information should be given with information about the open transactions  (UI details in UIU-1971 Closed ). The user can be active or inactive.



 Comments   
Comment by Erin Nettifee [ 25/Nov/20 ]

Comment from Andrea Loigman: "In basic user stories, we’d want designated access services staff to be able to delete a mistakenly created or duplicate patron record via the UI. The same is true if we’re using ‘pseudo’ patrons in order to facilitate interlibrary loan and workflow processes that might otherwise rely on a workflow engine or complex item states. It’ll be a mess if we have to go to our IT staff every time someone makes an error or a consortial partner or internal department changes.
So short answer - Yes we need this and it needs a permission separate from the ones to create, update or view patron records. I’m assuming the ‘no information’ clause is about current circs, fines, etc. and not historical ones. Also that data like addresses, emails, etc. wouldn’t stop a deletion. I’m not sure why blocks should stop a deletion."

Comment by Uschi Klute [ 27/Nov/20 ]

in the User Management SIG we have agreed that these points should be taken into account:

  • open loans
  • open requests
  • unpaid fees/fines
  • unexpired proxy
Comment by Lisa Sjögren [ 27/Nov/20 ]

Hi Uschi Klute! A propos dependencies, how would references to the deleted user in the metadata element of other records be handled? I.e. createdByUserId and updatedByUserId.

That would be an inevitable dependency for pretty much any staff user who has ever performed any sort of action in FOLIO.

Comment by Uschi Klute [ 27/Nov/20 ]

Hi Lisa Sjögren if I remember correctly, we had thought that it then should simply say "deleted user".
patty.wanninger: do I remember correctly?

Comment by Erin Nettifee [ 11/Mar/21 ]

Hi - is this planned for R2 or R3?

Comment by Lisa Sjögren [ 31/Mar/21 ]

Another dependency question: should linked permissionsUsers and credentials also be deleted when a user is deleted, or is it ok to leave them in the system? 

Comment by Björn Muschall [ 01/Apr/21 ]

Good question, Lisa Sjögren. The UM SIG also run into the question of data fragments that remain in the system after a user record has been deleted. Besides permissionsUsers and credentials we discovered that, for example, in

  • mod_feesfines.ACCOUNTS
  • mod_feesfines.COMMENTS
  • mod_feesfines.FEEFINEACTION
  • mod_feesfines.PAYMENTS
  • mod_circulation_storage.AUDIT_LOAN
  • mod_circulation_storage.REQUEST

data fragments are retained when the user is deleted. However, this ticket only covers Transactions checks. The issue of data fragments was discussed in the App Interaction SIG, as this is an overarching one. However, I do not remember the outcome of the discussion. Maybe we could come to some kind of regular cleanup routine or the deletion of particular records will entail the deletion of other data (which may be more difficult as it is cross-module).

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