- Article Type: General
- Product: Aleph
- Product Version: 20
We ran p_manage_01 as part of our upgrade from v17 to v20. The record counts for many searches are lower in v. 20 than the same searches in v. 17 -- this, despite the fact that the tables used for the indexing (tab00.eng, tab11_word, tab_expand, etc.) have not changed.
The differences in the keyword results in v20 vs. v17 are due to the "WORD expand_doc_bib_accref" in tab_expand.
The expand_doc_bib_accref causes all the words from the headings which are cross-references (non-preferred headings) for the headings in the doc record to be indexed as though they were in the record. As noted in KB 6715: "This means that users retrieve records which don't contain the term(s) they searched on. This can puzzle them. Most North American sites don't use this."
The abc01 Headings index was deleted by the p_manage_102 run you did. (See below.) Since there was no ACC Headings file for p_manage_01 to look at when it was running, it didn't expand any of the words from non-preferred headings.
p_manage_102, the first step in the Headings job sequence, failed. It deleted the existing z01 and z02, but failed to build a new one. This can be seen in the sta01 $data_scratch/p_manage_102.cycles file.
Thus, the complete Headings sequence: p_manage_102, p_manage_02, and p_manage_17 needs to be run.
My personal feeling is that the expand_doc_bib_accref is not desirable and that you should just leave the Words index as is. But, if you want to, you can re-run p_manage_01 once the Headings have been restored and the expand_doc_bib_accref will then get the words from the non-preferred headings....
- Article last edited: 10/8/2013