Issues
- Enable Action profile action for incoming MARC Bibs: Create Inventory InstanceMODINV-241Resolved issue: MODINV-241
- Item-storage 8.0 breaking changesMODINV-189Resolved issue: MODINV-189Bohdan Suprun
- Implement Loaders and MatchHandlers for Items and HoldingsMODINV-201Resolved issue: MODINV-201Kateryna Senchenko
- Implement action handler for Replace Instance actionMODINV-187Resolved issue: MODINV-187Oleksii Kuzminov
- Implement InstanceLoader and handler for matching of InstancesMODINV-204Resolved issue: MODINV-204Kateryna Senchenko
- Most recent check in information clears when item record is editedMODINV-190Resolved issue: MODINV-190Volodymyr Rohach
- Implement action handler for Create Item actionMODINV-184Resolved issue: MODINV-184Ruslan Lavrov
- Implement action handler for Create Holding actionMODINV-183Resolved issue: MODINV-183Volodymyr Rohach
- Implement action handler for Create Instance actionMODINV-182Resolved issue: MODINV-182Volodymyr Rohach
- Integrate mod-inventory with mod-pubsubMODINV-181Resolved issue: MODINV-181Ruslan Lavrov
- Forward effective call number typeId propertyMODINV-177Resolved issue: MODINV-177Bohdan Suprun
- Implement TestsMODINV-176Resolved issue: MODINV-176Bohdan Suprun
- Use JVM features to manage container memoryMODINV-175Resolved issue: MODINV-175David Crossley
- Forward on derived / effective call number component propertiesMODINV-174Resolved issue: MODINV-174Ryan Laddusaw
- back-end: show most recent check in on item recordMODINV-173Resolved issue: MODINV-173Dmytro Popov
- Apply event-driven approach for data-import actions in inventoryMODINV-172Resolved issue: MODINV-172Kateryna Senchenko
- Re-assess the container Memory allocation in default LaunchDescriptorMODINV-169Kateryna Senchenko
- Handle "Inventory: View instance records being suppressed for staff" permission on the back end.MODINV-167Resolved issue: MODINV-167
- ISBN API - explicitly strip hyphens when a valid ISBN is provided and !hyphensMODINV-166
- Update holdings-storage API version to 4.0MODINV-165Resolved issue: MODINV-165Bohdan Suprun
- Missing module permission in GET "/inventory/instances"MODINV-164Resolved issue: MODINV-164Bohdan Suprun
- HRID handling in Inventory for Item recordsMODINV-162Resolved issue: MODINV-162Bohdan Suprun
- HRID handling in Inventory for Holdings recordsMODINV-161Resolved issue: MODINV-161
- HRID handling in Inventory for Instance recordsMODINV-160Resolved issue: MODINV-160Bohdan Suprun
- Allow editing of the Instance relationship fields when Source = MARCMODINV-163Resolved issue: MODINV-163Ruslan Lavrov
- Map the Nature of content data element from MARC Bib to Instance - DRAFTMODINV-159Resolved issue: MODINV-159
- Fix the impact of the API change as per MODINVSTOR-315 for mod-inventoryMODINV-158Resolved issue: MODINV-158Volodymyr Rohach
- Handle new effectiveLocationId property for itemMODINV-157Resolved issue: MODINV-157Bohdan Suprun
- Does not pass X-Okapi-Request-IdMODINV-156Resolved issue: MODINV-156Adam Dickmeiss
- Map shelving order property for itemsMODINV-155Resolved issue: MODINV-155Kyle Felker
- Move schema for uuid from inventoryMODINV-199Kateryna Senchenko
- Invalid InstancesBatchResponse sent after tags field was addedMODINV-153Resolved issue: MODINV-153Kateryna Senchenko
- Missing and Incomplete Data in Hosted Ref Environments - Testing ImpactMODINV-152Resolved issue: MODINV-152
- Item: Change array copyNumbers to simple property copyNumber (breaking)MODINV-151Resolved issue: MODINV-151
- UIIN-470: Backend for nature of content on InstanceMODINV-149Resolved issue: MODINV-149Anatolii Starkov
- Inventory App: Assign tags to holdings recordMODINV-148Resolved issue: MODINV-148stanislav_mureiko
- Inventory App: Assign tags to item recordMODINV-147Resolved issue: MODINV-147stanislav_mureiko
- Inventory App: Assign tags to instance recordMODINV-146Resolved issue: MODINV-146Natalia Zaitseva
- Instance "suppress from display" flag should update SRSMODINV-144Resolved issue: MODINV-144Oleksii Kuzminov
- item-storage/items endpoint doesn't allow assignment of item status dateMODINV-143Resolved issue: MODINV-143
- Issue with metadata in inventory item records and moreMODINV-142Resolved issue: MODINV-142Julian Ladisch
- 400/422 error reporting of ISBN normalization APIMODINV-139Resolved issue: MODINV-139Craig McNally
- Update a list of Instance blocked fieldsMODINV-138Resolved issue: MODINV-138Igor Gorchakov
- Update batch post instances to send batch save to inventory-storageMODINV-134Resolved issue: MODINV-134Ruslan Lavrov
- ACL (field blocks) for Inventory have no sufficient fields on the backend endpointMODINV-133Resolved issue: MODINV-133Igor Gorchakov
- Change instance notes from array of string to array of objects, each with a note typeMODINV-132Resolved issue: MODINV-132Niels Erik Nielsen
- Add the date and source fields to the notes, and to sort the notes by date addedMODINV-129Resolved issue: MODINV-129Oleh Pochernin
- Create design to block from editing instance fieldsMODINV-126Resolved issue: MODINV-126Anatolii Starkov
- No enough permissions to update Instance RelationshipsMODINV-125Resolved issue: MODINV-125Bohdan Suprun
- Protect Instance fields from being updatedMODINV-124Resolved issue: MODINV-124Igor Gorchakov
Issue with metadata in inventory item records and more
Description
CSP Request Details
CSP Rejection Details
Potential Workaround
is blocked by
relates to
Checklist
hideTestRail: Results
Details
Assignee
Julian LadischJulian LadischReporter
Sobha DuvvuriSobha DuvvuriLabels
Priority
TBDStory Points
0Sprint
NoneDevelopment Team
Core: PlatformTestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Reporter
Labels
Priority
Story Points
Sprint
Development Team
TestRail: Cases
TestRail: Runs
Activity
Julian LadischAugust 27, 2019 at 7:09 AM
Fixed by = Update to RMB 27.0.0
Sobha DuvvuriJuly 23, 2019 at 1:40 PM
Possibly, but unsure
Zak BurkeJuly 23, 2019 at 11:24 AM
Is this maybe an RMB bug?
Cate BoeremaJuly 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 BoeremaJuly 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.
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")