Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-2734

Bulk APIs for Users module

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Open (View Workflow)
    • Priority: TBD
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Template:
      UXPROD features
    • Back End Estimate:
      Large < 10 days
    • 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
    • Calculated Total Rank:
      45
    • 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?

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                sekjal Ian Walls
                Reporter:
                sekjal Ian Walls
                Back End Estimator:
                Marc Johnson Marc Johnson
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases