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

Push record updates to discovery service edge API

    XMLWordPrintable

    Details

    • Template:
      UXPROD features
    • Potential Workaround:
      Currently Discovery services can harvest via OAI-PMH or an export once export has been completed.
    • Front End Estimate:
      Medium < 5 days
    • Back End Estimate:
      XXL < 30 days
    • Estimation Notes and Assumptions:
      The estimates are based on similar work in RTAC, but adding addition time for holdings and instances. The medium front end effort is just in case some configuration settings are needed.
    • Development Team:
      None
    • Calculated Total Rank:
      29
    • Kiwi Planning Points (DO NOT CHANGE):
      30
    • PO Rank:
      25
    • PO Ranking Note:
      Ranking low as there are acceptable workarounds that have been in use for years in the industry. This is a "nice to have".
    • Rank: Chicago (MVP Sum 2020):
      R5
    • Rank: Cornell (Full Sum 2021):
      R4
    • Rank: Duke (Full Sum 2021):
      R2
    • Rank: 5Colleges (Full Jul 2021):
      R4
    • Rank: FLO (MVP Sum 2020):
      R2
    • Rank: GBV (MVP Sum 2020):
      R4
    • Rank: Lehigh (MVP Summer 2020):
      R2
    • Rank: MO State (MVP June 2020):
      R2
    • Rank: TAMU (MVP Jan 2021):
      R2
    • Rank: U of AL (MVP Oct 2020):
      R4

      Description

      Although FOLIO currently generates messages for every instance, item and holding record created or updated in the system, an edge API should be created that send records for an external discovery service that contains the record and the operation so the discovery service can make the change and update the index in near real time so patrons can see the changes ASAP.

        TestRail: Results

          Attachments

            Activity

              People

              Assignee:
              hkaplanian@ebsco.com Harry
              Reporter:
              hkaplanian@ebsco.com Harry
              Front End Estimator:
              Harry Kaplanian Harry Kaplanian
              Back End Estimator:
              Harry Kaplanian Harry Kaplanian
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:

                  TestRail: Runs

                    TestRail: Cases