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

When Relevant User Record Attributes are Updated, Synchronize Those Updates with the User's Requests Automatically

    XMLWordPrintable

Details

    • Vega
    • 0
    • R2

    Description

      Current situation or problem:

      Currently, mod-circulation-storage stores copies of certain user record field values in the request-storage record for both the requester and any proxy (if applicable):

      • firstName
      • lastName
      • middleName
      • barcode
      • patronGroup (currently deprecated)

      to enable search/sort in ui-requests. If the user record is modified, these values can become out-of-sync and make it impossible to get accurate results when using the current user barcode for search or when sorting request records by user barcode (UIREQ-673, CIRCSTORE-286). We need to update these stored values in the request storage record whenever the associated user record is updated.

      In scope

      • Define a mechanism to notify mod-circulation or mod-circulation-storage that user records have been updated
      • Define when/if to update the copied data
      • Consider un-deprecating patronGroup

      Out of scope

      Use case(s)

      Proposed solution/stories

      https://wiki.folio.org/display/DD/Eventual+consistency+for+duplicated+data

      Links to additional info

      Questions

      TestRail: Results

        Attachments

          Issue Links

            blocks

            Bug - A problem which impairs or prevents the functions of the product. UIREQ-673 "Sort results by barcode" does not sort properly

            • P4 - lowest priority level, nice-to have things that require future discussion and design
            • Closed
            relates to

            Bug - A problem which impairs or prevents the functions of the product. CIRCSTORE-286 "Sort results by barcode" does not sort properly

            • P2 - normal priority level, must be included in the current development 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

            Tech Debt - FOLIO-2473 When requester barcode is changed in Users, requests should update accordingly

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

            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

            Activity

              People

                brookstravis Brooks Travis
                brookstravis Brooks Travis
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:

                  TestRail: Runs

                    TestRail: Cases