1. Summit ILS Team Circulation/Resource Sharing Working Group

2. Group Members: Shirien Chappell, UO Wade Guidry, UPS Bill Kelm, WU Heidi Nance, UW Rick Peterson, L&C

3. Initial Thoughts: Challenges o Needs vary by institutions o Some functionalities may not exist o Must maintain interaction with NRE during migration phase o Patron confidentiality o Maintaining a large loan rule table o Many libraries may still maintain auxiliary services

4. Detailed Spreadsheets: 1. Function 2. What to Look For 3. Mandatory / Desirable 4. Opt In / Out 5. Library Specific Answers

5. RFP - Written Response Outline F.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

6. 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.

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

8. 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

9. 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

10. Feedback Themes In general Confusion/uncertainty about consortial aspects, how one moves between consortial/local Macros/shortcuts with web clients

11. 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

12. Sierra Strengths Code completeness Easier learning curve Easier data migration At present, more complete feature set WRT consortial circ

13. 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.

14. What's next? We'll do what we did last time, adjust our workflows and learn a new system.