Uploaded image for project: 'mod-inventory'
  1. mod-inventory
  2. MODINV-338

Field mappings: Item - Item status handling logic for new statuses

    XMLWordPrintable

    Details

    • Template:
    • Sprint:
      Folijet Sprint 123
    • Story Points:
      3
    • Development Team:
      Folijet
    • Confidence factor:
      High

      Description

      Purpose: To refine the logic applied when setting the item status during item record creation or update, for the new statuses listed in UXPROD-2699 (In process (non-requestable), Intellectual item, Long missing, Restricted, Unavailable, Unknown)

      As a staff person working with field mapping profiles
      I want to allow item records with Unavailable, Intellectual, In process - non requestable, Long missing, or Unknown status to have their statuses updated by incoming import records
      So that I can assign or re-assign appropriate statuses

      NOTE: These new statuses are being added to the validation list for the Item record field mapping profile also, in UIDATIMP-641

      Scenarios

      1. 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 Update item
        • And the item record's existing item status is one of the following:
          • In process (non-requestable)
          • Intellectual item
          • Long missing
          • Restricted
          • Unavailable
          • Unknown
        • Then update the item record's status (and update the other fields in the item record according to the item field mapping profile)

      Plus these existing scenarios from MODINV-296 apply to these new statuses as well:
      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 (which all these new statuses are)
      • Then create the item record with the mapped item status
        • In process (non-requestable)
        • Intellectual item
        • Long missing
        • Restricted
        • Unavailable
        • Unknown

      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
      • And return an error for that item record to the Data Import log: Could not change item status from [existing status] to [field mapping status]
      • And add an error message to the context and put error message to the journal

      How to set up an import to test Scenario 3:

      1. Create a Field mapping profile for Creating Holdings
        • Name: Create holdings
        • Incoming record type: MARC
        • FOLIO record type: Holdings
        • Permanent location: Select a location from the dropdown list
      2. Create a Field mapping profile for Items
        • Name: Create items
        • Incoming record type: MARC
        • FOLIO record type: Item
        • Material type: Select book from the dropdown list
        • Permanent loan type: Select Can circulate from the dropdown list
        • Status: Select Available from the dropdown list
      3. Create an Action profile for Create holdings
        • Name: Create holdings
        • Action: Create
        • FOLIO record type: Holdings
        • Link the Holdings field mapping profile to this action profile
      4. Create an Action profile for Create item
        • Name: Create item
        • Action: Create
        • FOLIO record type: Item
        • Link the Item field mapping profile to this action profile
      5. Create a Job profile for Create instance, holdings, items
        • Name: Create instance holdings item
        • + Action: Default - Create instance
        • + Action: Create holdings
        • + Action: Create item
      6. Import the attached MARC file, using the newly created job profile
      7. Go to the newly-created item record in Inventory
      8. Go to Actions/New request
        • For requester information, enter barcode 789 then press Enter. That will bring up Requester details for sheldon, bazinga
        • For pickup service point, select Circ Desk 1
        • Press Save and Close
        • That will cause the item record's status to update to Paged
      9. Copy the item record's HRID
      10. Open the attached REVISED MARC file and edit the existing 901 $a to have the Item record's HRID in it (check with Ann-Marie Breaux) if questions about that
      11. Create a Match profile to match the 901$a of the incoming MARC record to the Item HRID field
        • Name: 901a to Item HRID
        • Incoming record: MARC Bib
        • Existing record: Click on Item (MARC Bib will show to the left of it)
        • Incoming MARC Bib: Field: 901, Ind1: [blank], Ind2: [blank], Subfield: a
        • Existing item record field: Admin data: Item HRID
      12. Create a Field mapping profile for Updating Items
        • Name: Update item status
        • Incoming record type: MARC
        • FOLIO record type: Item
        • Status: From the dropdown list, select one of the new statuses from scenario 1 (e.g. Long missing)
      13. Create an Action profile for Updating items
        • Name: Update item status
        • Action: Update
        • FOLIO record type: Item
        • Link the Item field mapping profile to this action profile
      14. Create a Job profile for Updating item status
        • Name: Update item status
        • + Match: 901a to Item HRID
        • If matched, + Action: Update item status
      15. Import the revised MARC file
      16. Check the item record to see if the status was updated or not, It should NOT have been updated

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                bisecomsergiy Sergiy Bichurin
                Reporter:
                abreaux Ann-Marie Breaux
                Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases