15 min | Update on Bulk delete user records | Magda | - Nolana will have a simple query to identify records for deletion (Nolana development begins July 1. Release in December 2022.)
- Query by identifier or write a simple query (i.e., Patron Group="Faculty")
- Use case: Query by Expiration Date; Magda will experiment and test.
- soft delete for user records is out of scope (soft delete = marking the record for deletion but not actually deleting it)
- option to preview records to be deleted prior to deletion; can download .csv file before deletion. Deleted records are stored in Export Manager (in case you forget to save the .csv file before deleting records.)
- no dependencies => records will be removed from system
- using functionality in place in Users app (Kiwi)
- records with dependencies will be reported in error log; information about affected records and short description of problem to resolve before deletion can occur.
- Bulk Edit Delete User Records requires permission independent of users delete permissions granted for single record deletion.
- Scheduled patron notices may be impacted by bulk edit delete of user records or item records. Magda will reach out to Julie Bickle (PO - patron notices).
- Discussion re: user records with dependencies; Can we still see open loans if user record is (soft) deleted?
Documentation suggestion: Include list of query options in Bulk Edit. - Bulk Edit - User data - in-app approach for user records (Magda Z.)
- UXPROD-3705 (https://folio-org.atlassian.net/browse/UXPROD-3705)
- functionality expected in Nolana
- Bulk edit for: Patron Group, Expiration Dates, Email Address
- Can we search for null fields?
Scheduled patron notices may be impacted by bulk edit delete of user records or item records. Magda will reach out to Julie Bickle (PO - patron notices). Nolana development begins July 1. Release in December 2022. Discussion re: user records with dependencies; Can we still see open loans if user record is (soft) deleted? |