Details
-
Bug
-
Status: Closed (View Workflow)
-
P4
-
Resolution: Cannot Reproduce
-
None
-
None
-
None
-
-
Prokopovych
Description
This applies to the 2.2 instance at Texas A&M. Today I loaded about a dozen items in item-storage/items; most of them had a status other than Available, such as Charged, Overdue, etc. The json that was submitted to the /item-storage/items endpoint contained a properly formatted UTC date for the item status whenever appropriate. However, the system is overriding the supplied item status date and displaying the last modified date as the item status date.
A sample item can be viewed at: https://folio-testing22.library.tamu.edu/inventory/view/20f1a3c0-6ebf-4612-a7d4-5ded226e14b9/929543c6-c3ea-496f-a103-f88afce49087/9037f3e7-62cd-4e13-8ae2-6f295a3d1002 (please contact me for read-only userid/password)
I have attached a screenshot of the display and a copy of the json that was submitted to the endpoint. The json was extracted after the initial creation of the item record, so the create and update dates are identical. At that point the screen was showing 9:13 PM as the status date. I subsequently updated the item by re-submitting the json, although still with the original status date. That's why the screenshot I attached shows the status time as 9:45 pm, the time of the record update.