When Summit is "down"

When we say that Summit is down, it means that the server is down, and it is not available for any functions at all. Summit is down occasionally, for example, for scheduled hardware or software upgrades, or for campus electrical power work.

Local updates: All updates to local bibliographic, item, order, and checkin records will be held at the local site (transaction file and
loading queues) and sent when the link is re-opened.

Pass-through searching will not work since Summit is down. The local catalog will probably display a message to the patron about being unable to connect to the [central] server.

Communications between local sites: Since all INN-Reach communications from one local system to another go through Summit, any activities that require sending a message to another local system will be "on hold." Those messages will be held at the local site until a link with the central system is again established. Summit will automatically re-establish connections with every local system when it comes up.

Summit Borrowing.

Local circ functions (print paging slips, checkout to remote site, checkin, checkout to patron, clear holdhself, return unwanted) will work just fine, but some transactions will be "on hold" until Summit is up again, such as sending the transaction for Institution Checkout to remote site.

Renewal requests: Since we use the option to check Owning Site before allowing a renewal, the renewal request will stay in a pending state until Summit is up.

Visiting Patron will not work since it depends on access to Summit and communication through Summit to the patron's local system, for patron verification.

Pickup Anywhere functions that depend on access to Summit to get information from the PUA database will not work.

updated: April 24, 2006