2022-12-13 CDL Sub-group Meeting Notes

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

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. 

Please list your questions/topics below