- Product: Summon
What is the status of the Summon Index?
This document delineates the status of the Summon Index. Content is currently being updated twice a week in our Index Updates. Based on a standard volume of data being processed, an updated index is released on Wednesday and Friday (Thursday and Saturday for Asia Pacific libraries, due to the international dateline). Rights for that content is updated in a nightly Rights Update. Changes to content rights are completed approximately 48 hours or less from being submitted.
Timeframe Needed for Content Changes to Appear in Summon
As a general guideline for adding, deleting, or changing content as part of the Index Update, you can expect your holdings updates to appear in Summon within 4 to 7 days. This timeframe applies to holdings updates you make in the Client Center or Intota, and to updates to your local collections (catalogs, repositories, and study guides) that have been sent to Summon.
For your Rights Update, any additions or deletions to rights for content that has already been indexed in Summon are generally processed in 48 hours or less from the time of submittal. The process begins at 12:00 a.m. (midnight) Pacific Time (convert to your time zone) along with the Daily Profile Data Refresh, and we process all changes committed within the previous 24 hours. The Rights Update can take up to 24 hours depending on the size and nature of the content being processed.
For a detailed view into the processing timeframe:
It is important to note that this information provides a set of expectations for when a library can anticipate seeing holdings updates reflected in the Summon Index. With an index of more than 2 billion items, it is inevitable that from time to time the volume of data being processed leads to issues that cause delays to the standard schedule. The best way to stay informed about processing delays is to receive an email alert; to subscribe to the alert, visit the System Status page.
|Index Updates Submitted||Index Updates Go Live in the Index|
Saturday, Sunday, Monday
(Asia Pacific libraries: Sunday, Monday, Tuesday)
(Asia Pacific libraries: Saturday)
Tuesday, Wednesday, Thursday, Friday
(Asia Pacific libraries: Wednesday, Thursday, Friday, Saturday)
Wednesday (the following week)
(Asia Pacific libraries: Thursday (the following week))
In most cases, Rights Updates are updated within 48 hours of being submitted, depending on the size and nature of content being processed in the Rights Update process.
If you need help identifying which Index Updates Submitted day applies to a change you have made for:
- Client Center or Intota updates: Within your Client Center or Intota profile, you can see what day you made a particular holdings update. Use that day as the Updates Submitted day in the table above (to find the day you made a particular holdings update, Client Center users see the View Changes page, Intota users see the View Recent Updates page).
- Local collection updates: If you subscribe to Content Ingestion Reports, see the processing date listed in the report. Use that day as the Updates Submitted day in the table above (for more information about ingestion reports see the Content Ingestion Report page).
Note that an export of a library's full catalog does not align with the above timeframe for index updates and deletions. New full loads require additional validation work conducted by our metadata librarians, and a library should expect a new full load to go live in the Index a week to ten days after uploading to the Summon FTP server.
If Summon is not displaying holdings updates that should be indexed in Summon according to the information above, see Missing Article or Book Citation in Search Results.
Please keep in mind that changes made to e-resources in your Client Center or Intota profile also require an index update to appear in Summon. This is in addition to the nightly cache build, which will make changes visible in your E-Journal Portal/360 Link sites for patrons the following day. So it is important to remember that the Summon Index processes updates based on this nightly cache build process. See Client Center: Daily Profile Data Refresh (Cache Build) for more information.
- Date Created: 20-Feb-2014
- Last Edited Date: 08-Mar-2018
- Old Article Number: 10414