[UXPROD-2739] Bulk APIs for Organizations Storage Module Created: 07/Oct/20  Updated: 05/May/21

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
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 MODORGSTOR-87 Bulk Create/Update API for organizations Open
is defined by MODORGSTOR-88 Bulk DELETE API for organizations Open
is defined by MODORGSTOR-89 Bulk Create/Update API for contacts Open
is defined by MODORGSTOR-90 Bulk DELETE API for contacts Open
Development Team: None
Kiwi Planning Points (DO NOT CHANGE): 5
PO Rank: 60
PO Ranking Note: Could be a large data set, but not likely to need regular updating in bulk
Rank: Chalmers (Impl Aut 2019): R4
Rank: Chicago (MVP Sum 2020): R3
Rank: Cornell (Full Sum 2021): R3
Rank: Duke (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R4
Rank: GBV (MVP Sum 2020): R2
Rank: U of AL (MVP Oct 2020): R5

 Description   

Current situation or problem:

In order to facilitate migrations in a timely and efficient manner, the Organizations Storage 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 Organizations
  • Bulk Delete (with CQL query parameters) for Organizations
  • Bulk Create/Update for Contacts
  • Bulk Delete (with CQL query parameters) for Contacts

Out of scope:

Batch APIs for addresses, phone number, urls and categories are not required. The anticipated order of magnitude for these record sets is not sufficient to require batch handling, and they appear to be deprecated in their individual APIs anyway.

Use case(s):

  • Initial Data Migration, including iterative data load/delete
  • Updating with an external source of truth

Comments:

In order for these APIs to be effective, they need to bypass the business logic and go directly to the storage module. Any BL-level logic will need to be accounted for by the user; documentation should reflect this.


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