1 of 16

Tipasa

Stefanie Gorzelsky and Sagan Wallace

2 of 16

Concordia’s Stats

3 of 16

Concordia’s Stats

4 of 16

Saint Martin’s Stats

5 of 16

Saint Martin’s Stats

6 of 16

Why Tipasa?

St Martin’s reasoning

  • Moved from a shared local server to hosted solution
  • Migrate roughly around change to new Primo UI
  • Small enough to “risk” new tech

Concordia’s reasoning:

  • Would be switching to Tipasa anyway�
  • Timed migration to correspond with new Primo UI as well as local authentication upgrades (ezProxy -> SAML)�
  • Small enough to “risk” new tech

7 of 16

OCLC migration calendar

8 of 16

Authentication

Saint Martin’s used:

  • Secure LDAP
  • Weekly patron load from Alma analytics to Tipasa - we are willing to share this!

9 of 16

Other authentication options

  • LDAP (must be ldaps/secure LDAP), also available with Provision on Demand
  • SAML-based authentication methods, v2.0 and above (Shibboleth, Okta, Google SAML, etc.), also available with Provision on Demand
  • AD FS, also available with Provision on Demand
  • Microsoft Azure
  • CAS
  • SIP with userObject via EZproxy*
  • III Patron API with userObject via EZproxy*

​

​

*Requires the library to have an EZproxy server (either OCLC-hosted or standalone). Implementation staff will assist you with configuring EZproxy to support Tipasa.

10 of 16

Saint Martin’s go-live

Quiet migration:

  • Did not advertise prior to the change
  • Staff side - picked up the technology quickly
    • Easy conversion of requests created in ILLiad to Tipasa
  • Patron side - only a few called in with issues, most relating to the changed emails in Alma

Overall, a very easy transition

11 of 16

Staff side

12 of 16

13 of 16

14 of 16

Pros ….. & Cons

  • Training syllabus was solid�
  • Article Exchange works well - easy for patrons to find�
  • Patrons like the text message alerts�
  • Easy to configure emails and text messages
  • Training isn’t very customized�
  • Tipasa isn’t fully separated from their other products�
  • Not as many customizations available yet�
  • No way to re-send unfilled request - must clone instead�
  • No user screen to see everything a patron has out at one time

​

15 of 16

Final recommendations

  • Great for smaller institutions�
  • Doesn’t support much customization�
  • No Alma integration - yet. Alma-NCIP integration scheduled for release February 2019

16 of 16

Thank you!

​

Questions?

Contact:

Stefanie Gorzelsky

SGorzelsky@stmartin.edu

​

Sagan Wallace

llermo@cu-portland.edu

​