Ordering functionality that FOLIO needs to stay competitive (UXPROD-3440)

[UXPROD-3879] Implement data consistency approach for Item<>Piece interaction Created: 25/Oct/22  Updated: 20/Nov/23

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Ordering functionality that FOLIO needs to stay competitive

Type: New Feature Priority: P2
Reporter: Dennis Bridges Assignee: Dennis Bridges
Resolution: Unresolved Votes: 0
Labels: acquisitions, kafka, split
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
clones UXPROD-3342 Implement data consistency approach f... Closed
Defines
is defined by MODORDERS-559 Spike : Analyze domain event pattern ... Open
is defined by MODORDSTOR-303 Implement Kafka event consumer in mod... Open
is defined by MODORDSTOR-304 Implement logic for updating Piece fi... Open
is defined by UIREC-225 Data consistency - Update Piece when ... Blocked
is defined by MODORDERS-642 Data corruption. When holding/item da... In Refinement
Relates
relates to UXPROD-1647 Theme: Ability to maintain relationsh... Open
Epic Link: Ordering functionality that FOLIO needs to stay competitive
Development Team: Thunderjet
PO Rank: 55
Rank: Cornell (Full Sum 2021): R2

 Description   

Overview:

Receiving updates in UXPROD-2373 Closed and UXPROD-1925 Closed have added additional reference points between orders and inventory records. They have also added fields to the piece record that must be reflected in related item records. When user edits these fields in either the item or the piece record the other must be updated so the data remains consistent in both modules.

Use cases:

See wiki page: https://folio-org.atlassian.net/wiki/x/zQ1U 

Approach

See MIRO Board



 Comments   
Comment by Dennis Bridges [ 25/Oct/22 ]

This was split from UXPROD-3342 Closed to separate the synchronization of updates flowing from receiving to inventory and the updates flowing from inventory to receiving. This will represent updates flowing from inventory to receiving.

Comment by Kristin Martin [ 15/Nov/23 ]

Hello, we had a Slack conversation about this in September/October 2023: we load records and orders and some vendors provide copy number with the full cataloging which we load into the item record. However, when we receive something, that removes the information in the item record, because the copy number field is blank in the piece record to be received. This behavior is expected but undesirable for us since we end up erasing desired data and having to redo the work. The reason this works this way is that the Piece<>Item interaction has been completed, but the Item<>Piece interaction has not. Dennis Bridges suggested, "We may be able to address this with a smaller change. Eg. if the copy number field is null in the piece, do not update that field in the item." We would like to see that change if this larger functionality will not be implemented for some time. Is there a Jira for that?

Comment by Dennis Bridges [ 20/Nov/23 ]

A story was created to address the previous comment https://folio-org.atlassian.net/browse/MODORDERS-970. This is not assigned to this feature as it does not define updating piece information from item. Rather it is being treated as an enhancement to how Piece edits update item records.

Generated at Fri Feb 09 00:35:31 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.