Issues

Select view

Select search mode

 
29 of 29

Implement data consistency approach for Item<>Piece interaction

Description

Overview:

Receiving updates in and 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

Update May 16, 2024: Need to re-evaluate in the context of bindery support and updated RTAC model.

Priority

Fix versions

None

Development Team

Thunderjet

Assignee

Solution Architect

Parent Field Value

None

Parent Status

None

Checklist

hide

TestRail: Results

Details

Reporter

PO Rank

0

Rank: Cornell (Full Sum 2021)

R2

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created October 25, 2022 at 9:32 PM
Updated February 6, 2025 at 1:39 PM

Activity

Show:

Dennis Bridges November 20, 2023 at 4:56 PM

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.

Kristin Martin November 15, 2023 at 12:20 PM

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

Dennis Bridges October 25, 2022 at 9:39 PM

This was split from 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.

TestRail: Cases
TestRail: Runs
Loading...