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

eholdings - Order Integration : Automatically select a title/package in KB and add to library's holdings

    XMLWordPrintable

Details

    • Medium < 5 days
    • Large < 10 days
    • Low
    • Small < 3 days
    • Dependency - Orders app work
    • Spitfire
    • 1
    • 85
    • R4
    • R4
    • R4
    • R4
    • R2
    • R4
    • R5
    • R4
    • R2
    • R4
    • R1
    • R2
    • R1
    • R4
    • R4

    Description

      To streamline workflow, if an order contains a electronic resource then automatically activate electronic resource in KB based on an order status.

      Integration should handle

      • User manually associate an electronic resource to a POL AND matching an eResource on POL generated via an order feed to an electronic resource in KB
      • Select title and/or package in the KB and add to the library's eholdings
      • Send applicable order detail to eholdings
      • Check coverage date on order matches KB managed coverage date. If no match then populate custom coverage in the eholdings app
      • Provide details to eHoldings when title or package orders has lapsed or been cancelled.
      • no clashes between order integrations that already existing with KB used by library

      For EBSCO KB customers, note that ESS already supports AND GOBI capability should be in place before fall.

      TestRail: Results

        Attachments

          Issue Links

            is cloned by

            New Feature - New feature requests UXPROD-968 eholdings - ERM Integration

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            relates to

            Umbrella - FOLIO-1273 Define and describe the architecture for seamless push and pull of data between apps (interaction)

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Open

            Umbrella - FOLIO-1331 Define and describe the architecture for how to keep data in sync across multiple apps

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Open

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODKBEKBJ-123 Spike: Orders App: Allow user to search KB for packages/titles

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODKBEKBJ-124 Spike: Orders App: Store mod-kb-ebscojava metadata

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UXPROD-1297 Populate Newly Created Container Record with KB metadata

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Open

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UXPROD-1298 Inventory App: Container Record: KB updates metadata

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Blocked

            Activity

              People

                kgambrell Khalilah Gambrell
                kgambrell Khalilah Gambrell
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:

                  TestRail: Runs

                    TestRail: Cases