Skip to main content
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    Bib record additions and changes don't dynamically update ADM Z13 or Z00R

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

    We recently ran p_manage_07 for each of the 5 ADMs in our database, in order to fully populate the z00R tables. [Note: You may want to do this for the ADM Z13 in addition or instead.] In monitoring these tables since then as additions and changes are made to bibliographic records, it appears that additions of new bib records are reflected in new z00R records, but changes to existing bib records by means of the Cataloging GUI do not result in changes to the relevant z00R records.

    For example, we modified an author name in a particular bib record, but when we looked at the related z00R record some time later, a similar change had not been made.

    The SysLib manual seems to imply that adds and changes are both done: "Note that if the CREATE-Z00R variable of the tab100 table in the library's tab directory is set to Y, this function also updates/creates Z00R records."

    Are there any other configuration settings that need to be made so that the z13 and z00R are dynamically updated with changes? In general, does p_manage_07 need to be run with some regularity so that z13 and z00R tables in our various ADMs remain in sync with ABC01.z00?

    **Answer for Version 20-up:**
    v20 rep_ver 15272:
    Description: Ongoing update of Z13 records in ADM/HOL/CRS libraries.
    Up to now the Z13 record in ADM, HOL and CRS libraries does not get updated if the BIB record is edited. To correct the ADM/HOL/CRS Z13 records was possible only by running p_manage_07 in ADM/HOL/CRS libraries and rebuilding all of them.
    Now an individual Z13 record could be rebuilt automatically whenever the BIB record is updated.
    For this reason a new messaging type, represented by the character "e", has been implemented for UPDATE-DOC action. The Z105 library daemon, ue_11, has been enhanced to support delivering, receiving and processing the new messaging: Update Z13 and Z13U in relevant libraries. Once this message is received, the system should update the relevant Z13/Z13U records in the target libraries.

    Example of ./usm01/tab/tab_z105:
    ! 1 2 3 4 5 6 7 8 9 10 11 12

    Alternatively the new message type can be set up for INDEX-DOC action. The INDEX-DOC action is used by the ue_01 daemon. The advantage of this solution is that also dependant BIB records are included. This is only needed if the ADM/HOL/CRS-Z13 of the dependant BIB records use information of the originally updated BIB record.

    Example of ./usm01/tab/tab_z105:
    ! 1 2 3 4 5 6 7 8 9 10 11 12
    and then restart ue_11 (Messaging daemon) in the $z105_library .

    Additionally it is possible to use this mechanism inside the CRS library. This can be used for CRS records linked to other records in the course library.
    Example of ./usm30/tab/tab_z105:
    ! 1 2 3 4 5 6 7 8 9 10 11 12

    **Answer for Version 19 and lower:**
    If the ADM record or item record is updated in addition to the bib record, the ADM z13 or z00r will be updated. But if only the bib record is updated, then the ADM record will not be updated.

    One way to handle this, as you suggest, is to periodically run p_manage_07 in each ADM.

    Another would be to do the following weekly:

    1. Run p_ret_01 in the bib library looking for records with the relevant OWN code and an Update date in the past week.

    2. Use the output from step 1 as input to p_manage_70, specifying BIB-TO-ADM as the desired Convert Type. (This will generate a file of ADM numbers corresponding to the file of bib numbers output by p_ret_01.)

    3. Use the output from step 2 as input to p_manage_40 in the ADM library. (This will generate a z07 indexing request for each input record. The processing of this z07 by the ADM ue_01 will update both the ADM z13 and the ADM z00r.)

    4. Repeat steps 1-3 for each of the other ADM's.

    This process will consume less time and resources than running p_manage_07 in each ADM library and will not require any downtime.

    • Article last edited: 10/8/2013