1. How to add a fix procedure for copy cataloging from a Z39.50 base
Yoel Kortick

2. Copyright Statement
All of the information and material inclusive of text, images, logos, product names is either the property of, or used with permission by Ex Libris Ltd. The information may not be distributed, modified, displayed, reproduced – in whole or in part – without the prior written permission of Ex Libris Ltd.
TRADEMARKS Ex Libris, the Ex Libris logo, Aleph, SFX, SFXIT, MetaLib, DigiTool, Verde, Primo, Voyager, MetaSearch, MetaIndex and other Ex Libris products and services referenced herein are trademarks of Ex Libris, and may be registered in certain jurisdictions. All other product names, company names, marks and logos referenced may be trademarks of their respective owners.
DISCLAIMER The information contained in this document is compiled from various sources and provided on an "AS IS" basis for general information purposes only without any representations, conditions or warranties whether express or implied, including any implied warranties of satisfactory quality, completeness, accuracy or fitness for a particular purpose.
Ex Libris, its subsidiaries and related corporations ("Ex Libris Group") disclaim any and all liability for all use of this information, including losses, damages, claims or expenses any person may incur as a result of the use of this information, even if advised of the possibility of such loss or damage.
© Ex Libris Ltd., 2008

3. Introduction
Slides 4 to 15 will show an automatic fix procedure which adds the format to records which are copy-catalogued from the Library of Congress
Slides 16 to 26 will show an automatic fix procedure which does the above and also deletes certain fields from records which are copy-catalogued from the Library of Congress

4. Why do we need the fix procedure - 1
Here we search for a record in the library of Congress which is set up as a Z39.50 base

5. Why do we need the fix procedure - 2
After clicking “show” in the lower pane the record appears
We will now click “Catalog” in the upper pane or “Cataloging” in the lower pane
There is no FMT field here

6. Why do we need the fix procedure - 3
When record appears in cataloging edit mode we will choose “duplicate record”.

7. Why do we need the fix procedure - 4
The format of the duplicated record is XX.
We therefore need to manually change it.
Instead we will make a fix procedure which will automatically make it BK

8. Why do we need the fix procedure - 5
Even after saving the record it remains XX

9. Making the fix procedure
We will add a fix procedure to $alephe_gate/loc.conf which will add the FMT field based on the contents of the LDR field of the record.
aleph113-19(1) USM01-ALEPH>>cd $alephe_gate
aleph113-19(1) USM01-ALEPH>>diff loc.conf loc.conf.orig
23c23
< Z58-IN-RECORD-FIX FMT
---
> Z58-IN-RECORD-FIX
We have defined that the fix procedure used by loc.conf (loc.conf is the definitions for Library of Congress) is FMT.
We could have called it anything, as long as we put it in tab_fix as it appears in loc.conf.

10. Making the fix procedure
We will add the FMT fix procedure to $data_tab/tab_fix of the EXT01 library
EXT01 is the library used for all Z39.50 connections which use USMARC !
!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!>
FMT fix_doc_create_fmt
The next slide will explain what fix_doc_create_fmt does.
To get new definitions we restart PC server and Z39 gate server

11. Making the fix procedure
From the “Aleph 20 Syslib Guide – Cataloging”:
fix_doc_create_fmt This program, according to the definitions of the LDR field, adds the FMT field with the record format (for example, BK for books). The program can be used to add the FMT field to records imported through the Z39.50 server that do not have the FMT field. If the field is present, the program does nothing.

12. Searching again the LOC via Z39.50
Now we will again search and view catalog records from Z39.50 and see that they already have a FMT field (unlike before the fix procedure)
Compare with slide 5 where there is no FMT field for the same record

13. Searching again the LOC via Z39.50
This record has FMT with SE based on LDR field

14. Copy cataloging a record
When we click “Cataloging” the record appears in cataloging edit mode with the correct format

15. Copy cataloging a record
We can then duplicate the record and save it in our library without manually changing the record

16. Another fix procedure
We will now make another fix procedure which will do the same as the previous fix procedure but also delete fields 906, 925 and 955.
These fields will be deleted automatically as the record comes from the Library of Congress top the Aleph 500 GUI.

17. Why do we need the fix procedure - 1
Here we search for a record in the library of Congress which is set up as a Z39.50 base
We search for “libraries and ancient and Timbuktu”

18. Why do we need the fix procedure - 2
After clicking “show” in the lower pane the record appears
We will now click “Catalog” in the upper pane or “Cataloging” in the lower pane
See fields 906, 9250 and 955

19. Why do we need the fix procedure - 3
When record appears in cataloging edit mode we will choose “duplicate record”.
We do not want these fields

20. Why do we need the fix procedure - 4
The record now has the undesired 906, 925 and 955 fields after duplicating to USM01.
Now we need to manually delete them

21. Why do we need the fix procedure - 5
We want a fix procedure which will not only add the FMT field (as in the previous slides) but also delete fields.
In this case we want it to delete the 906, 925 and 955 fields.

22. Making the fix procedure
We will add a fix procedure to $alephe_gate/loc.conf which will add the FMT field based on the contents of the LDR field of the record and delete other fields.
$alephe_gate
loc.conf loc.conf.orig
23c23
< Z58-IN-RECORD-FIX FMTDL
---
> Z58-IN-RECORD-FIX
We have defined that the fix procedure used by loc.conf (loc.conf is the definitions for Library of Congress) is FMTDL
We could have called it anything, as long as we put it in tab_fix as it appears in loc.conf.
We called it FMTDL because it sounds a bit like “Format” and “Delete”.

23. Making the fix procedure
We will add the FMTDL fix procedure to $data_tab/tab_fix of the EXT01 library
EXT01 (we already explained) is the library used for all Z39.50 connections which use USMARC
! !!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!> FMTDL fix_doc_create_fmt FMTDL fix_doc_do_file_ del
We already explained what fix_doc_create_fmt does.
Let’s see the del fix procedure in ext01 $data_tab/import

24. Making the fix procedure
Here is ext01 $data_tab/import/del !
!-!!!!!-!!-!-!!!-!!!-!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!! 1 906## DELETE-FIELD 1 925## DELETE-FIELD 1 955## DELETE-FIELD
For more information on home made fix procedures see the following two files on the Doc Portal under Aleph > Tree Search > How to from support > Miscellaneous
How_to_make_home_made_fix_procedures_parameters.ppt
How_to_make_home_made_fix_procedures_examples.ppt

25. Searching again the LOC via Z39.50
Now we will again search and view catalog records from Z39.50 and see that they already have a FMT field (unlike before the fix procedure) and the 906, 925 and 955 fields are gone
We of course also restart the z39 gate server via util W 3 5
Compare with slide 17 and see that now the fields 906, 9250 and 955 are gone

26. Searching again the LOC via Z39.50
This record has FMT with BK based on LDR field and the 906, 925 and 955 fields are automatically deleted.

27. Copy cataloging a record
We can then duplicate the record and save it in our library without manually changing the record
Fields 906, 9250 and 955 are gone