Good morning,
Some quick notes for context – as you know, MIT is currently in the planning stages of migrating to Ex Libris’ ALMA LMS. The past few years have been busy in the resource sharing world as OCLC has developed Tipasa (designed to replace ILLiad) and then after significant feedback from their user community extended the lifespan of ILLiad indefinitely, so this is certainly interesting, if not conclusive, news.
From: bounce-123589176-75349504@list.cornell.edu <bounce-123589176-75349504@list.cornell.edu> On Behalf Of Heidi Nance
Sent: Monday, May 6, 2019 7:59 AM
To: Supports resource sharing among Ivy Plus libraries <ipl-resourcesharinggroup-l@list.cornell.edu>; BD-PARTNERS-L@list.cornell.edu
Subject: *Announcement* Ex Libris and Resource Sharing (was "FW: Ex Libris Announcement Yesterday")
Hello Resource Sharing Colleagues,
As some of you may have heard by now, Ex Libris announced their planned development of a “Next Generation Resource Sharing System” at last week’s ELUNA conference.
You may recall that at ALA Annual 2018, I – in my capacity as convener of the Consortial Approaches to Resource Sharing (CARS) group – approached Ex Libris to request that they ensure that their products and services use standard Resource Sharing protocols vs. proprietary APIs in order to be interoperable with future Resource Sharing Systems (including but not at all limited to ReShare). Ex Libris followed up with an in-person meeting with myself, Jill Morris (ED PALCI), Susan Stearns (ED BLC), Sydney Thompson (TRLN), Dvir Hoffman (Ex Libris), Jane Burke (Ex Libris) and Asaf Kline (Ex Libris) on October 3rd, 2018 at the New School in New York City, NY to discuss Resource Sharing Futures. At this meeting, it was clear that Ex Libris was trying to determine whether to build a competitor product to ILLiad/Tipasa and/or any other future Resource Sharing systems. Our group unanimously emphasized that our goals was not to move to another monolithic system, but rather to ensure that any and all RS products and services were affordable, sustainable, met or exceeded functional needs of many types of libraries, and used standard protocols to pass requests between systems. We made clear that one possible way for this to happen was to have a diversity of Resource Sharing solutions – all interoperable – to ensure effective competition in the marketplace.
It appears that Ex Libris has, as a result, decided to enter the standalone Resource Sharing products and services market.
So what does this mean for IPLC? Chris Bourg (MIT, UL Chair), on behalf of the UL’s group, has directed the RSG to focus on evaluating the TRLN proposal for BDSI Discovery until June 16. Only then should we consider turning our attention to evaluating other and/or Fulfillment products and services. To that end, I will put this RSG’s July agenda for further discussion about whether or how to take any action.
Also, a friendly reminder that in order to ensure consistent communication regarding IPLC Resource Sharing matters, if any vendor or product/services provider approaches you to discuss “what IPLC thinks” about their RS product/service, please redirect them to me as the UL-appointed representative of these matters for IPLC overall.
Please feel free to share this information with others at your library as needed. Please refrain from sharing my above comments with anyone outside of IPLC at this time.
Thank you!
Best,
Heidi
0 Comments.