Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Issue with metadata in inventory item records and more

Description

On updating an inventory record, we see metadata - createdDate and updatedDate being updated and both being set to same timestamp.

Steps to reproduce:
1. Go to Inventory app
2. Filter by "English"
3. Select "A Semantic webprimer"
4. Select Item record 10101 and update Item Data -> Material type from "book" to "dvd"
5. A PUT request is sent to https://folio-clover-okapi.aws.indexdata.com/inventory/items/7212ba6a-8dcf-45a1-be9a-ffaa847c4423 returning a 204
6. Then, there are a few GET requests that are sent out as part of the update and refreshing the UI page.
7. GET https://folio-clover-okapi.aws.indexdata.com/inventory/items/7212ba6a-8dcf-45a1-be9a-ffaa847c4423 - gives a response like below where metadata - createdDate and updatedDate are set to same

8. GET request sent to https://folio-clover-okapi.aws.indexdata.com/inventory/instances/5bf370e0-8cca-4d9c-82e4-5170ab2a0a39 returns metadata with null values for createdDate and updatedDate

9. Another GET request is made to https://folio-clover-okapi.aws.indexdata.com/inventory/instances/5bf370e0-8cca-4d9c-82e4-5170ab2a0a39 which gives metadata as null - why is a second request being made and why did metadata values change?

9. Two requests are made to GET https://folio-clover-okapi.aws.indexdata.com/users?query=%28id%3D%3D%220f36ec69-3569-5264-9648-6d7ac57c0754%22%20or%20id%3D%3D%220f36ec69-3569-5264-9648-6d7ac57c0754%22%29 - unsure why there are 2 requests to get the same user and also unsure why the query has (id=="0f36ec69-3569-5264-9648-6d7ac57c0754" or id=="0f36ec69-3569-5264-9648-6d7ac57c0754")

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Julian Ladisch August 27, 2019 at 7:09 AM

Fixed by = Update to RMB 27.0.0

Sobha Duvvuri July 23, 2019 at 1:40 PM

Possibly, but unsure

Zak Burke July 23, 2019 at 11:24 AM

Is this maybe an RMB bug?

Cate Boerema July 17, 2019 at 7:20 AM

Not sure if this is related, but several bugs were filed recently because the record metadata had gone missing in folio-snapshot and testing. To remedy this, we implemented which would display "unknown" in the record metadata component when data was not present. There is also an issue in the Core:Platform backlog for making sure the timestamp data is populated for sample data FOLIO-2102. Finally, we had planned to modify Inventory such that the component displayed whether there was data present or not (). I'll link these up for reference.

Cate Boerema July 17, 2019 at 6:59 AM

Thanks . is a common use case and results in a nasty error so I marked it P1 and assigned it to q3.1. Is this issues the backend work needed to support a fix for UIIN-645? Or is it something different? I have a hard time understanding the user impact.

Cannot Reproduce

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Core: Platform

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created July 16, 2019 at 7:09 PM
Updated December 3, 2019 at 12:05 PM
Resolved December 3, 2019 at 12:05 PM
TestRail: Cases
TestRail: Runs