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

A process is needed to periodically refresh the record against the source (Knowledge base)

    XMLWordPrintable

Details

    • Small < 3 days
    • Large < 10 days
    • Low
    • Large < 10 days
    • Hide
      Dependencies between the KB and Inventory; and the seamless push and pull of data between apps (FOLIO-1273) - there are som system design discussion to have here. How is this process for refresh to be scheduled? Will KB push this or will inventory pull it?
      Show
      Dependencies between the KB and Inventory; and the seamless push and pull of data between apps ( FOLIO-1273 ) - there are som system design discussion to have here. How is this process for refresh to be scheduled? Will KB push this or will inventory pull it?
    • Prokopovych
    • 1
    • 62
    • CW: PO rank aligned with Calculated Total rank.
    • R1
    • R5
    • R4
    • R4
    • R4
    • R4
    • R4
    • R4
    • R1
    • R1
    • R4
    • R1
    • R1
    • R4
    • R4

    Description

      Purpose: A process is needed to periodically refresh the record against the source (Knowledge base). Essentially, this is about defining how to keep update of eResources, which originate from the KB, and then have gotten a fuller description of the bibliographic record in Inventory (eResources in Inventory).

      Two use cases: updates to access information in holdings for selected titles (e.g., platform change, URL change) & updates to Instances – updates to Instances depends on first having ability to create Instances based on titles in KBs

      TestRail: Results

        Attachments

          Issue Links

            relates to

            New Feature - New feature requests UXPROD-138 Locally-stored metadata records for eResources in Inventory

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

            New Feature - New feature requests UXPROD-1080 Locally-stored metadata records for eResources in Inventory - part 2 (Holdings and Item record)

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

            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

            New Feature - New feature requests UXPROD-151 Ebook packages - relationship to individual title records in Inventory

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

            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

                charlotte Charlotte Whitt
                cboerema Cate Boerema
                Charlotte Whitt Charlotte Whitt
                Niels Erik Gilvad Nielsen Niels Erik Gilvad Nielsen
                Niels Erik Gilvad Nielsen Niels Erik Gilvad Nielsen
                Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                  Created:
                  Updated:

                  TestRail: Runs

                    TestRail: Cases