Users App (UXPROD-784)

[UXPROD-2013] Purge user file based on various data types Created: 23/Aug/19  Updated: 20/Sep/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Users App

Type: New Feature Priority: TBD
Reporter: patty.wanninger Assignee: Amelia Sutton
Resolution: Unresolved Votes: 0
Labels: usermanagement
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Epic Link: Users App
Development Team: None
Kiwi Planning Points (DO NOT CHANGE): 1
Rank: Chalmers (Impl Aut 2019): R3
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R4
Rank: GBV (MVP Sum 2020): R2
Rank: Grand Valley (Full Sum 2021): R4
Rank: hbz (TBD): R2
Rank: Lehigh (MVP Summer 2020): R4
Rank: TAMU (MVP Jan 2021): R4
Rank: U of AL (MVP Oct 2020): R3

 Description   

Libraries have the need to purge their user file of records that are inactive or expired based on a number of criteria such as last activity date, expiration date, or date of registration, or some other combination.

A "user purge" should remove the record from the user file completely.



 Comments   
Comment by Marie Widigson [ 14/Apr/21 ]

Should this relate to UXPROD-2728 (Delete user through the API with check for open transactions (API, Single user)?

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