1. Building bases according to sub library
Defining the tab_base.lng for optimum performance
Version 16 and up
Presenter: Yoel Kortick

2. All of the information in this document is the property of
Ex Libris Ltd.  It may NOT, under any circumstances, be distributed, transmitted, copied, or displayed without the written permission of Ex Libris Ltd.
The information contained in this document has been prepared for the sole purpose of providing information for the 2nd line support meeting.  The material herein contained has been prepared in good faith; however, Ex Libris disclaims any obligation or warranty as to its accuracy and/or suitability for any usage or purpose other than that for which it is intended.
© Ex Libris Ltd., 2006

3. Introduction
It is possible to build logical bases according to sub library
Each base is built according to an expanded field called WSL (Word from sub library)
The WSL field is created from the sub library code in the Z30 item

4. Introduction The logical base is built via a CCL command
The CCL command may contain wildcards and/or Boolean operators
The structure of the CCL command influences the speed at which results are produced
This demonstration will show the structure of CCL command and the way to structure them for optimum speed performance

5. Introduction
Before getting directly to the subject at hand we will give a brief overview of how bases may be created via sub libraries
This brief overview will include a small explanation of a specific expand procedure

6. tab_sub_library.lng
We have the following three sub libraries in $alephe_tab/tab_sub_library.eng !
!!!!!-!-!!!!!-!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!-!!!!!-!!!!!-!!!!!-!!!!!
CAMPN 1 USM50 L Northern Campus A 16A 17A CAMPN ALEPH
CAMPS 1 USM50 L Southern Campus A 16A 17A CAMPS ALEPH
CAMPD 1 USM50 L Downtown Campus A 16A 17A CAMPD ALEPH

7. The expand procedure
An expand procedure called expand_doc_bib_loc_usm creates an “expanded” field called SBL.
This procedure may appear multiple times in BIB library $data_tab/tab_expand, each time with a different expand menu.
Each expand menu performs a different function, and is explained in the table header.
The expand menu which is of interest to us is the WORD menu. The menu performs indexing via manage_01 and ue_01. Here is the explanation from the header:
! WORD p_manage_01_a create word indexing (Service)
! ue_01_w internal program

8. The expand procedure
Here are the occurrences of expand_doc_bib_loc_usm in tab_expand: !
!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!>
WORD expand_doc_bib_loc_usm
ACC expand_doc_bib_loc_usm
INDEX expand_doc_bib_loc_usm
SORT-DOC expand_doc_bib_loc_usm
WEB-FULL expand_doc_bib_loc_usm
WEB-BRIEF expand_doc_bib_loc_usm
WEB-FULL-1 expand_doc_bib_loc_usm
GUI-BRIEF expand_doc_bib_loc_usm
CREATE-Z13 expand_doc_bib_loc_usm
PRINT-REC expand_doc_bib_loc_usm
PRINT-COL expand_doc_bib_loc_usm
PRINT-CAT expand_doc_bib_loc_usm
TAB33-DOC expand_doc_bib_loc_usm
Z39_SERVER expand_doc_bib_loc_usm
RET expand_doc_bib_loc_usm
SECTION1 expand_doc_bib_loc_usm
EXPORT-03 expand_doc_bib_loc_usm
Z39_HOL expand_doc_bib_loc_usm
PUBLISH expand_doc_bib_loc_usm

9. The item with sub libraries
System number is a bibliographic record with two items attached which have sub library CAMPS and one item in sub library CAMPD:

10. The expand procedure via UTIl F / 4
If we view the record in UTIL F/4/doc_expand using expand menu WORD we see an SBL field created for each sub library:
enter file name (or q to exit) doc_expand
Enter expand_menu [No Expand]: WORD
Load: /exlibris/aleph/a18_1/alephe/unicode/unicode_case
ENTER DOC NUMBER : 36993
[other bibliographic data]
SBL L $$aCAMPD
SBL L $$aCAMPS

11. The expand procedure And because of the WEB-FULL menu in tab_expand…!
!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!>
WORD expand_doc_bib_loc_usm
ACC expand_doc_bib_loc_usm
INDEX expand_doc_bib_loc_usm
SORT-DOC expand_doc_bib_loc_usm
WEB-FULL expand_doc_bib_loc_usm
WEB-BRIEF expand_doc_bib_loc_usm
WEB-FULL-1 expand_doc_bib_loc_usm
GUI-BRIEF expand_doc_bib_loc_usm
CREATE-Z13 expand_doc_bib_loc_usm
PRINT-REC expand_doc_bib_loc_usm
PRINT-COL expand_doc_bib_loc_usm
PRINT-CAT expand_doc_bib_loc_usm
TAB33-DOC expand_doc_bib_loc_usm
Z39_SERVER expand_doc_bib_loc_usm
RET expand_doc_bib_loc_usm
SECTION1 expand_doc_bib_loc_usm
EXPORT-03 expand_doc_bib_loc_usm
Z39_HOL expand_doc_bib_loc_usm
PUBLISH expand_doc_bib_loc_usm

12. The expand procedure in web name tags
We can see the sub library in the “name tags” view of the web

13. The expanded field in tab11_word
The SBL field which we saw via UTIL F/4/doc_expand word is sent to a WSL field via tab11_word
enter file name (or q to exit) doc_expand
Enter expand_menu [No Expand]: WORD
Load: /exlibris/aleph/a18_1/alephe/unicode/unicode_case
ENTER DOC NUMBER : 36993
[other bibliographic data]
SBL L $$aCAMPD
SBL L $$aCAMPS
il-aleph02-18(1) USM01-YOELK>>grep SBL tab11_word
SBL WSL
The SBL field is created via expand procedure and then sent to index WSL

14. The expanded indexed field in CCL search
Because the WSL is a word index “like all other” word indexes, it may be searched via the GUI or web:

15. The expanded indexed field in CCL search
Wildcard searches may also be used
WSL=camp* [all records with a sub library beginning with camp]
WSL=ca* [all records with a sub library beginning with ca]

16. The expanded indexed field in CCL search
Boolean searches may also be done. Here we search for:
(WSL=campd) OR (WSL=campn) OR (WSL=camps)

17. The expanded indexed field in CCL search
Here are the three CCL searches we did, and how they rank in order of speed in producing results:
CCL Command
Speed
(WSL=campd) OR (WSL=campn) OR (WSL=camps)
Fastest
WSL=camp*
2nd Fastest
WSL=ca*
3rd Fastest

18. The CCL search in tab_base.lng
Because bases in tab_base.lng may be made via any CCL command, the bases may be built as follows: !
!!!!!!!!!!!!!!!!!!!!-!-!!!!!!!!!!!!!!!!!!!!-!!!!!-!!!!!-!!!!!-!!!!!-!-!!!!!!!!!>
DOWNTOWN_CAMPUS Downtown Campus CAMPD USM01 N wsl=campd
NORTHERN_CAMPUS Northern Campus CAMPN USM01 N wsl=campn
SOUTHERN_CAMPUS Southern Campus CAMPS USM01 N wsl=camps
ALL_CAMPUSES All Campuses ALLCA USM01 N (wsl=campd) OR (wsl=campn) OR (wsl=camps)
!* ALL_CAMPUSES All Campuses ALLCA USM01 N wsl=camp*
!* ALL_CAMPUSES All Campuses ALLCA USM01 N wsl=ca*
For Northern Campus we have wsl=campd
For Southern Campus we have wsl=campd
For Downtown Campus we have wsl=campd

19. The CCL search in tab_base.lng
For a base of all campus we could have either of the following three options, and they would all work: !
!!!!!!!!!!!!!!!!!!!!-!-!!!!!!!!!!!!!!!!!!!!-!!!!!-!!!!!-!!!!!-!!!!!-!-!!!!!!!!!>
ALL_CAMPUSES All Campuses ALLCA USM01 N (wsl=campd) OR (wsl=campn) OR (wsl=camps)
ALL_CAMPUSES All Campuses ALLCA USM01 N wsl=camp*
ALL_CAMPUSES All Campuses ALLCA USM01 N wsl=ca*
However, because of the performance ratings previously noted, it would be:
best to have (wsl=campd) OR (wsl=campn) OR (wsl=camps)
2nd best to have wsl=camp*
3rd best to have wsl=ca*

20. The CCL search in tab_base.lng
Thus for optimum performance tab_base.lng, in this case, should look like this: !
!!!!!!!!!!!!!!!!!!!!-!-!!!!!!!!!!!!!!!!!!!!-!!!!!-!!!!!-!!!!!-!!!!!-!-!!!!!!!!!>
DOWNTOWN_CAMPUS Downtown Campus CAMPD USM01 N wsl=campd
NORTHERN_CAMPUS Northern Campus CAMPN USM01 N wsl=campn
SOUTHERN_CAMPUS Southern Campus CAMPS USM01 N wsl=camps
ALL_CAMPUSES All Campuses ALLCA USM01 N (wsl=campd) OR (wsl=campn) OR (wsl=camps)
And when user searches in web he will have high speed searches.