Requests (UXPROD-790)

[UIREQ-650] [BE] When inventory data (e.g. barcode, instance title) changes for requested item, request should update accordingly Created: 20/Sep/19  Updated: 23/Oct/23

Status: Open
Project: ui-requests
Components: None
Affects versions: None
Fix versions: None
Parent: Requests

Type: Story Priority: P3
Reporter: Cate Boerema (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: backend, chalmers-dress-rehearsal, data-sync, keep-bug
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
is cloned by FOLIO-2473 When requester barcode is changed in ... Closed
is cloned by UIIN-821 Clicking request queue link in item r... Closed
is cloned by CHAL-188 Request placed on item without barcod... Blocked
Duplicate
is duplicated by UIREQ-327 Barcode should replace folio ID when ... Closed
Relates
relates to FOLIO-1273 Define and describe the architecture ... Open
relates to FOLIO-1331 Define and describe the architecture ... Open
relates to UIREQ-589 [BE] Data corruption. When holding/it... Open
relates to CHAL-87 Difficult to debug request issues due... Closed
relates to UXPROD-2594 After an item has been associated wit... Draft
relates to CHAL-68 Barcodes missing in Requests-app for ... Blocked
Sprint: Prokopovych - Sprint 128, Prokopovych - Sprint 129, Prokopovych - Sprint 124, Prokopovych - Sprint 126, Prokopovych - Sprint 125, Prokopovych - Sprint 127
Story Points: 8
Development Team: Vega
Epic Link: Requests

 Description   

Update Jan. 21, 2022: This has been moved from a bug to a story since it is missing (not broken) functionality. It's been linked to umbrella features that are being worked on by the cross app & data synchronization working group. 

Overview: Certain inventory data is copied into the Request record. When that data is updated in Inventory, the updates aren't getting synched in Requests.

Data affected: Item barcode, Item title

Data not affected: Effective location, Effective call number, Contributor

1. Steps to repro (adding/updating barcode use case):

  1. log into snapshot
  2. Go to inventory and create an item with no barcode
  3. Create a request on that item
  4. Save the request and notice that, instead of the barcode, we display the FOLIO ID as a link to the item record (this was developed per user story which I can't find)
  5. Now edit the item and apply a barcode
  6. From the item record, click the requests link to view the request

Expected:

  • In the results list, the barcode should populate in the barcode column
  • When you click to open the request, the item barcode should display instead of the FOLIO number

Actual:

  • If you search for the request by searching the instance title, it appears but the Barcode column is still blank
  • If you drill into the request details, the FOLIO ID is still displaying as the link to the item record instead of the barcode

2. Steps to repro (moving items to new instance use case):

  1. log into snapshot
  2. Go to inventory and create a page request for an item in ABA Journal
  3. Back on the Instance record for ABA, choose "move holdings/items to another instance"
  4. Move your paged item to a holding in Temeraire
  5. After the move, review the request record

Expected:

  • In the results list, the Title should populate with Temeraire
  • When you click to open the request, the Title should populate with Temeraire
  • When you search requests by Temeraire, your request should be found

Actual:

  • In the results list, the Title displays ABA
  • When you click to open the request, the Title displays ABA
  • When you search requests by Temeraire, your request is not found

Additional info:

  • If you edit the request (to change the request expiration date, for example), the title will update after save
  • The effective location, effective call number and contributor data are all updating as they should

3. Steps to repro (moving holdings to new instance use case):

  1. log into snapshot
  2. Go to inventory and create a page request for an item in ABA Journal
  3. Back on the Instance record for ABA, choose "move holdings/items to another instance"
  4. Move the holdings record with which your paged item is associated to Temeraire
  5. After the move, review the request record

Expected:

  • In the results list, the Title should populate with Temeraire
  • When you click to open the request, the Title should populate with Temeraire
  • When you search requests by Temeraire, your request should be found

Actual:

  • In the results list, the Title displays ABA
  • When you click to open the request, the Title displays ABA
  • When you search requests by Temeraire, your request is not found

Additional info:

  • If you edit the request (to change the request expiration date, for example), the title will update after save
  • The effective location, effective call number and contributor data are all updating as they should

--------------------- Repro steps from CHAL-68 Blocked ---------------------------------------

1. Login to Chalmers' FOLIO
2. Go to Orders
3. Go to POL
4. Receive a book and scan the barcode.
It will get status In process.
5. Go to Requests
6. Search for the barcode
7. Look in the list for the barcode

Expected Result:
To see and to be able to search and see barcodes on all items that has a barcode.

Actual Result:
I cannot search, nor see the barcode for items with status In process.



 Comments   
Comment by Cate Boerema (Inactive) [ 20/Sep/19 ]

FYI Marc Johnson since you were curious

Comment by Cate Boerema (Inactive) [ 23/Sep/19 ]

Recording this as techdebt because we shouldn't expect the UI to do this (per Marc Johnson and Zak Burke)

Comment by Cate Boerema (Inactive) [ 21/Oct/19 ]

Per Marc Johnson the best way to do this is probably to make use of pub-sub. Let's hold off on this until that becomes available.

If we happen to have ui bandwidth, we could look into doing it that way, but for now let's wait a bit.

There is a workaround for this - edit the request will update with the barcode.

Comment by Jacquie Samples [ 01/Nov/19 ]

Just to be clear, because I am confused, what does "FOLIO ID" refer to? That is, which FOLIO ID is displayed? The Item record HRID, UUID, Inventory HRID?

Thanks

Comment by Cate Boerema (Inactive) [ 17/Dec/20 ]

Item record UUID, Jacquie Samples. This functionality has existed for some time. You can try it out yourself by creating a request on an item with no barcode.

Comment by Brooks Travis [ 08/Feb/21 ]

Marc Johnson In light of the Kafka work being done in Inventory to support ElasticSearch and Remote Storage Integration, should this be re-thought?

Comment by Holly Mistlebauer [ 08/Feb/21 ]

Brooks Travis and Marc Johnson: This seems more like a bug to me, and something we should address soon.

Comment by Marc Johnson [ 09/Feb/21 ]

Brooks Travis Holly Mistlebauer

In light of the Kafka work being done in Inventory to support ElasticSearch and Remote Storage Integration, should this be re-thought?

Good question, yes it likely does. At the very least, the dependencies for this work are way out of date.

At the moment, FOLIO uses a mixture of pub-sub and direct Kafka integration. My understanding is that direct Kafka use is still considered to be a special case (although I think that was intended to change by the end of 2021 R1).

Jakub Skoczen Craig McNally VBar Have I understood that correctly?

If it remains a special case, then either this work needs to be supported by a design document and acceptance of a special case or we need to make mod-inventory or mod-inventory-storage publish messages to pub-sub that can support this.

This seems more like a bug to me, and something we should address soon.

It is a known limitation. You can consider it a bug for prioritisation purposes if that helps.

Comment by Holly Mistlebauer [ 12/Feb/21 ]

STATUS UPDATE:

There are 3 back-end stories the Core: Functional Team had hoped to fit into Iris, but with only one sprint to go and limited back-end capacity, we will not be able to complete them. The stories are...
UIREQ-650 Open (this has 8 story points, so there is no way we can fit it in)
MODINVSTOR-636 Closed (this has 3 story points, so I have added it to the end of the planned stories for Sprint 108, but it is still unlikely to be completed)
MODINVSTOR-669 Closed (this has 8 story points, so there is no way we can fit it in)

Comment by Stephanie Buck [ 22/Dec/21 ]

Hi Holly Mistlebauer. Vega has committed to not taking stories that are more than 5 points into a sprint to prevent spillover. Can you split this into smaller bugs? Maybe by each use case that you've outlined above? Thanks!

Comment by Dmitriy Litvinenko [ 18/Jan/22 ]

Alexander Kurash Could you please check this is BE bug?

Comment by Marc Johnson [ 18/Jan/22 ]

Dmitriy Litvinenko

Could you please check this is BE bug?

The issue manifests in the UI so folks raised it in the UI (and folks consider it a bug).

The changes needed to make the system behave the way folks want are all back end changes.

Comment by Stephanie Buck [ 20/Jan/22 ]

Holly Mistlebauer, is this still a P2? Asking because it's been around since 2019. 

cc: Taisiya Trunova

Comment by Brooks Travis [ 20/Jan/22 ]

Holly Mistlebauer Stephanie Buck I thought it had originally been a P3 (was it ratcheted up by Support SIG?). It's just been held up by the lack of a platform-level recommendation for how to solve this class of problems, I believe.

Comment by Stephanie Buck [ 21/Jan/22 ]

Thanks, Brooks Travis. I think so, too. 

Khalilah Gambrell, any thoughts on how to address this type of bug or manage them in backlogs? It's a bug in requests, but it's a FOLIO wide issue, too. 

Holly Mistlebauer, if you're not opposed, I'll drop this to a P3. 

Comment by Erin Nettifee [ 21/Jan/22 ]

I don't think this is a bug, it's functionality that wasn't prioritized to be built..... FWIW.

Comment by Khalilah Gambrell [ 21/Jan/22 ]

Stephanie Buck, there is a working group exploring this issue related data sync - https://folio-org.atlassian.net/wiki/display/AppInt/Cross-app+data+synchronization+working+group and I have asked them to present at an upcoming POs meeting.

Here are umbrella issues that you can link this issue
https://folio-org.atlassian.net/browse/FOLIO-1331
https://folio-org.atlassian.net/browse/FOLIO-1273

I recommend contacting Raman to see how this issue relates to this working group's efforts.

Comment by Brooks Travis [ 21/Jan/22 ]

I do agree with Erin Nettifee, as well, that this isn't actually a bug, per se. It's missing functionality. And apologies for not providing the information that Khalilah did regarding the working group (which I'm on). I thought I'd already linked those umbrella issues to this.

Comment by Stephanie Buck [ 21/Jan/22 ]

Thanks so much, all. I'll move this to a story. Brooks Travis, do you have the time to keep me in the loop regarding the working group? 

Generated at Thu Feb 08 23:20:55 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.