Annual Account Reconciliation (AAR)
See the Annual Account Reconciliation Documentation page for schedule details, FAQs, procedures & tutorials, and reports for the AAR process.
This document outlines the statuses that borrowing requests may have. It explains why a request might end up in a particular status and gives recommendations for next steps to take, how frequently to check different statuses, and troubleshooting information.
This document outlines how to create a request on behalf of a patron.
Outlines how to cancel a Summit request from within Alma. This includes cancelling the request from the patron’s account and cancelling the request from the Borrowing Requests queue.
Outlines how to assign patrons to a user group that will allow them to request Summit items. This applies to institutions with multiple resource sharing locations.
This page demonstrates how to receive items using the “Receiving Items” page.
This document highlights using return items (fulfillment menu) as well as returning an item from the borrowing request.
The task list is one way to identify if there are requests or other tasks that need to be worked on in ALMA from the first page. This is a customizable option in Alma which can be displayed, hidden, and moved.
When searching for lending requests the user can use parameters such as external identifier, author, title, requester, and item barcode. Requests can also be narrowed down by facets, activity status, or the “assigned to” tab.
This document explains how to identify when requests stuck in Ready to be Sent with a “Could not Send” error require a workaround, and how to do it.
When and how to use the Duplicate option on inactive requests.
How to dismiss notes from borrowing requests that have been rejected by all potential partners.
This document covers the two ways to clear expired holds on Summit items.
This document outlines the statuses that lending requests may have. It explains why a request might end up in a particular status and gives recommendations for next steps to take, how frequently to check different statuses, and troubleshooting information.
This document explains how to ship individual items manually from the Lending Requests page.
This document explains how to ship items from the Shipping Items page.
On occasion a lending library will need to reject a request. The most common reasons to reject are non-circulating, poor condition and not on shelf.
Sometimes the locate process has difficulty figuring out which item to place the Summit request on at a specific owning library. This can lead to a partial (or failed) locate. The request still gets sent to the lending library, but extra staff mediation is required.
Most lending requests automatically get routed into your Being Processed queue. However every now and then you’ll see one turn up with a status of Created Lending Request. These requests typically require a little extra staff intervention.
This document walks through how to set up printers for circulation desks in Alma, how to enable Quick Printing, and how to generate slips from the Pick From Shelf screen. The process was demonstrated on the recorded Slip Printing Demo Open Call (Video, 54:49) on July 27, 2021.
Outlines how to complete a lending request once the item has been returned to the owning library.
When searching for lending requests the user can use parameters such as external identifier, author, title, and item barcode. Requests can also be narrowed down by facets, activity status, or the “assigned to” tab.
This document demonstrates how a borrower would request a renewal in Primo, and how a staff member can place a renewal request for a borrower through Alma.
A brief guide to setting the Summit Loan TOUs to allow renewals and adjusting the Lending Resource Sharing TOUs to include a maximum renewal date.
The Borrowing Info Letter is triggered when a renewal request comes through Primo. This document shares ideas for editing that notification to make it bit clearer.
Summit Quick Sheet
Occasionally mistakes happen. Reviewing the audit trail is a good way to determine what went wrong. Below are some common errors and their accompanying audit trails.
The history trail is an invaluable resource when it comes to troubleshooting Summit requests. It contains all the partner data that gets relayed back and forth between the borrowing and lending libraries. It archives any status changes that have occurred along the way. And it documents essential operator and timestamp information. By familiarizing yourself with what a normal history trail looks like, it will help you identify procedural missteps and give you a better sense for how to correct these problems when they occur.
Role templates are used to create a customized set of privileges for Alma users.
Summit processors need specific roles to allow them to process Summit requests. This document outlines the roles and scopes that will need to be assigned.
General messages are a way that you can communicate with your partner library concerning item damage, AAR status, general questions about the request, etc.
Why and how to use the three types of notes available to Summit processors: internal, note to partner, and fulfillment.
Instructions for both Lending and Borrowing institutions for processing requests for multi-part volume series.
All Summit libraries are required to offer Visiting Summit Patron borrowing privileges. This document explains how to verify a patron’s eligibility for the program, the role of the local institution vs the patron’s home institution, and its impact on AAR.
This document contains the recommendation to enable “Rejected by partner” as part of the Borrowing Requests Inactive Filters.
Instructions for adding or editing non-Summit eligible locations in the Network Zones Resource Sharing Restriction Rules mapping table.
Alliance Policies and Courier Service
Have a question? Need additional documentation? Let us know through the Feedback Form.