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

Remote Storage Integration Module (Caiasoft)



    • Template:
      UXPROD features
    • Potential Workaround:
      Cate Boerema: As far as I know, there is no workaround for this for institutions that use remote storage (many). For this reason, I have significantly increased the ranking and marked po-mvp
    • Epic Link:
    • Front End Estimate:
      Medium < 5 days
    • Back End Estimate:
      XXL < 30 days
    • Estimation Notes and Assumptions:
      Cate reduced back end estimate from 10 to 5 days because it is now thought that Caiasoft will develop the edge apis. All that will be left for FOLIO developers will be any settings pages that might be needed (and that might also be able to be developed by Caiasoft)
      Cate reduced back end estimate from 10 to 5 days because it is now thought that Caiasoft will develop the edge apis. All that will be left for FOLIO developers will be any settings pages that might be needed (and that might also be able to be developed by Caiasoft)
    • Development Team:
    • Calculated Total Rank:
    • PO Rank:
    • PO Ranking Note:
      2019-07-12: Increased the ranking relative to calculated because, as far as I know, there is no workaround for institutions that have remote storage (many).
    • Cap Plan Fix Version (DO NOT CHANGE):
      R2 2021
    • Rank: Chalmers (Impl Aut 2019):
    • Rank: Chicago (MVP Sum 2020):
    • Rank: Cornell (Full Sum 2021):
    • Rank: Duke (Full Sum 2021):
    • Rank: 5Colleges (Full Jul 2021):
    • Rank: FLO (MVP Sum 2020):
    • Rank: GBV (MVP Sum 2020):
    • Rank: Grand Valley (Full Sum 2021):
    • Rank: hbz (TBD):
    • Rank: Hungary (MVP End 2020):
    • Rank: Lehigh (MVP Summer 2020):
    • Rank: Leipzig (Full TBD):
    • Rank: MO State (MVP June 2020):
    • Rank: TAMU (MVP Jan 2021):
    • Rank: U of AL (MVP Oct 2020):


      Update 2021-1-13
      This feature will cover must-have features for Summer 2021 go-live institutions:

      • Accession
      • Requesting an item for circulation
      • Returning an item to remote storage

      The Accession workflow will require some development work around APIs and edge-APIs. Mikhail Fokanov is working with Laura Beatham at CaiaSoft to review code.

      Remote storage configuration and settings development are covered in UXPROD-2696, along with the bulk of development needed for Requesting items and Returning items. They use the same workflows.

      Caiasoft MVP workflows & requirements doc: https://drive.google.com/file/d/1iS8nKYkIP4Q7BA0i8tU6csLqvgEiYRta/view?usp=sharing

      Cornell Caiasoft workflows: https://docs.google.com/document/d/1TP4nSNtEkvOnT-tE2yhwqElVtf2aW--EefW9OKhBLjc/edit?usp=sharing

      Duke Caiasoft workflows: https://docs.google.com/document/d/1e3vSoerJgYoZpCWW7mDUTaMdfPjVIwCoJdSdOPdMOQU/edit?usp=sharing 

      Vision document: https://docs.google.com/document/d/1kMTq4D6PBWsTrEOsn-GIUgFt7vbGKxA2/edit#

      Update 2019-12-17 Current planning is that Caiasoft will do the bulk of the development on the edge apis. Still reserving some time on this feature for FOLIO development for any settings pages that might be needed.

      Purpose: Implement a FOLIO/Caiasoft integration module that would could serve as a model for integration with other remote storage systems (many of the FOLIO community institutions have homegrown systems). For details on remote storage systems and SMEs in the FOLIO community, please see: https://wiki.folio.org/display/RA/RA+-+Off-site+integration?focusedCommentId=14463074#comment-14463074 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

      Current thinking on design: Original thinking on design (see below) was that we could leverage existing page request functionality for remote storage requests and all we really needed was to ensure we had an edge api for page requesting. We still intend to leverage page request functionality, but we have decided to develop a FOLIO/Caiasoft Integration Module which would serve as an abstraction layer between the two systems. This will help protect the integration against disruption as both systems are likely to change and direct integration would be brittle.

      The current thinking is documented in detail on the FOLIO wiki here: https://wiki.folio.org/display/RA/Caiasoft+Managed+Remote+Storage

      NOTE: A separate feature has been created for the work needed to support automated storage and retreival systems (like the one in place at Chicago). See UXPROD-1516 for details.


      Original (old) thinking on design:

      • Existing page request functionality should work for remote storage requests
      • FOLIO needs an API that remote storage systems can call to determine what new page requests have been created for remote storage locations
      • API response should include data such as:
        • Requested item barcode
        • Requested item's effective location
      • Process will work something like this:
        • Page request is created in FOLIO for item with effective location of, say, "Remote storage A"
        • The remote storage system calls API to determine if new page requests have been created for items in "Remote storage A" - this may happen on-demand or on a regular chron job
        • When the new request comes through, staff retrieves the requested item from remote storage and scans it into FOLIO check in app at the service point in the remote storage facility
        • FOLIO tells the staff where the item needs to be routed to fulfill the request (to the pickup service point specified in the request)

        TestRail: Results


            Issue Links



                stephaniesbuck Stephanie Buck
                cboerema Cate Boerema
                Front End Estimator:
                Alex Mozolev Alex Mozolev
                Back End Estimator:
                Viachaslau Khandramai Viachaslau Khandramai
                0 Vote for this issue
                11 Start watching this issue



                    TestRail: Runs

                      TestRail: Cases