Index taking unusually long
Symptom
- Collection index is taking longer than normal to complete
Applies to
- CONTENTdm
Additional information
Certain factors can trigger an additional index operation in a collection that will take longer to complete.
- Field Additions/deletions
- Search field 'yes/no' changes
- Controlled vocabulary add/disable
Please allow the collection to complete indexing or for twenty-four hours to elapse before contacting OCLC Support to report indexing issues.
Occasionally, indexing can last longer than twenty-four hours. When this happens, the Index status message can incorrectly display a "Last index successful" statement. If the timestamp for this statement predates when the last index was initiated, then the index is still ongoing. You can also access the indexing log directly at the following CONTENTdm Administration URL: https://server#####.contentdm.oclc.org/cgi-bin/admin/getfile.exe?CISOMODE=1&CISOFILE=/alias/index/description/log.txt
In the address above, the variables for #####
and alias
must be substituted with the correct server ID and desired collection. The index is still ongoing if the last entry in the log reads:
YYYY-MM-DD HH:MM:SS index start
NOTE: The amount of time required to complete an index will depend on the size of the collection. Best practice would be to make all your changes at once and kick off the index at the end of the day or a time that is convenient for your organization.