• Article Type: General
• Product: Aleph
• Product Version: 16.02

Description:
In both out TEST and PROD versions, tags - links 650, 700, 651, 800 receive a No Services Box and the message (No Services Were Found)

I am finding this consistent with all records in Aleph, both TEST and PROD. When displaying a full view of a record and clicking on the links for subject (650, 651) Added Entry (700) and Person Series Entry (800) when clicked on, receive the form service-no-service, however, the pop-up says for the most part "No Services Were Found". A 651 took me to the form and there was an Authority Search and this is what it says (Search (All) Large type Book)). A 700 tag (Added Entry) on some records takes me to the Other Services and does display the FInd, Browse, Authority search capabilities. So, some seem to work and most do not.

I do not know if this is related to our reindexing and we did not catch it in TEST as we reindexed and now caught it in PROD as users are testing more explicitly. Our TEST server has the latest service packs installed, not implemented, but out PRODUCTION does NOT have the SP's installed.

My client seems to belive that this did work at one time and I would agree with that as I assume I would of seen this by now.

Resolution:
It appears that your $data_tab/tab00.eng file was changed relatively recently, and that it is no longer in synch with your $data_tab/tab_service table. In tab_service, you specify which services are to be run for each type of hyperlink, and which indexes these services should use for their searches. In your tab_service, you have all 6XX fields pointing to the SUL and SUM indexes, but these indexes are not defined in your tab00.eng. For your 8XX fields, you are using the SRS index, which is also no longer defined in tab00.eng.

Since you have just reindexed, and it is likely that tab00.eng contains the correct index names for your new indexes, you will probably need to update the tab_service file to include the names of your current indexes. After you do this, you will need to restart your www_server processes.

• Article last edited: 10/8/2013