Uploaded image for project: 'FOLIO'
  1. FOLIO
  2. FOLIO-1331

Define and describe the architecture for how to keep data in sync across multiple apps

    XMLWordPrintable

Details

    • Core: Platform

    Description

      Purpose: Define process to keep data in sync seamless when exchanged and shared by two or multiple apps.

      NOTE: This ticket complements FOLIO-1273.

      This area is relevant for interaction between, e.g.:

      • the Acquisition app and Inventory, e.g. when a brief record is created in the Acquisition app, and then pushed to Inventory when the order is send to the vendor
      • the eHoldings app and Inventory app
      • the ERM app and Inventory app, e.g. selected holdings records
      • the Inventory > Item record and the Check in screen, and e.g. piece number, Piece Description, and condition data as missing and damaged items
      • the Inventory > Item record and the Check out screen, e.g. piece number, Piece Description, and condition data as missing and damaged items
      • the Courses > Reserves record and Inventory>Item
      • the Inventory > Item record and the Request Screen, e.g. Call number, Volume and Enumeration (UIREQ-81)
      • the MARC Batch Loader and various apps (SRS, Inventory, Acq (orders/invoices))
      • exchange of records between Inventory and SRS e.g.
        • bibliographic records created and maintained in quickMARC accessing the SRS MARC directly, and pushed to Inventory
        • holdings records maintained as MFHD - MARC 21 Format for Holdings Data, https://www.loc.gov/marc/holdings/ and then shared with Inventory > Holdings
      • eHoldings app and ERM app
      • eHoldings app and Order app
      • How does mod-source-storage interact with quickMARC and Inventory?
      • Do we need additional storage beyond mod-source-storage for MARC holdings?

      Documentation:

      TestRail: Results

        Attachments

          Issue Links

            clones

            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
            is cloned by

            Umbrella - FOLIO-1756 Define and describe the architecture for how to keep data in sync across multiple apps for partial record updates

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIU-2082 [BE] Data corruption. When holdings/item data are moved in Inventory, then the connected Fee/Fine is not updated accordingly

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

            New Feature - New feature requests UXPROD-127 A process is needed to periodically refresh the record against the source (Knowledge base)

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

            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-139 Avoid creation of duplicative metadata for eBooks

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

            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

            New Feature - New feature requests UXPROD-187 Receive Item and update details regarding availability

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

            New Feature - New feature requests UXPROD-689 Ability to update item record with call number when receiving

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            New Feature - New feature requests UXPROD-691 Allow Item status to be set during receiving process

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

            New Feature - New feature requests UXPROD-693 Ability to update item record with Barcode

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

            New Feature - New feature requests UXPROD-961 Allow Inventory Instances to generate purchase order and purchase order lines

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

            New Feature - New feature requests UXPROD-967 eholdings - Order Integration : Automatically select a title/package in KB and add to library's holdings

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

            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

            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

            New Feature - New feature requests UXPROD-1806 NFR: Data Import Pub-Sub (Event Driven) Infrastructure, part 1

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            New Feature - New feature requests UXPROD-2012 NFR: Data Import Pub-Sub (Event Driven) Infrastructure, part 2

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            New Feature - New feature requests UXPROD-2196 NFR: PubSub enhancements (BE)

            • P2 - normal priority level, must be included in the current development cycle
            • Open

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIREQ-589 [BE] Data corruption. When holding/item data are moved in Inventory, then the connected Request is not updated accordingly

            • 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. UIREQ-650 [BE] When inventory data (e.g. barcode, instance title) changes for requested item, request should update accordingly

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

            New Feature - New feature requests UXPROD-150 Automatic update of Bib records updated in the MARCcat module to metadata records in the Inventory via SRS (AtCult work)

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

            New Feature - New feature requests UXPROD-683 Create Instance Record in inventory for items ordered that are not currently represented in inventory

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

            New Feature - New feature requests UXPROD-684 Ability to create an Item Record in inventory for electronic items ordered not currently represented in inventory by an Item

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

            New Feature - New feature requests UXPROD-686 Create Item Record in inventory for physical items ordered that are not currently represented in inventory by an Item

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

            New Feature - New feature requests UXPROD-687 Create Holding Record in inventory for items ordered that are not currently represented in inventory by a Holding

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

            New Feature - New feature requests UXPROD-2473 Automatic update of Holdings records updated in the MARCcat module to metadata records in the Inventory via SRS (Scanbit work)

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

            New Feature - New feature requests UXPROD-2474 Automatic update of Authority records updated in the MARCcat module to SRS (Scanbit work)

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

            New Feature - New feature requests UXPROD-3399 When Relevant User Record Attributes are Updated, Synchronize Those Updates with the User's Requests Automatically

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

            Page Loading...

            Activity

              People

                Unassigned Unassigned
                charlotte Charlotte Whitt
                Votes:
                0 Vote for this issue
                Watchers:
                24 Start watching this issue

                Dates

                  Created:
                  Updated:

                  TestRail: Runs

                    TestRail: Cases