Details
-
Story
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
-
Folijet Sprint 98, Folijet Sprint 99
-
8
-
Folijet
-
Q3 2020
Description
Purpose: To refine the logic applied when setting the item status during item record creation or update
As a staff person working with field mapping profiles
I want different things to happen depending on existing and new item statuses and whether the item record is being created or updated
So that I do not accidentally assign or re-assign inappropriate statuses
Scenarios
- Scenario 1
- Given the Item status list in the Field mapping profile (when incoming record type = MARC and FOLIO record type = Item)
- When the action is Create item
- And the item status is in the dropdown list in the item record field mapping screen
- Then create the item record with the mapped item status
- Scenario 2
- Given the Item status list in the Field mapping profile (when incoming record type = MARC and FOLIO record type = Item)
- When the action is Update item
- And the item record's existing item status is one of the following
- Available
- In process
- In transit
- Missing
- On order
- Order closed
- Withdrawn
- Available
- Then update the item record's status (and update the other fields in the item record according to the item field mapping profile)
- Scenario 3
- Given the Item status list in the Field mapping profile (when incoming record type = MARC and FOLIO record type = Item)
- When the action is Update item
- And the item record's existing item status is one of the following
- Aged to lost
- Awaiting delivery
- Awaiting pickup
- Checked out
- Claimed returned
- Declared lost
- Paged
- Then do not update the item record's status (but update the other fields in the item record according to the item field mapping profile)
- And return an exception for that item record to the Data Import log: Could not change item status from [existing status] to [field mapping status]
- Add an error message to the context and put error message to the journal
NOTES:
- Further handling for Available status moved to
MODINV-339to unblock this story - When status Recently returned (UXPROD-527) is added to the Inventory item record, it should also be disallowed being updated by the incoming status; see MODINV-337
- When status Long missing (
UXPROD-2177) is added to the Inventory item record, it should be allowed for Creates (scenario 1) and updates (scenario 2); seeMODINV-338andUIDATIMP-641
TestRail: Results
Attachments
Issue Links
- blocks
-
MODINV-344 Release mod-inventory 16.1.0
-
- Closed
-
- defines
-
UXPROD-2550 MARC Bib Field Mapping Profiles Details for Inventory Item Status
-
- Closed
-
- relates to
-
UIDATIMP-529 Field mappings: Item - update reference dropdown list for Item status
-
- Closed
-
-
UIDATIMP-641 Field mappings: Item - update reference dropdown list for Item status to include new statuses
-
- Closed
-
-
MODINV-337 Field mappings: Item - Item status handling logic for Recently returned
-
- Blocked
-
-
MODINV-338 Field mappings: Item - Item status handling logic for new statuses
-
- Closed
-
-
MODINV-339 Field mappings: Item - Item status handling logic for Available status - DRAFT
-
- Closed
-
-
UIDATIMP-515 Field mappings: Reference dropdowns - Item - Item status list is wrong
-
- Closed
-