Summit ILS TeamCirculation/Resource Sharing

Working Group

Group Members:

Shirien Chappell, UOWade Guidry, UPSBill Kelm, WUHeidi Nance, UWRick Peterson, L&C

Initial Thoughts:

Challengeso Needs vary by institutionso Some functionalities may not existo Must maintain interaction with NRE during

migration phaseo Patron confidentialityo Maintaining a large loan rule tableo Many libraries may still maintain auxiliary

services

Detailed Spreadsheets:

1. Function2. What to Look For3. Mandatory / Desirable4. Opt In / Out5. Library Specific Answers

RFP - Written Response OutlineF.3.1. Borrowing & Lending Processing

F.3.1.1. Local (single institution)

F.3.1.2. Consortial (Alliance)

F.3.1.3. Interlibrary Loan (non-Alliance) F.3.2. Circulation

F.3.2.1. Administrative

F.3.2.2. Billing and Payments

F.3.2.3. Bookings / Scheduling

F.3.2.4. Check-in / Check-out

F.3.2.5. Collection Management

F.3.2.6. Course Reserves

F.3.2.7. Patrons

F.3.2.8. Patron Self-Service

F.3.2.9. Support and Training F.3.3. Statistics and Reporting

Circulation Demo Scripts

Start with local and then cover the consortial aspect.

Way too much for one hour.Need to keep our presenters on task.

Vendor Demonstrations

Ex Libris - Looks good.Innovative - Looked very familiar.OCLC - Looks like some progress.Serials Solution - Looks like great ideas.

Feedback Themes

III• safe choice, familiar• concerns about hidden costs• unclear which components are included• same old, same old - "Millennium with

some makeup"• Encore - love it or hate it

Feedback Themes

ExLibris• seems mostly cooked but still forward

looking• strong reporting/analytics• concerns about sets/processes as

substitute for "create list"• concerns about print serials control• Primo looks solid, some are worried about

the latency from the backend

Feedback Themes

In general

• Confusion/uncertainty about consortial aspects, how one moves between consortial/local

• Macros/shortcuts with web clients

Alma Strengths

• patron notification history• Ad hoc messaging to patrons• consortial circulation rule sharing• single-vendor integration with Primo• sophisticated rota management• new code base• nicer analytics interface

Sierra Strengths

• Code completeness• Easier learning curve• Easier data migration• At present, more complete feature set

WRT consortial circ

Final Thoughts

There will be specific questions that library staff have, that unfortunately will not be answered until after a decision is made tomorrow.

We have a potential to be working with three systems for awhile.

What's next?

We'll do what we did last time, adjust our workflows and learn a new system.