2023-5-16 - Consortia SIG Notes

5

Announcements

Dennis back at May 30 meeting to discuss our questions.

• Timeline for app?  

• When and how might we be able do testing?

• Further developments planned?

• Did his team have feedback on our use cases?  Survey?  

• Attendance at future meeting to continue discussion?  

5

Request for volunteer on documentation

Working with the documentation group, from the Consortia pov, docs.folio.org has documentation for each of the apps. So far there is no consortia documentation, and we’ll need some with Poppy release. Christine Tobias is your contact for questions. Slack or email tobiasc@msu.edu.  This is scholarly activity/service toward your continuing appointment!

• Lucy is interested and offered to explore the possibility with Christine

2

WOLFcon!

Need proposals submitted.  Would be good to build momentum on the Consortia development work starting

33

GALILEO/Georgia RFP

Lucy Harrison

Haven’t yet signed a contract. Looking forward to next two years of migrating.

FOLIO/EBSCO/ReShare package
Panorama Full (analytics platform that combines data sets in a central place from different library and campus systems)
EBSCO Usage Consolidation and Loading service
HoldingsIQ (Automated module for managing holdings data from different sources)

18 members of evaluation team for RFP.  Big process, took their time.

Publishing timeline and have lib guide with the logic/principles behind moving to FOLIO

Scope

• implement FOLIO, ReShare, Panorama

• evaluate OPAC Locate vs EDS

Summer 2025 go live

EBSCO Approach will be

• 27 separate standalone setups for each library, then tie them together (Consortial features)

• each institution will see their own stuff first, then can expand to see what other members have

Could add in other Georgia libraries later, not Day 1

Open to either single tenant with multiple libraries or a multi-tenant system

• EBSCO originally suggested a single tenant, but shifted to a multi-tenant approach after learning more about GALILEO's needs and from the MOBIUS contract.

• Current set-up on Alma involves a network zone with individual library zones

GALILEO currently uses EDS for discovery and Primo for the OPAC

• A few libraries have chosen a different set-up and use Primo for discovery as well

• The main GALILEO portal uses EDS for discovery ; multiple layers of collection/access

• All libraries have OpenAthens

• Management of the system varies between libraries: some are self-managed while others have GALILEO or EBSCO provide the service

ReShare expectations

• GALILEO wants development to allow patrons to seamlessly request materials (unmediated) from other libraries, to visit other libraries and have borrowing privileges, and to drop-off borrowed materials at any library for return to their home library ; commonly referred to as DCB (direct consortial borrowing)

• Libraries want to control their own data while be able to participate in resource sharing

• Expect to benefit from the work being done by K-Int for MOBIUS

• Development will likely change FOLIO to enable integration 

The contract is still in negotiation.  

• Expected to be signed by end of June

• Still reviewing a few developments and special issues including the continued relationship between Georgia Tech & Emory University