• Current and Stable

    • FOLIO Upgrade Planning

    Owned by Jag Goraya
    Last updated: about 2 hours ago by Tim Auger
    3 min read

    Assumptions / Notes

    • Repeat plan checks for standalone and consortial FOLIO systems

    • Repeat tests across systems and FOLIO versions.

    • Ingest testing on EBSCO integration environment k-int development environment, rather than staging

    • Request and circulation testing on staging for each client implementation

    • Test records needed:

      • Eligible Patron with Authentication Details

      • Solely-Owned Bib Record with Requestable Item

    Upgrade Checks / Questions

    Setup and Connection

    Can we connect to a FOLIO system?
    Can we authenticate a patron on a FOLIO system?

    Ingesting FOLIO Catalog Records

    Can we harvest catalog records performantly?
    Can we receive changes to catalog records?
    new record additions
    deletion of records
    modifications to key fields
    fields used by Locate: id, title, contributors, identifiers, publication, format, physicalDescription, subjects, languages, document type (sourceTypes)
    fields used by clustering algorithm: ***
    modification to suppression fields

    FOLIO as a Borrowing Library

    Do we reject a request from a patron with account blocks?
    Do we reject a request from an ineligible (NOT_ELIGIBLE) patron type?
    Do we reject a request for a deleted patron?
    Can we process a request for a FOLIO patron?
    Can we successfully submit a request to DCB?
    Can we circulate the request and update FOLIO systems?
    Does finalisation handle borrowing library cleanup?

    FOLIO as a Supplying Library

     

    Implementation Upgrade Plans

     

     

    Operated as a Community Resource by the Open Library Foundation