StagingDirector deaccessioning: mark an item as withdrawn to deaccession item from remote storage database

Description

Purpose: 

Marking an item as withdrawn (item status) should remove the item barcode from remote storage database, deaccessioning the item

User story statement(s):

As a circulation librarian,
I want to ensure that when an item with a remote storage location is moved to withdrawn status the item barcode is removed from the remote storage database
so that the item is deaccessioned from remote storage and it can no longer be found in the remote storage database

Scenarios:

  1.  Scenario:

    • Given an item record with a remote storage location

    • When I mark an item a Withdrawn

    • Then I see the "Removing from remote storage" popup that states "Are you sure you want to remove this item from remote storage? Please ensure the item has been physically removed from the shelf before selecting Yes." 

  2. Scenario:

    • Given the Removing from remote storage popup

    • When I select Cancel

    • Then I am returned to the item record 

  3.  Scenario:

    • Given the Removing from remote storage popup

    • When I select Yes

    • Then I see the item record AND I see the message Confirm item status: Withdrawn window with the message "[Title] (book) (Barcode: abc)'s item status will be marked as Withdrawn and removed from remote storage."

  4. Scenario:

    • Given the Confirm item status: Withdrawn window

    • When I select Cancel 

    • Then I am directed to the item record

  5. Scenario:

    1. Given the Confirm item status: Withdrawn window

    2. When I select Confirm

    3. The item status is changed to Withdrawn AND the item is deaccessioned (barcode removed) from the remote storage database

Environment

None

Potential Workaround

None

Attachments

3

Checklist

hide

TestRail: Results

Activity

Show:

Stephanie Buck February 13, 2023 at 7:55 PM

HI Priyanka. I cannot confirm how locations are designated on the back end - I'm sorry. 

From the UI perspective, locations are set as remote in Settings > Tenant > Location. From the FOLIO record UI, any remote location will have the word Remote appended to the location name.

For  your question regarding sufficiency: checking item effective location first will catch most situations. That said, if a remote location is set anywhere in the item record OR the holdings record, then marking it withdrawn or deleting it should trigger the system to attempt a deaccession, in order to ensure that it is no longer in the remote storage system inventory database.

Priyanka Terala February 13, 2023 at 11:06 AM
Edited

Hi ,

With the help of the document https://docs.folio.org/docs/platform-essentials/locations/locations/#item-effective-location

How do I understand if the item is stored in remote storage? - I understand - if effective location (id) of the item (that is being marked as withdrawn) matches with one of the the folioLocationId from the response of https://folio-snapshot-okapi.dev.folio.org/remote-storage/mappings api, then it should be considered that the item is stored in remote location.

  1. is my above understanding, correct?

  2. question regarding sufficiency - is my understanding that checking effective location of item is sufficient and need not look for temporary or permanent locations of item or holding, correct?

Could you please confirm on the above questions?

Priyanka Terala February 10, 2023 at 2:27 AM

 
Thank you for your clarifications. As per the discussion with Volaris BE team, API is yet to be developed. Once that is available, this and other deaccession FE tickets would be picked up.

Stephanie Buck February 9, 2023 at 4:30 PM

Hi . Great questions. You can find answers to many UX questions [here|https://ux.folio.org/docs/all-guidelines/.

  1. This should follow the patterns already present in Inventory, so the user should be returned to the item record page the user started in. I updated scenario 2.

  2. Confirmation modal patterns should match across FOLIO, especially within the app itself. Use the pattern already established in Inventory

  3. Yes

  4. This sounds correct to me

  5. There could be a communication error with remote storage.

Priyanka Terala February 9, 2023 at 12:37 PM

Hi ,

Could you please clarify on the below?

  1. Scenario1 talks about clicking "Mark as withdrawn" from Actions menu, while in item view screen. In Scenario 2, once cancel is selected, one should return to item record in view mode or edit mode?

  2. In Scenario 3, is my understanding that the confirmation modal will show up as an overlay on item record correct?

  3. In scenario 4, once cancel is selected, is user redirected to item record in view mode?

  4. In Scenario 5, on clicking confirm, is my understanding that there should be an API call to remote the item from remote storage
    database. On success response, this item status is changed to "Withdrawn".

  1. Can there be any error scenarios here? and how are they to be addressed?

Details

Assignee

Reporter

Labels

Priority

Story Points

Development Team

Volaris

Affected Institution

Grand Valley State University

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created October 10, 2022 at 6:21 PM
Updated February 20, 2023 at 2:37 PM
TestRail: Cases
TestRail: Runs