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

    Z07 records: order of processing; controlling indexing priority

    • Article Type: General
    • Product: Aleph
    • Product Version: 20, 21, 22, 23

    Description:
    v18 rep_change 1162 describes the ability to set the priority of the z07's for each batch job. Does it apply to both new and updated records?

    Resolution:
    The aleph_start "setenv z07_..." overrides apply to both new and updated records.

    Typically, you will want to give preference to new records from the GUI -- and perhaps updated as well.

    The current default (without any setenv z07_xxxxx's in aleph_start) is for:
    * new records, regardless of source, to be given a z07_sequence of '1990';
    * updated records from the GUI and oclc_server to be given '1998';
    * updated records from other sources (p_manage_21, p_manage_40, ue_08) to all be given the current year (which means they will all be processed at the same priority -- the lowest).

    If you find these priorities satisfactory, you do *not* need to add any setenv z07_'s.

     

    Here are 2 possible scenarios for specifying setenv_z07's in aleph_start:

    Scenario 1. You want new records to always take precedence, regardless of source, and to control the relative priority of jobs which only update.

    Solution:

    Include setenv z07_'s only for jobs which update records (which don't create any new records) and give these jobs numbers between '2000' and '2006' to make them *not* be processed in preference to GUI/oclc_server updates:
    Example:
    setenv z07_p_manage_21 2004
    setenv z07_p_manage_40 2005
    setenv z07_ue_08 2006
    Note: You *could* also include jobs which load *only* new records, if you wanted. Such jobs should have numbers between '1991' and '1997'.

    Scenario 2. You want the records from certain jobs, regardless of whether they are new or updates to be processed in preference to GUI/oclc_server updates and at a lower priority than *new* GUI/oclc_server records:

    Solution: Give them numbers between '1998' and '2002'.
    Example:
    setenv z07_p_manage_18 1998 *
    setenv z07_p_file_99 1999
    Plus, the same as #1:
    setenv z07_p_manage_21 2004
    setenv z07_p_manage_40 2005
    setenv z07_ue_08 2006

    * Another way to control the indexing priority of manage-18-loaded records is the "Override Indexing Priority" option in the manage-18 submission (seen in the manage-18 job log as "p_z07_priority_year"). The manage-18 p_z07_priority_year takes precedence over any aleph_start setenv.

    A third (unlikely) scenario: You want new/updated records for this job/utility to take precedence over both new and updated GUI/oclc_server
    records. Solution: specify a value less than 1990.

     

    NOTE:  In order to make the "setenv z07_xxxx" take effect for a GUI-submitted job, the batch queue needs to be restarted (util c/3, then util c/2).

    See also Articles
    * 000013380 ("Z07's generated by ue_08 and by item and HOL record updates") and
    * 000025711 ("GUI record changes are not taking priority in index queue")

     

     

    Additional Information

    faq


    • Article last edited: 2/9/2015
    • Was this article helpful?