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

[UXPROD-3342] Implement data consistency approach for Piece<>Item interaction Created: 27/Sep/21  Updated: 28/Mar/23  Resolved: 28/Mar/23

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Orchid (R1 2023)
Parent: Ordering functionality that FOLIO needs to stay competitive

Type: New Feature Priority: P2
Reporter: Dennis Bridges Assignee: Dennis Bridges
Resolution: Done Votes: 0
Labels: acq-morningglory-candidate, acquisitions, kafka
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
is cloned by UXPROD-3879 Implement data consistency approach f... Open
Defines
is defined by MODORDERS-807 Copy number does not get applied to i... Closed
is defined by MODORDERS-569 Implement logic for updating Item fie... Closed
is defined by UIREC-148 Data consistency - Update Item when p... Closed
Relates
relates to UXPROD-1647 Theme: Ability to maintain relationsh... Open
Epic Link: Ordering functionality that FOLIO needs to stay competitive
Front End Estimate: Medium < 5 days
Front-End Confidence factor: 80%
Back End Estimate: XL < 15 days
Back-End Confidence factor: 50%
Estimation Notes and Assumptions: We need to think about splitting stories based on Moving item vs moving Holdings.
Development Team: Thunderjet
PO Rank: 55
Rank: Cornell (Full Sum 2021): R2
Solution Architect: Raman Auramau

 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 into UXPROD-3879 to separate the synchronization of updates flowing from receiving to inventory and the updates flowing from inventory to receiving. This feature will represent updates flowing from receiving to inventory.

Comment by Dennis Bridges [ 28/Mar/23 ]

All stories resolved for release in Orchid

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