Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-2696

Remote Storage Integration (Dematic thin thread)

    XMLWordPrintable

Details

    • XXXL: 30-45 days
    • Jumbo: > 45 days
    • Firebird
    • Resource Access
    • 94
    • R1
    • R5
    • R1
    • R3
    • R4
    • R1
    • R5
    • R4
    • R3
    • 2
    • Yes
    • Hide
      [Patrick from GVSU: There are workarounds for this. However, we have a signed agreement with Dematic to work on this project and they will have an end date. They are expecting this work to be completed by July 1, 2021. Because of Dematic's tight schedule if the work isn't done by that time it will most like result in a significant additional cost for GVSU.] [Tod from Chicago: This is a showstopper for us. We have millions of physical items in storage and need these integrations to (1) facilitate adding new items into storage, and (2) have requests on stored items turn into actual retrievals of those items. The work in this feature is for the underlying support in FOLIO that will allow us to build an edge module for Dematic EMS. So it's basic plumbing. We don't have practical workarounds without it. Caiasoft integrations will also rely on portions of this work.]
      Show
      [Patrick from GVSU: There are workarounds for this. However, we have a signed agreement with Dematic to work on this project and they will have an end date. They are expecting this work to be completed by July 1, 2021. Because of Dematic's tight schedule if the work isn't done by that time it will most like result in a significant additional cost for GVSU.] [Tod from Chicago: This is a showstopper for us. We have millions of physical items in storage and need these integrations to (1) facilitate adding new items into storage, and (2) have requests on stored items turn into actual retrievals of those items. The work in this feature is for the underlying support in FOLIO that will allow us to build an edge module for Dematic EMS. So it's basic plumbing. We don't have practical workarounds without it. Caiasoft integrations will also rely on portions of this work.]
    • Hide
      This is already the thin-thread. We are talking about two Dematic products: EMS and Staging Director. What is needed for Dematic does overlap with what is needed for Caiasoft. Chicago and GVSU prefer to have 3 months for integration and testing, but would settle for 2 months.
      Show
      This is already the thin-thread. We are talking about two Dematic products: EMS and Staging Director. What is needed for Dematic does overlap with what is needed for Caiasoft. Chicago and GVSU prefer to have 3 months for integration and testing, but would settle for 2 months.
    • Hide
      The Capacity Planning Team recommended to the FOLIO Product Council that the Iris release date be extended to May 3 (from March 1) so that all of the at-risk 'showstopper' features could be completed and released before the July implementations. (Slide deck presented to PC: https://docs.google.com/presentation/d/12s_fs3vqjm4hAGIfZ_HX1jm--v8QOEFber5uvo0VTGw/edit?usp=sharing)
      Show
      The Capacity Planning Team recommended to the FOLIO Product Council that the Iris release date be extended to May 3 (from March 1) so that all of the at-risk 'showstopper' features could be completed and released before the July implementations. (Slide deck presented to PC: https://docs.google.com/presentation/d/12s_fs3vqjm4hAGIfZ_HX1jm--v8QOEFber5uvo0VTGw/edit?usp=sharing)
    • Hide
      FOLIO Product Council compromised and allowed the Iris release to be delayed by one month, to April 5. Due to the size of the t-shirt estimate for this feature, it will NOT be completed as part of the Iris release. The Capacity Planning Team will be meeting to discuss how/when this feature will be delivered to the libraries needing it before implementation.
      Show
      FOLIO Product Council compromised and allowed the Iris release to be delayed by one month, to April 5. Due to the size of the t-shirt estimate for this feature, it will NOT be completed as part of the Iris release. The Capacity Planning Team will be meeting to discuss how/when this feature will be delivered to the libraries needing it before implementation.

    Description

      Purpose: Implement a thin thread integration with Dematic remote storage system, a FOLIO-initiated workflow. Where possible functionality will be developed so it can be reused with other Remote Storage providers, but the focus here is for an end to end thin thread for Dematic. For details on remote storage systems and SMEs in the FOLIO community, please see: https://wiki.folio.org/display/AppInt/Remote+storage+integration+subgroup The Smith-developed homegrown remote storage system used by 5 Colleges is up on Github if people want to take a look at how that works: https://github.com/SmithCollegeLibraries/sis-inventory-management

      NOTE: A separate feature is being drafted to address Caiasoft integration UXPROD-498, a remote storage-initiated workflow

      Thin thread includes:
      Integration
      Accession (single item)
      Request item for circulation
      Returning an item to remote storage

      Backlog could include the following. This is not inclusive of all work. The use of Caiasoft below is a placeholder name for any remote storage system. In this feature, Caiasoft is replaced with Dematic.

      • Integration-
        • Ability to flag FOLIO locations as “remote storage locations”
        • [mod-inventory-storage] Add new “remote storage flag” property to location record
        • [ui-tenant-settings] Make “remote storage flag” be editable in Settings => Tenant => Locations
        • [edge-caiasoft, mod-caiasoft] Implement POST Item Attribute Update request triggering
      • Accession (single item)-
        • [mod-inventory-storage] Create endpoint to retrieve brief item information based on provided barcode
        • [ui-inventory] Add “Send to remote storage” action in item detail view (with pop-up)
        • [edge-caiasoft, mod-caiasoft] Handle Incoming Accession Items request-response collaboration
        • [mod-caiasoft] Implement logic for selection/creation of remote storage holding for accession item
      • Request item for circulation-
        • [mod-circulation-storage] Trigger request to remote storage
        • [edge-caiasoft, mod-caiasoft] Handle Circulation Request Item request-response collaboration
        • [edge-caiasoft, mod-caiasoft] Catch and process “in transit” status from Remote Storage system
      • Returning an item to remote storage
        • [edge-caiasoft, mod-caiasoft] Send notification to Remote storage about item’s returning

      Out of scope:

      • Bulk item accession
      • Deaccession
      • Reporting
      • Canceling retrieval requests in remote storage

      Vision document: https://docs.google.com/document/d/1kMTq4D6PBWsTrEOsn-GIUgFt7vbGKxA2/edit#
      https://drive.google.com/file/d/1iS8nKYkIP4Q7BA0i8tU6csLqvgEiYRta/view for Dematic part

      Dematic MVP workflows & requirements doc: https://docs.google.com/document/d/10vmY77rO-K2lFv_Hsena5ENQLIqOfCh9DJDP2a59iLs/edit?usp=sharing

      Grooming:

      Feature overview
      Grooming Session

      Tech Design:

      Tech Design

      Update 10/23/20:

      This feature will cover both Dematic EMS and Dematic StagingDirector. Both accession processes begin in FOLIO. Dematic StagingDirector pushes newly accessioned items to remote storage via TCP/IP. Dematic EMS polls FOLIO for accessioned items via API.

      High-level estimation based on the current team's performance:
      BE = ~50 man-days
      FE = ~35 man-days

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                stephaniesbuck Stephanie Buck
                stephaniesbuck Stephanie Buck
                Votes:
                0 Vote for this issue
                Watchers:
                13 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases