Intota Discussion

Instead of a standard presentation/demo, we got to sit down with a couple people and simply discuss what the library is looking for and what the vendor is selling. Hopefully my notes make sense.

What are Your Pain Points?

Interoperability is key. The pain for us is that our current systems are not interoperable. Allows each system to specialize in what they’re meant for, connecting them the way we want to.

Current system too much of an expensive black box.


  • Modern architecture
  • Ability for in-house development, and extensible
  • Cost

Vendor Comments

The rest of the post was lead by the vendor but comments are not all necessarily made by the vendor.

  • Summon is a discovery system and continues to be developed independently.
  • Knowledge base in one system because reduce maintenance.
  • Focus of interoperability with student systems, finance, and other campus systems.
  • SaSS model

Hearing pain points from others

  • Assessment esp. collections e.g. usage of e-resources
  • PDA is laborious


  • Intota Assessment
    • October 2013
    • analytics to create a single report on collection.
    • Components include ILL, Google books, Summon. e.g. cost per use, number of core items
  • Inotota E
    • Early 2014
    • covers ERM, PDA, ingested by Summon.
    • Partnered with ebrary.
  • Intota
    • Late 2014
    • what could replace the ILS
  • knowledge base sits at the centre of all of them
  • All the services will be wrapped in an API.

Solving Pain Points

  • Workflows
  • System maintenance
  • Assessment

Areas of Focus

  • Unified, intelligent workflows
  • Knowledge base – needs to be accurate, current, comprehensive
  • Interoperable
  • Assessment


  • seamless for other Intota libraries, use API for third party such as RACER, but all managed through Intota


  • FRBR model
  • RDA toolkit
  • Knowledge base with print from other sources as necessary, but ability to make changes locally
  • Add to orders very easily, can add/edit existing, and place orders.
  • Supports different types of metadata schemes: MARC, Dublin Core, MODS
  • Pulls whatever information it can find

Full fund accounting

  • Can add tags to different funds


  • Pulling in templates


  • Browser based
  • Will be for desktop and Tablet
  • Meets Accessibility Guidelines: Section 508


  • Annual based on FTE and size of collection

Comparison to Competitor

  • WorldShare is the old model thrown in the cloud, without the necessary functions for an academic library.
  • Alma is crowd sourced knowledge base with a very different approach. Less experienced with SaSS.

Author: Cynthia

Technologist, Librarian, Metadata and Technical Services expert, Educator, Mentor, Web Developer, UXer, Accessibility Advocate, Documentarian

Leave a Comment

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: