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

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

    XMLWordPrintable

Details

    • Core: Platform

    Description

      Purpose: Define seamless exchange (push and pull) of

      • data in given elements in one app to given elements in another app, and also
      • handle excange of a complete record, e.g. being created in one app, and later maintained in another app.

      NOTE: This will imply determination of how we make sure data is in sync across apps - FOLIO-1331.

      Tech lead documentation: https://wiki.folio.org/display/DD/Data+consistency+and+message+driven+approach?focusedCommentId=65114576#comment-65114576

      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 Inventory > Item record and the Request Screen, e.g. Call number, Volume and Enumeration (UIREQ-81)
      • the Course Reserves record and Inventory > Item. Course > User
      • the Data Import and various apps (MARCcat, Inventory, Acq (orders/invoices)
      • PO lines and Pieces and their links to Instances, Holdings, and Items
      • exchange of records between Inventory and MARCcat
      • eHoldings app and ERM app
      • eHoldings app and Order app

      Documentation:

      TestRail: Results

        Attachments

          1. 1006.png
            1006.png
            1.35 MB
          2. 1007.png
            1007.png
            416 kB

          Issue Links

            is cloned by

            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
            relates to

            Umbrella - FOLIO-1712 PubSub support in FOLIO

            • 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. 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

            Umbrella - UXPROD-1647 Theme: Ability to maintain relationships between other apps when holdings/items are moved

            • 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-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-144 Assign Accession numbers to holdings and item records - when items are acquired

            • 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

            Activity

              People

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

                Dates

                  Created:
                  Updated:

                  TestRail: Runs

                    TestRail: Cases