[UXPROD-2734] Bulk APIs for Users module Created: 07/Oct/20  Updated: 20/Jun/23

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None

Type: New Feature Priority: TBD
Reporter: Ian Walls Assignee: Ian Walls
Resolution: Unresolved Votes: 0
Labels: bulk-api, usermanagement
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
is blocked by UXPROD-2818 RMB Work to Support Bulk Delete APIs Closed
Defines
is defined by MODUSERS-228 Bulk Create/Update API for users Open
is defined by MODUSERS-122 DELETE /users with CQL Closed
is defined by MODUSERS-229 Bulk DELETE API for users Draft
Relates
relates to UXPROD-2731 Improvements to User loader - additio... Open
relates to UXPROD-2732 Improvements to User loader - protect... Closed
relates to UXPROD-242 Ability to Protect Fields from Being ... Draft
relates to UXPROD-2320 Improvements to User loader - source ... Draft
relates to DEBT-3 Slow or missing batch upload/download... In Review
Back End Estimate: Large < 10 days
Back End Estimator: Marc Johnson
Estimation Notes and Assumptions: CB: Talking to Marc and entering his estimate. He thinks each one of these is about a sprint per dev.
Development Team: None
Kiwi Planning Points (DO NOT CHANGE): 15
PO Rank: 95
PO Ranking Note: Essential for large institutions, as this data will likely need not only to be loaded initially, but updated regularly from an external source of truth.
Rank: Chalmers (Impl Aut 2019): R2
Rank: Chicago (MVP Sum 2020): R2
Rank: Cornell (Full Sum 2021): R2
Rank: Duke (Full Sum 2021): R2
Rank: 5Colleges (Full Jul 2021): R2
Rank: GBV (MVP Sum 2020): R2
Rank: MO State (MVP June 2020): R2
Rank: U of AL (MVP Oct 2020): R1

 Description   

Current situation or problem:

In order to facilitate migrations and bulk record changes in a timely and efficient manner, the Users module needs to have batch APIs. POSTing, PUTting and DELETEing records one HTTP request and database commit at a time is unusably slow for large data sets.

In scope:

  • Bulk Create/Update for Users
  • Bulk Delete (with CQL query parameters) for Users

Out of scope:

Batch APIs for usergroups, addresstypes and departments. The anticipated order of magnitude for these record sets is not sufficient to require batch handling. The individual record APIs are sufficient.

Use case(s):

  • Initial Data Migration, including iterative data load/delete, WITHOUT deleting important user records like admin account(s)
  • Regular data updates from an external source of truth
  • Patron anonymization in accordance with institutional policy

Questions:

Are proxies used in large enough record sets for implementing libraries to merit the creation of batch APIs for this record type?



 Comments   
Comment by Cate Boerema (Inactive) [ 19/Oct/20 ]

Adding Core Functional as the dev team here since we officially own this module. I assume these will be done by the team owning the module.

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