1. Summit 3: Knowns and Unknowns Joint Session: Moshe Shechter Anya N. Arnold

2. Agenda Who and When (>5 min) Development Project (>5 min) Demo (=20min) Questions and Comments (=20min)

3. Who SPOT – Kate Cabe, Chair (July 2013-July 2014) – Julie Carter, Chair (July 2014- Post Implementation) – Alex Merrill – Erin Bledsoe – Heidi Nance – Jesse Thomas – Michael Mackin – Nancy Hoover – Council

4. Who Shared ILS Circ Working Group – Chelle Batchelor – Others as needed Alliance – Anya N. Arnold – Keith Folsom – Al Cornish – John Helmer

5. Who ExLibris – Audrey Ho – Asaf Kline – Carmit Marcus – Chen Marckfeld – John Larson – Melissa Hilbert – Moshe Shechter

6. When Meetings every two weeks- big team Meeting every two weeks –Anya and Melissa SPOT every week

7. When Planning – Currently underway Development – August through December Implementation – All 37 members in January

8. Development Summit 3 Dev Project- Review Summit 3 Dev Project Demo Moshe Shechter

9. Discussion

10. Notes taken Summit 3:Knowns & Unknowns 07-10-2014 9am Q&A: - When in January will Summit 3 be available? Actual date TBD - Is there a way to sort Summit requests from others in pick from shelf? Or way to filter to just Summit? Current paging, slips header and monitor request can be already be filtered - What about institutional patrons? No institutional patrons in S3, materials will have different statuses - Can we place requests on behalf of patrons? Yes - Will the slips automatically print? We see it as send a report - Can you use actual barcode on book? Yes as long as the barcode isn't already used in your system. This hasn’t happened throughout NRE - Will there be a delay before notices are sent? There is currently no delay in sending notices in Alma functionality so Summit 3 will have that same functionality, i.e. no delay - How will we send notes to each other? Use general messages options, will show up in your facets - Renewals? Summit not doing renewals - Temp barcode? Will be lenders barcode. - Is there load leveling? There will be, it is manual. Rota is assigned based on configuration - Request number or barcode? Use item barcode - Return something from branch library? Can they use scan in? Depends on configuration. You may set items in transit or may have to log in to your Resource Sharing Library - How does system look at availability? Currently looking at just holdings. Will look at item policies and availability - S3 won't need to clean up temp bibs and items? Should be removed when requests are completed - Multiple piece items? Will try to place item level holds? - Pick up anywhere is coming!