Uploaded image for project: 'mod-remote-storage'
  1. mod-remote-storage
  2. MODRS-39

Caiasoft: Returning an Item to remote storage (Duke flow)

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Closed (View Workflow)
    • Priority: TBD
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 1.1.0
    • Labels:
      None
    • Template:
      Thunderjet/Firebird Back-end Story Template
    • Sprint:
      Firebird Sprint 114
    • Story Points:
      2
    • Development Team:
      Firebird

      Description

      Purpose/Overview:

      Returning items scanned into remote storage when received at remote storage

      Requirements/Scope:

      1. API endpoint remote-storage/return/{remoteStorageConfigurationId} is updated to handle return flow options.
      2. Request body isn't changed
      3. Handle error cases to send them to edge-caiasoft for further processing.

      Approach:

      This logic mostly implemented in scope of MODRS-10 (for Dematic provider).

      1. Resolve provider type and return flow settings from configuration by remoteStorageId. The following flow should works for Returning items scanned into remote storage when received at remote storage.

      2. FOLIO checks if a new hold or recall request has been created while the item was in transit:

      • If there are one or more open requests on an item, the first of them is added to the remote retrieval request queue to be sent to the Remote Storage System. The call from CaiaSoft will be instantaneous and come back off the refile.
      • If an item is not requested, its status becomes “Available” (check-in).

      3. In case the notification from Remote Storage was received and the item still hasn't been checked-in to the service point associated with its effective location, FOLIO will check it in automatically at its primary service point to complete circulation.

      Acceptance criteria:

      • API endpoint remote-storage/return/{remoteStorageConfigurationId} logic is updated
      • Unit tests coverage for new code is at least 80%

        TestRail: Results

          Attachments

          1. available_status_of_item.PNG
            available_status_of_item.PNG
            169 kB
          2. checked_out_item_002.PNG
            checked_out_item_002.PNG
            156 kB
          3. check out1.png
            check out1.png
            291 kB
          4. check out2.png
            check out2.png
            293 kB
          5. configuration.png
            configuration.png
            298 kB
          6. create_hold_request.PNG
            create_hold_request.PNG
            89 kB
          7. create request.png
            create request.png
            482 kB
          8. holding and item.png
            holding and item.png
            496 kB
          9. image-2021-05-21-11-28-22-592.png
            image-2021-05-21-11-28-22-592.png
            159 kB
          10. image-2021-05-21-11-32-20-154.png
            image-2021-05-21-11-32-20-154.png
            161 kB
          11. image-2021-05-21-11-52-11-408.png
            image-2021-05-21-11-52-11-408.png
            156 kB
          12. item.png
            item.png
            495 kB
          13. location.png
            location.png
            438 kB
          14. location.PNG
            location.PNG
            155 kB
          15. request status changed.png
            request status changed.png
            490 kB

            Issue Links

              Activity

                People

                Assignee:
                Harbuz Aliaksei Harbuz
                Reporter:
                khandramai Viachaslau Khandramai
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases