- Product: Summon
This document describes the Central Discovery Index (CDI) process. 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 in approximately 24-40 hours from submission (with 30 hours being the average).
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, 360 MARC updates that are sent weekly to Summon, and your local collection updates (catalogs, repositories, and study guides) that have been sent to Summon.
Libraries can expect to see brand new local catalog records (not updated or deleted records) in Summon within 24 hours of delivery to the FTP updates folder. In general, daily catalog additions will process within an hour of delivery and become available almost immediately in the Summon search results. For more details, see Increased Frequency of Catalog Additions.
For your Rights Update, any additions or deletions to rights for content that have already been indexed in Summon are generally processed in approximately 24-40 hours from submission (with 30 hours being the average). The length of time to complete the update varies depending on the size and nature of the content being processed. The Rights Update begins at 12:00 midnight Pacific Time (convert to your time zone) along with the Daily Profile Data Refresh, and it will include all changes committed within the previous 24 hours.
Detailed View of 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 CDI. 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))
If you need help determining the Index Updates Submitted day for use in the table above, check the following updates:
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 Index 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.
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 CDI 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: 28-Dec-2020
- Old Article Number: 10414