[UXPROD-2736] Bulk APIs for FeesFines 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 MODFEE-127 Bulk Create/Update API for accounts Open
is defined by MODFEE-128 Bulk DELETE API for accounts Open
is defined by MODFEE-129 Bulk Create/Update API for feefines Open
is defined by MODFEE-130 Bulk DELETE API for feefines Open
Development Team: None
PO Rank: 80
PO Ranking Note: Important financial information that could be extensive
Rank: Chalmers (Impl Aut 2019): R3
Rank: Chicago (MVP Sum 2020): R2
Rank: Cornell (Full Sum 2021): R2
Rank: Duke (Full Sum 2021): R3
Rank: 5Colleges (Full Jul 2021): R4
Rank: GBV (MVP Sum 2020): R3
Rank: U of AL (MVP Oct 2020): R3

 Description   

Current situation or problem:

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

Out of scope:

Batch APIs for policies, settings, and owners are not required. 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

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