2024-3-19 Consortia SIG Notes

What are specific use cases for consortial ordering? 

Common use case: some central decision making process for the consortia, will order something as a group.  An "entity" communicates with the vendor and places the order. The members participating would pay with the "entity that communicated with the vendor."

Lloyd: Marmot doesn't do that, all finances are separate, they do their own purchases, might share bib records. No coordinated purchases. Each communicates with vendor separately. Do sometimes get group discount. But we wouldn't do a joint order.

Lucy: GALILEO might do a joint order, but not all libraries using same ILS. Central might sign contract, establish the contract, then members pay the vendor directly. 

Margaret: 5C print is shared, but e-resources are independent.  Sometimes shared bib, sometimes not. Messy. Individual agreements are made with vendor.

Corrie: sometimes vendor splits the agreements/licenses.

Dennis: what is a good way to refer to the type of order where the procurement process is independent, but the consortium as a whole is negotiating it.  Is it important to keep track of this as a different flavor of order?

Corrie & Lucy: yes, and sometimes important to note in the discovery layer also (Dennis likened it to a bookplate type of concept)

Design demo. UXPROD-4553 (assume multi-tenant functionality)
Combination of requirements, not just this. Order in central tenant of the consortial system. Can create a multi-tenant order from central tenant. In POL when assigning locations, can choose from different tenants in the system. (This doesn't address if member isn't using FOLIO. Would need another POL line for external libraries.)  Could use a separate POL for each member, one location on each. Or can do multiple locations on one POL. When open order and create encumbrance, the central tenant pays. But this might address the use case where members pay the vendor. In that case, here you keep track of the actual order, pay elsewhere.  But this generates holdings/items in whatever tenant the locations are associated with.
Receiving: in holdings, has Acquisition accordion showing all orders, also has Consortial holdings accordion (regular ECS feature).

Use case: sometimes seeing another member's price info would be restricted

In next meeting, Dennis would like to talk about managing permissions. The new proposed architecture requires a rethink.

From last meeting: 

(Noah) We should do a survey about perceived gaps, 3rd party integrations needed. Corrie and Noah will do a draft for discussion. Ask about timing folks are considering for moving/implementations. Will be posted on folio-general channel, send it "anywhere and everywhere."

Draft list of questions

Dennis is planning to do a ECS-related presentation, circulation, requests management, user management, etc. Multiple PO's are involved in all this.