Today, more than 100 libraries use Tipasa for borrowing and lending, taking advantage of the many benefits of handling these processes in the cloud. OCLC continues to talk to libraries, conduct research, collect feedback during in-person and virtual events, and meet with the OCLC ILL advisory group to further understand the workflows and processes that other libraries have built around their current use of ILLiad. We use that understanding to plan the Tipasa roadmap.

The advisory group members, listed below, include representatives from a wide variety of library types and sizes who currently use ILLiad. These representatives serve a one-year term, and the phase 1 group ended in May 2017. The phase 2 group began their term in June 2017.

Libraries considering a migration to Tipasa can:

Current Tipasa users can access the OCLC Community Center to connect online, share best practices, stay up to date on new product releases and contribute ideas to improve OCLC services. From the Community Center, users can also access Tipasa's Support and Training website, which includes a comprehensive collection of training and documentation resources.

Libraries using Tipasa

  • Alabama A&M University (AL)
  • Albright College (PA)
  • Arkansas State University (AR)
  • Asbury Theological Seminary (KY)
  • Ashford University (CA)
  • Atlanta University Center (GA)
  • Auburn University (AL)
  • Augsburg College (MN)
  • Bellarmine University (KY)
  • Bennington College (VT)
  • Bentley University (MA)
  • Borough of Manhattan Community College (NY)
  • Boyd County Public Library (KY)
  • Brooklyn Law School (NY)
  • Bryn Athyn College (PA)
  • Buena Vista University (LA)
  • Buffalo and Erie County Public Library (NY)
  • Caldwell University (NJ)
  • Central Arkansas Library System (AR)
  • Central New Mexico Community College (NM)
  • Christendom College (VA)
  • Christopher Newport University (VA)
  • Clarke University (IA)
  • College of Lake County (IL)
  • College of Wooster (OH)
  • Columbus State University (GA)
  • Cornerstone University (MI)
  • Cumberland University (TN)
  • Daemen College (NY)
  • Denison University (OH)
  • Dixie State University (UT)
  • Dominican University (IL)
  • Eastern Mennonite University (VA)
  • Eastern Washington University (WA)
  • Eckerd College (FL)
  • Fuller Theological Seminary (CA)
  • Gardner-Webb University (NC)
  • George Washington University Law Library (DC)
  • Grand Rapids Community College (MI)
  • Gustavus Adolphus College (MN)
  • Hampden-Sydney College (VA)
  • High Plains Library District (CO)
  • High Point University (NC)
  • Horry County Memorial Library (SC)
  • Immaculata University (PA)
  • Indiana University East (IN)
  • Indiana University Kokomo (IN)
  • Jet Propulsion Laboratory (CA)
  • John Carroll University (OH)
  • Juneau Public (AK)
  • Kenyon College (OH)
  • Lawrence University (WI)
  • Lenoir-Rhyne University (NC)
  • Lexington Public (KY)
  • Loras College (IA)
  • Lynchburg College (VA) 
  • Manhattan College (NY)
  • Marist College (NY)
  • Missouri State University (MO)
  • Mitchell Hamline School of Law (MN)
  • Montclair State University (NY)
  • Mount St. Mary College (NY)
  • The National Renewable Energy Laboratory (CO)
  • Nebraska Wesleyan University (NE)
  • Neumann University (PA)
  • North Central College (IL)
  • North Park University (IL)
  • Northern Michigan University (MI) 
  • Northwestern College (IA)
  • Ohio Wesleyan University (OH)
  • Palos Verdes Library District (CA)
  • Plymouth State University (NH)
  • Point Loma Nazarene University (CA)
  • Providence College (RI)
  • Queens University of Charlotte (SC)
  • Sacred Heart University (CT)
  • Saint Francis University (PA)
  • Saint Joseph's University (PA)
  • Saint Thomas University (FL)
  • Saint Xavier University (IL)
  • Salem College (NC)
  • Schaumburg Township District Library (IL)
  • Shenandoah University (VA)
  • South Texas College of Law (TX)
  • Southern Adventist University (TN)
  • Southern New Hampshire University (NH)
  • Springfield College (MA)
  • St. Edward's University (TX)
  • Stevenson University (MD)
  • Sul Ross State University (TX)
  • Sweet Briar College (VA)
  • Tampa-Hillsborough County Public (FL)
  • Texas A&M International University (TX)
  • Texas A&M University-Commerce (TX)
  • Trinity International University (IL)
  • Troy University (AL)
  • Tulsa Community College (OK)
  • University of Alabama Huntsville (AL)
  • University of Arkansas Fort Smith (AR)
  • University of Central Missouri (MO)
  • University of Evansville (IN)
  • University of Maine Augusta (ME)
  • University of Minnesota Duluth (MN)
  • University of Missouri - St. Louis (MO)
  • University of Montevallo (AL)
  • University of North Alabama (AL)
  • University of Saint Francis (IN)
  • Ursinus College (PA)
  • Virginia Wesleyan College (VA)
  • Viterbo University (WI)
  • Wabash College (IN)
  • Washington and Lee University (VA)
  • Washington University Law Library (MO)
  • West Virginia Library Commission (WV)
  • West Virginia Wesleyan College (WV)
  • Western Illinois University (IL)
  • Western Kentucky University (KY)
  • Wheaton College (MA)
  • William James College (MA)
  • Worcester State University (MA)

OCLC ILL phase 2 advisory group members

  • Mikki Butcher, James Madison University
  • Nicole Colello, University at Buffalo, The State University of New York
  • Amber Cook, University of South Carolina
  • Kaylin Creason, Bethel University
  • Maureen O’Brien Dermott, Dickinson College
  • Kate Enge, Juneau Public Libraries
  • Caitlin Finlay, Cornell University
  • Robyn Fleming, The Metropolitan Museum of Art
  • C. William Gee, East Carolina University
  • James B. Harper, Wake Forest University
  • Krista Higham, Millersville University
  • Sarah Kasten, University of Notre Dame
  • David H. Ketchum, University of Oregon
  • Carol Kochan, Utah State University 
  • Micquel Little, Claremont Colleges
  • Megan Lounsberry, Louisiana State University
  • Kurt Munson, Northwestern University
  • Melissa Perez, University of Texas at San Antonio
  • Renna Redd, Clemson University
  • Liza Scherff-Neskarikar, Princeton University
  • Zehra Zamin, LOUIS: The Louisiana Library Network

OCLC ILL phase 1 advisory group members

  • Jennifer Acker, Hudson Valley Community College
  • Tina Baich, IUPUI University Library
  • Margaret W. Ellingson, Emory University
  • Jade Erickson, St. Catherine University
  • John de La Fontaine, Occidental College
  • Megan Gaffney, University of Delaware
  • Brittany Heer, Univ of Colorado Health Sciences Library
  • Geneva Holliday, Univ of North Carolina at Chapel Hill
  • Teva Hutchinson, Atlanta Univ Center, Robert W. Woodruff Library
  • Holly Klump, Rivier University Regina Library
  • Aimee Lind, Getty Research Institute
  • Carrie Marten, Purchase College Library – SUNY
  • Meg Massey, Franklin & Marshall College
  • Dawn Mick, Iowa State University Parks Library
  • Kurt Munson, Northwestern University
  • Heidi Nance, University of Washington
  • Shannon Pritting, SUNY Poly
  • LeEtta Schmidt, University of South Florida
  • Hui Sheng, Westchester Library System
  • Kari Sime, Johnson County Library

General questions

What is OCLC's vision for this new service? Why is OCLC doing this?

We are committed to building a new service with all the required capabilities of an advanced, high-volume ILL management system based on input from the advisory group, early adopters and the broader ILLiad community.

As part of OCLC's commitment to our membership it's key that we monitor technology trends and ensure that our member libraries are positioned for success. Moving away from the current client/server architecture on which ILLiad is based is part of this. Many industry tools are moving to the cloud, and this is a natural progression.

We are excited about moving our ILLiad customers to Tipasa.

Do you need to be an ILLiad customer to purchase Tipasa?

Tipasa is an ILL management system that is being built for libraries that need a higher level of functionality than WorldShare ILL provides, including a patron interface, notification service and integration with third parties. This certainly includes the ILLiad library community, but is not limited to that community. Tipasa is available to any library that needs this feature set.

How did you choose the name Tipasa?

Tipasa was an ancient Roman trading city, located in what is now modern-day Algeria. The new service is a cloud-based ILL management system for libraries that want to share and obtain materials through different resources and systems, as well as provide an exceptional experience for the patron. Using this name for an ancient trading city feels connected with sharing knowledge and ILL, and it was not in use by other companies that work with libraries. We asked the community for input on the name and lots of votes were cast including several write-in names. In the end, Tipasa was selected for the name of our new service.   

Watch a short video about the name Tipasa. 

What is Atlas Systems role in the transition?

OCLC and Atlas have been partners for over 15 years, and the migration of ILLiad to the cloud is the culmination of that partnership. OCLC became the exclusive distributor of ILLiad in 2000. In 2008, OCLC and Atlas entered discussions about the eventual need to move ILLiad functionality to the cloud and entered an agreement that anticipated this outcome.

Atlas will remain involved with the ILLiad product through the transition, continuing to handle any needed development work, backup customer support and providing custom services and training. Both companies are in regular communication working together to ensure that ILLiad libraries are well-supported during the transition.

We're proud of our partnership with Atlas and look forward to working with them during this migration.

When will OCLC release more info?

This is a multi-year project that will be rolled out in phases allowing sufficient time for libraries to migrate. Libraries can choose to migrate to Tipasa at a point when their functionality needs are best met. There is a Roadmap and Research Topics document on the ILLiad to Tipasa community center that provides additional information about timeline and features. We will continue to update the community with dates and details as they become available.

What is the long-term support plan for ILLiad?

OCLC and Atlas Systems will continue to support ILLiad for the foreseeable future.

When can I see a demo?

You can watch a short 15-min demo or watch our Feb Product Insights session for a longer Tipasa demo. We will advertise additional demos well ahead of schedule to make sure you have plenty of notice so you can participate.

What about WorldShare Interlibrary Loan? How does Tipasa relate to that service?

These are two different interlibrary loan products on the same platform. WorldShare ILL will continue to be enhanced. Tipasa will include a new feature set to meet the needs of current ILLiad customers.

How will this affect self-hosted ILLiad libraries?

Tipasa is entirely cloud-based, so you won't need to maintain your own servers or annually update software. OCLC and Atlas Systems will continue to support ILLiad for the foreseeable future.

Will all ILLiad customers be forced to move to the cloud-based version, or can those of us who still maintain our own servers continue to do so?

Over time, the ILLiad community will move to Tipasa.  

This is a multi-year project that will be rolled out in phases allowing sufficient time for libraries to migrate. Libraries can choose to migrate to Tipasa at a point when their functionality needs are best met. We will continue to update the community with dates and details as they become available.

What is the reasoning for moving ILLiad to the cloud when ILLiad works well for many clients/customers already?

OCLC's goal in building this new service in the cloud is to make it easier for libraries to use this ILL functionality through our WorldShare platform. The OCLC partnership with Atlas for ILLiad was started in 2000, and almost 20 years later, OCLC is making significant investments in the WorldShare platform and additional services built on that platform. By moving this ILL functionality to the cloud, OCLC will make it unnecessary for libraries to manage a local server or update the software in order to use it. This will save libraries time and money, and it will make the software more accessible to libraries who aren't yet using it.

How can I get involved? *UPDATED*

In each phase of Tipasa development, we will convene an advisory group and will extend invitations to participate and shape our plans. Libraries can also get involved in other activities, such as our usability program and special interest groups. This is your opportunity to provide input, share your workflows and help guide development. We distribute messages to a database of contacts that is pulled out of the Policies Directory and other sources, and we send out information via listservs. If you are concerned that your institution's information is out of date or incorrect, please update the Policies Directory or contact OCLC Support. You can also send an email to let us know that you're interested in usability testing, future programs and advisory groups.

In August 2017, OCLC conducted the first ILL Research Experience Workshop at our headquarters in Dublin, Ohio. Read the report on this workshop. We’ve since held a second workshop in Boston and plan to hold additional workshops in 2018.

Tipasa pricing and functionality questions

What is the price for Tipasa?

The new product will require an annual subscription as it does today. Exact pricing will be shared with each library as it approaches its migration with plenty of time to plan for any budget change.

For specific pricing questions please send an email to libservices@oclc.org.

How is billing handled?

OCLC will switch over billing from ILLiad to Tipasa automatically in the month following go-live. The invoices will say "ILLiad" until your library fully goes live with Tipasa. There's the option to pay monthly, quarterly, or annually. With ILLiad, annual billing was the only option.

I’m concerned about how this shift will impact staffing and budgeting, as our ILLiad customizations have allowed us to save considerably on staffing.

We realize the importance of workflows and automation in libraries' ILL operations and the need to be able to continue to provide your existing levels of service with your existing staff. We have conducted extensive interviews and research with ILLiad libraries to understand and support your workflows. And we continue that research as well as usability testing and interactions with our advisory group to inform our development and rollout of new features.

How will Tipasa allow for customizations? How will it handle current add-on functionality available in ILLiad? How will it work with Relais, DOCLINE, Rapid, etc.? *UPDATED*

Our approach is to rethink resource sharing management functionality and offer an enhanced experience through Tipasa that allows for customized workflows and integration points with services you use regularly, such as Relais, DOCLINE, and Rapid. User experience and design is very much part of our work on this project. Given the complexity of these workflows, we will be working closely with the community to build these capabilities. We are in the process of integrating some of the current ILLiad add-on functionality now as well as conducting research on which integrations will be developed next. We currently are working to integrate RAPIDILL copy requests and Google/Google Scholar.

We have plans to incorporate APIs in a future phase to allow libraries to create custom integrations with their own systems. The Tipasa API task force kicked off in September 2017 with a goal to identify and prioritize the problems that libraries and library developers would like to solve using APIs. The task force plans to have their recommendations completed to share at the OCLC Resource Sharing Conference in March 2018.
Task force members, along with OCLC staff Hank Sway, John Trares and Jennifer Corsi, include:

  • Lauren Ajamie, University of Notre Dame
  • Tyler Ashcroft, Brigham Young University
  • Eric Bivona, Dartmouth College
  • Tim Jackson, University of Albany & IDS Project
  • Ralph Johnson, University of Michigan
  • Shannon Pritting, SUNY Polytechnic Institute
  • Mark Sullivan, IDS Project

How does authentication work in Tipasa? Will the authentication be integrated with the WorldShare Management Services (WMS) patron database?

Tipasa supports a variety of authentication methods including Central Authentication Service (CAS), LDAP/Active Directory, Shibboleth/SAML as well as a basic authentication method.

WMS libraries will use the same patron database with a few modifications for additional ILL fields to authenticate their patrons for both services.   

Do the e-mail notifications support HTML? And how many different notifications are available?

The notification service supports 26 standard e-mail and text notifications (loan available for pick up, overdue notices, etc.), which can be automated or sent manually. Text notifications are part of the core Tipasa functionality and do not require a separate account or any additional costs. Tipasa also includes 50 additional custom e-mail notification templates that can be created for whatever purpose the library needs. The e-mail notifications do not support HTML editing.

We do a lot with server add-ons and custom web forms. Will this sort of functionality be available in the new product?

There are currently three customizable patron request forms available in Tipasa, and our roadmap includes adding additional forms.

Will there be a scanning utility in Tipasa to replace Odyssey?

Tipasa itself will not have an integrated scanner, however, we are working with scanner companies to make our APIs available to them to embed the scanning workflow into Tipasa.

Will libraries be able to integrate non-OCLC requests into Tipasa?

A lending request form and workflow to track those requests is on our roadmap.

Does the copyright element work in conjunction with CCC? Can you submit your copyright payment through the new product? Will we be able to use other copyright services? Reprints Desk?

Tipasa is integrated with CCC's Get it Now service and has copyright tracking and management functions. The copyright functionality continues to be developed and will include the ability to create a batch submission of committed royalty payments to CCC.  We also are in discussions with CCC about adding the ability to pay CCC royalties invoices via IFM. Lastly, we are in discussions with Reprints Desk to include integration with them in our next phase of development.

Will the new product support NCIP? ISO ILL?

ISO ILL is supported in Tipasa, and there are plans to use NCIP to support circulation and ILS integration in a future phase.

Is this a new interface or will any of the ILLiad interface be retained?

Tipasa has a new interface built on the WorldShare platform to meet the needs of ILLiad users now and in the future.

Can you explain the features of the patron interface in Tipasa?

Tipasa includes an easy-to-use interface built with responsive design. It currently includes 3 fully customizable request forms that continue to be populated via OpenURL either via a link resolver or any of your discovery interfaces. The new patron request forms are set up in Service Config and do not require any CSS or HTML skills. During implementation, we provide marketing materials to help you communicate with patrons, and you can simply update your existing library webpage link.

Data security and reporting questions

How will patron data be secured in the cloud?

OCLC holds a global ISO/IEC 27001:2013 certification for our information security management systems (ISMS). Our data protection and access control implementation is regularly monitored and assessed against global information security practices. OCLC systems and applications meet or exceed the data protection requirements of our global patrons and limit access to only approved users or institutions through auditable and controlled means. For more information, please see OCLC's security policy.

Will requests be purged and, if so, after how long?

OCLC's request database retains a rolling 5 years of requests. 

How will reporting/statistics work in Tipasa?

Currently, Tipasa supports a variety of reports that are available within 10 days of month-end via the OCLC Statistics available at stats.oclc.org. We do have plans to provide statistics through a relatively new OCLC service called WorldShare Report Designer, which will take advantage of a universe of ILL data and enable you to build custom reports, charts, and data visualizations to satisfy library, academic, and agency reporting requirements. In addition, querying of request data is available from the Tipasa interface based on data such as title, author, patron department, borrower symbol, request tags, etc.

Current ILLiad subscribers can access OCLC Statistics today to see what's available. You'll need your 9-digit autho and password, which you can request from OCLC Support if you don't know it.

How do we know that a cloud-based system will be reliable?

OCLC uses commercially reasonable efforts to ensure OCLC’s Systems are available 99.5% of the time (the “Up-time Commitment”). The up-time is measured on a monthly basis calculated to include twenty-four (24) hours per day over each month, but excluding from the numerator and denominator in the calculation the duration in time of any temporary shutdowns due to scheduled maintenance, telecommunications, or power disruptions caused by third parties, and any other causes beyond OCLC’s reasonable control. OCLC agrees to notify libraries promptly of any factor, occurrence, or event coming to its attention that may affect OCLC’s ability to meet the Up-time Commitment or that is likely to cause any material interruption in the Services.

In the event of a disaster at OCLC’s primary data center, OCLC will restore services in its secondary center within four hours of disaster declaration.

General enhancements are installed on a bi-monthly or quarterly basis and include new features, improvements to existing features and bug fixes.  Scheduled downtime hours for normal system maintenance and upgrades occur quarterly on Sundays, 2:00 am p.m. - 6:00 a.m. ET.  Between quarterly installs, critical issues are fixed with patch installs.  These installs do not require downtime of the system, and go through the same rigorous testing as quarterly ones.  

Quarterly product updates

Upcoming events


Tipasa users can access the OCLC Community Center to connect online, share best practices, stay up to date on new product releases and contribute ideas to improve OCLC services.  

Tipasa's Support and Training website includes a comprehensive collection of training and documentation resources.

Member stories

Tipasa is making resource sharing more efficient for a wide variety of libraries. Learn more about how your peers are using the service:

University of Saint Francis member story

Share resources with fewer clicks

Discover how the University of Saint Francis simplified interlibrary loan for staff, student workers, and library users.


Simplify resource sharing by using the cloud

See how Ohio Wesleyan University improved services by shifting interlibrary loan processes to the cloud.

Tipasa, the world’s first cloud-based interlibrary loan management system, allows you to manage a high volume of interlibrary loan requests, automate routine borrowing and lending functions, and provide an enhanced patron experience. You can meet users’ needs without heavy IT support, server management or extensive configuration and training.

Service availability

  • Tipasa

    Available in the United States

Learn more

Resource sharing revolutionized
Learn more about OCLC’s plans for resource sharing