Skip to end of banner
Go to start of banner

2022-12-13 CDL Sub-group Meeting Notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Date


Zoom

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

Meeting ID: 843 4272 0176

Passcode: folio-lsp

Recording

No recordings available

Calendar invite

FOLIO Controlled Digital Lending Subgroup Meeting.ics

Attendees


Discussion Items

Time

Item

Who

Description

Goals/Info/notes

Time

Item

Who

Description

Goals/Info/notes

2minAdministrivia


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

----


No meetings on 12/27/2022. But the week before the Christmas holidays looks good for everyone.


Note taker: Peter Murray


Discuss input from the previous three meetings
all 

Input from ReShare, and the ERM. What do we want to follow up on coming out of these talks. Action items?

Andrea the demo of ERM gave us some very useful ideas. And how could we reuse and adapt this. 

David: think the ERM was a good solution, and can we adapt is directly or is it more a mental idea. 

Andrea: The ERM does not deal with the item record, and this we need to have for CDL. We need the linking from ERM app to Inventory data (which has been discussed but not implemented yet).

Andrea: The ReShare work is still on the drawing board. 

David: In the long term we want FOLIO to support the requesting from an ILL system. 

Andrea: Can we learn from the bound-with data model.

Lisa: Can we picture the workflow for CDL in FOLIO as pictured for CDL in ReShare (consortial communication). Should we write up the workflow? Peter and Charlotte promised to do this. 

David: Here the workflow diagram would be helpful. Didn't see in the diagram - now the CDL is no longer in use, and now the print is available ('back on shelf') 

CDL in FOLIO - support request, support the lending process.

David, Andrea, Lisa:

  1. How important is it to do the three partie item status (being worked on by a small group), also new item state for CDL
    1. The item status 'restricted' (can be checked out with a warning message - is this a bug? Charlotte to check in on Emma's Jira tickets on this. RA-SIG will help out discussing the requirements)
      1. physical item: access to the CDL then flipped to restricted
      2. physical item: when returned then flipped back to available
    2. CDL item status was to use 'restricted', similar as the Hathi-trust. Andrea mentioned that we need to be able to solve multiple copies, move them around (logic similar to TLR routing).  
  2. The workflow engine (FOLIO to communicate with any storage)
  3. How to capture this in the Circulations log? 
    1. Circulation log is right now not reflecting the item states, and therefor it can not see the difference between a regular loan (of a physical loan) and a CDL loan
    2. Can be captured in the Circulation log?
      1. To be solved at a later time
      2. For the MVP we want to capture it has been used
  4. The CDL app? (MVP)
    1. If it's own apps - what is the advanges
      1. Can tailor the work flow (here we need the diagram) 
      2. Does this make it easier for FOLIO to pull in information
      3. Lisa referred to the Slack conversation with Sebastian Hammer (https://folio-project.slack.com/archives/C0323AXFM1D/p1668724850521619)
        1. legal
        2. economic
      4. Easier for libraries who do not want to accommodate CDL loan (and therefor will not implement the CDL app)
      5. Capture statistics in the CDL app.
      6. How does this tie in with the Workflow issue
      7. We need to establish the proof of no 
    2. This will requires interaction with Inventory, item records
    3. Or should it just interacts with the Request app.
  5. Collection development. Buying more copies. Here it is necessary to tie the given circulation of a title, to understand the need for acquring more copies (or replace).
    1. If multiple copies, then necessary to know how many of these were CDL loans. Do we in FOLIO need to know the kind of user. This is relevant for legal causes. 
      1. Loan to the institutions own patrons
      2. Loan to consortial users (ILL request)


We need to know what might missing. 






Defining record requirements

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.





Planning our next meeting

12/20/2022: 




Next steps

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. 


Discussion topics/ questions for the group@all

Please list your questions/topics below




News



Chat log

  • No labels