ILL2 Unpopulated Status Trees

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

Description:
We've opened several clients, and there's no ILL data in them. There should be requests under these statuses, but the status tree itself doesn't even show correctly.

Resolution:
The problem is caused by missing or empty $alephe_tab / tab_ill_status_borrow and tab_ill_status_lend files.

$alephe_tab / tab_ill_status_borrow and tab_ill_status_lend
Defines what statuses belong to which Status Groups, e.g.,
GNW NEW NEM LOW
If these files are missing, then the GUI left pane Summary mode Status Tree will be empty (see attached image, SKB-16384-107-empty-status.jpg)
The textual description of the group codes and statuses is derived from xxx40 / tab / pc_tab_exp_field.eng (BOR-REQ-STATUS and LEND-REQ-STATUS)

$alephe_tab / tab_ill_tree_bor_msg and tab_ill_tree_lend_msg
Defines what messages belong to which Message Groups, e.g.,
G-MSG 14 20 29 30
If these files are missing, then the GUI left pane Summary mode Message Tree will be empty (see attached image, SKB-16384-107-empty-msg.jpg).
The textual description of the messages codes is derived from xxx40 / tab / pc_tab_exp_field.eng (BOR-REQ-MSG and LEND-REQ-MSG)
The message numbers (not the message group code) correspond to the message codes found in xxx40 / $dt / tab46.eng
(In WebILL, this information was stored in xxx40 / $dt / tab_ill_tree_in_msg and tab_ill_tree_out_msg -- these files can be removed from Integrated ILL.)

xxx40/tab/pc_tab_exp_field.eng setup
Defines status and message codes and translations displayed in the left pane Status Tree for Borrowing and Lending (see SKB-8192-10215 for a detailed list of statuses), e.g.,
BOR-REQ-STATUS L New GNW
BOR-REQ-STATUS L New NEW
BOR-REQ-MSG L Cancel Reply 14

$alephe_tab / tab_ill_status_borrow_txt.eng and tab_ill_status_lend_txt.eng
These are also WebILL files. If they exist in your Integrated ILL setup, they can be deleted (v18 rc 001600).

• Article last edited: 10/8/2013