Restore of Aleph table or screen doesn't take effect **MASTER RECORD**

Description

In trying to implement the Google book search enhancement (SP 1590) for version 18.01, it seems as if www_f_lng/full-set-tail was configured incorrecty. The line changes were inserted after line 29 ( </table>) and after restarting the web server full views of our bib records in the OPAC can no longer be accessed. This is still the case after restoring full-set-tail to its original setting. Why is this?

Resolution

Comparing the ./alephe/www_f_lng screen to the utf_files ( /tmp/utf_files/exlibris/aleph/u18_1/alephe/www_f_lng ), you can see that though the timestamp on the former is from 2004, the timestamp on the latter is from today:
-rw-r--r-- 1 root root 890 May 27 12:05 full-set-tail

When you restore a version of the screen which has an earlier timestamp, the system doesn't recognize it.

The table (/screen) which the system is using is, in most cases, *not* the u22_1/alephe, u22_1/xxx01, etc., table. (Or the ./alephe/www_f_lng screen.) The version actually being used is the $aleph_utf/utf_files/... version. (To verify the exact path, look at the www_server log or the pc_server log, when it does the "load" of the table/screen you will see this.) This extra level was introduced as part of the unicode/utf implementation (to handle the case where the table contains diacritic or special characters).

The system checks the timestamp of the file: If the file in utf_files is the same or later than that in the source table, the utf_files is not updated.

Thus, there are 3 possibilities:
   1) do something to change the timestamp of the source version;
   2) delete the individual file from the utf_files; or
   3) delete all the utf_files, using the util x/7 ("Clean utf_files directory") utility. (The latter may seem kind of drastic but, in fact, since these files are derived from the source files, the only effect is the relatively small one of the server needing to recopy the files.) See also article UTIL X 7 (Clean utf_files Directory) to be executed on a regular basis?

For a general discussion of the case where a new table or screen change does not take effect, see article ALEPH table or screen change doesn't take effect

.

• Article last edited: 1-Sept-2016