Date

23 Oct 2019

Attendees

Goals

Discussion items

Time

Item

Who

Notes

5min

Housekeeping/updates

All

45min

Technical architecture for central office/tenant functionality

Summary document: https://docs.google.com/document/d/1UbJ_xnPukO_f2Cw14PmJTM_gxvvx2MRUbGQm52Ly5zU/edit?usp=sharing
Office/tenant relationship diagram: https://www.lucidchart.com/documents/view/b5add676-2ba0-4e16-8024-a053f4bf4855/0_0

ISO18626 messages (XML Schema): http://illtransactions.org/schemas/ISO-18626-v1_2.xsd

ISO18626 guidelines: http://illtransactions.org/guidelines/

All w/guest Sebastian Hammer

Background on work to-date related to cross-tenant unmediated requests

Q: would patron management/sharing be part of central office functionality? A: maybe in some cases
CTUR functionality could be setup/managed individually by each library/tenant, but it would be useful/easier to have a central office manage these aspects (especially if central office functionality is a long-term goal anyway)

Might be some pieces of ReShare that can be reused/repurposed for FOLIO-specific functionality

in ReShare - shared index and consortial directory (IPs, etc.) are managed centrally
centralized brokers make it difficult to pass a request to another consortium or resource sharing relationship

Some discussion about purpose of a FOLIO-specific resource sharing solution; what are the unique requirements that can't be handled by another solution?

10min

Wrap-up/planning

All

10/30 - develop more details about central office functionality/requirements

11/6 - review ReShare

Action items

Browser not supported