2022-11-29 CDL Sub-group Meeting Notes

Topic: FOLIO Controlled Digital Lending

Time: Oct 25, 2022 12:00 PM Eastern Time (US and Canada)

Every week on Tuesdays

Join Zoom Meeting

https://openlibraryfoundation.zoom.us/j/84342720176?pwd=N0wwK3hSRTh5YUdQWjc2VlBCazVMZz09

Meeting ID: 843 4272 0176

Passcode: folio-lsp

Note taker: Peter Murray 

Debra Denault Sebastian Hammer 

Follow up on last week's call.

Review the workflow diagram. This starts from the existing ReShare Returnables workflow and adds things that are specific to ReShare CDL.  For MVP, anything in green is a manual step outside of ReShare; boxes in green can become a part of ReShare CDL later. This workflow adds a question to the user if they want the item digitally; there are decisions to be made if the digital request goes end-of-rota...would the request turn into a paper copy?  For the MVP, there are not yet constraints on whether the book is older than a specified age window.  The autoresponder in ReShare is engaged at the Supplying library; it uses the ILS Z39.50 server to determine availability of the item and responds to the Requesting library if the item is available, and if not the autoresponder sends an ISO "not-available" message to the Requester. An added step at the Supplier is querying the library staff if they want to digitally supply the item (for an item that is too big or the physical condition of the book). For now, there is a list of already digitized items that will be stored centrally in a Google Drive. If the item is available on the shelf and the Supplying library will digitize, the item is pulled from the shelf. ReShare will check out the item on the ILS so it shows as unavailable in the local catalog.  Then the Supplying library digitizes the item, uploads it to the consortium database, and manually adds the URL to the digital item index. What happens when one library has a digital copy and another library is asked to lend based on its physical copy? For BLC, there will be one repository, and the Supplying library can see if a scan exists. ReShare is managing the consortial sequestration across all of the members. For CDL, ReShare will add a new lending interface for the URL and expiration date; when this info is completed, the status is set to "shipped" and an ISO message is sent to the Requesting library. From the patron's perspective, the notification of availability and delivery comes from the Requesting library. When the lending time expires, the Requesting library sends a "returned" message to the Supplying library and a message is sent to the Supplying library staff to make the item available.

Much of what described here is going to take changes to the ReShare Supply app. What would it mean to drop the Supply app into the FOLIO environment for servicing a library's internal patrons? What would work well and what would not?

Two tracks of discussion: what is the status of the ReShare CDL development and what can be reused for a CDL implementation within a library using FOLIO.

Peter Murray  and Charlotte Whitt will start working on the FOLIO CDL workflow chart. 

This is the MVP requirements Document.

MVP requirements:

Assumptions:

• Will leverage ReShare development. Access using VuFind or POD
• Eventually will FOLIO have an app for CDL.
• Not everyone using CDL in FOLIO will use ReShare and vice versa.
• FOLIO CDL will follow NISO as it’s developed (Action point for Sebastian Hammer)

1. Determination of digital record representation in FOLIO:
   • Description: functional notation that this has a digital equivalent
   • Ideas for implementation: binary flag that CDL exists at the item record, or field that includes unique ID for digital version
   • FOLIO Inventory integration that shows the relationship between the digital and physical copy
2. FOLIO Inventory integration that allows us to link digital and physical availability based on use and demand
   • • • Item state for sequestering of physical objects
       • API where FOLIO can communicate whether the physical copy is in use or not?
       • API where 3rd party tools can communicate that physical copy no longer needs to be requested
       • Ability to support multiple models for sequestration (immediate, delayed sequestration, delayed access, etc.)
       • Eligibility for digitization. Not just support item records, but also support by rules (material type, date range, location etc). Create a request type?
3. Integration with third party CDL tools
   • • • • ILL-systems: Illiad, ReShare, InnReach 
         • Maybe also Storage systems: Caiasoft and Dematic
         • Course reserve system; the FOLIO app Courses, and Ares
         • Rare book management system: Aeon
         • Integration with local CDL storage and delivery systems
         • Idea: need to describe landscape of current 3rd party tools
         • Do we need to think about integration with other tools; e.g. 
4. Specific reporting on circulation of physical items w/CDL counterparts
5. Extension of FOLIO circ rules and patron data into the CDL space
   • integration with wait list/requesting functionality within circ rules.  Requesting, renewals, etc.

12/06/2022: Martina Schildt  will attend the meeting and present the suite of ERM apps. 

Action items: 

• Peter Murray  and Charlotte Whitt will start working on the workflow chart. The intention is to present for the group in the beginning of December.