Details
-
New Feature
-
Status: Draft (View Workflow)
-
P3
-
Resolution: Unresolved
-
None
-
None
-
None
-
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
-
UIREQ-673 "Sort results by barcode" does not sort properly
-
- Closed
-
- relates to
-
CIRCSTORE-286 "Sort results by barcode" does not sort properly
-
- Closed
-
-
FOLIO-1273 Define and describe the architecture for seamless push and pull of data between apps (interaction)
-
- Open
-
-
FOLIO-1331 Define and describe the architecture for how to keep data in sync across multiple apps
-
- Open
-
-
FOLIO-2473 When requester barcode is changed in Users, requests should update accordingly
-
- Blocked
-
-
UXPROD-1647 Theme: Ability to maintain relationships between other apps when holdings/items are moved
-
- Open
-