| Time | Item | Who | Notes |
|---|
| General discussion of deleting users as it is | Björn M. | - Some deletion functions exist. Users can delete a user
through the UI or through the API (mod-users, not user-import) while dependencies exist on the record. - Definition of term "dependencies": Loans, fees/fines, holds, requests, etc. Basically, unresolved items that exist in other modules.
- Some will want to have a record of what user edited a user record.
- The ability to delete a user record must be defined by a specific permission.
- Basic description of wanted behavior: We want to be able to delete a user, but only if the user has no dependencies. If they have dependencies, there should be a message telling the user to clear the dependencies first. This function should be set so that the delete command can't override the presence of dependencies.
|
| UXPROD-2388 (Delete inactive user through UI) | Björn M. | - Does this user have to be inactive? Perhaps there should be a pop-up advising the staff member that the user is not inactive.
- User deletion should have a pop-up when they encounter a user with dependencies; and it should have a pop-up saying, essentially, "Are you sure?" before committing the deletes.
|
| UXPROD-2728 (Delete inactive user through API with dependency check) | Björn M. | - It is assumed that the API delete would work on multiple users in a batch.
- Currently, in mod-user on github, there is a delete user function with no dependency checks and no warnings.
- A deletion call in the API should not stop if it encounters a record with dependencies attached.
- A user deletion should fail in the API if there are dependencies attached.
- Perhaps we should get a list of the dependencies when a user deletion fails.
- Can we get a log of failed deletions?
- The program that invokes the API call should be able to log failed deletions.
- Bulk deletion of users through the API is actively being worked on in FOLIO.
- Action item: Identify all of the modules where there might be dependencies in a User record. (Which and how.)
|
| More general discussion of user deletion | Björn M. | - We should retain a "last update" date for the transaction in the metadata. Keep the "last update," delete the user. The metadata should retain the UUID of the user, but not the user name. The user name should be replaced with "delete user" or something similar.
- Action item: Patty will write the User Stories and review with Cate.
|
| Updates | Patty W. | - Adding multiple external system IDs has been pushed to Iris.
- UXPROD-242 (protects fields from being overwritten by bulk load of users) - Patty wants to push for this.
- There is a JIRA ticket for hiding "stalker data".
- UXPROD-2569 (Report of active borrowers in a calenar year) - We all need to rank this issue.
|