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

    p_cir_07 includes requests not within specified date range; no sub-sort

    1. Last updated
    2. Save as PDF
    • Article Type: General
    • Product: Aleph
    • Product Version: 18.01

    Description:
    We run p_cir_07 daily to identify and set aside booking requests for the Audio Visual library. The date range is specified as the next day, e.g. start request date/end request date = 20100317 - 20100318, but the report includes other dates not in this range.

    For example the report mise-de-cote-AudioVideo_20100317 with the date range march 17 to march 18 includes dates for the 15 and 19 as start dates.

    How can we limit this report to only those dates indicated in the date range?

    And how can we sort the report by date first, and then sub-sort by requester?

    Resolution:
    The logic for the Start Request Date and End Request Date is a bit confusing. If the z37 has the same date for the start and end date, it's very simple, but when the end date is higher than the start date,... it gets confusing.

    Say that you specify a start date of 20100317 and an end date of 20100318 in the submission. Should a z37 with a z37_effective_start_time of 20100317 and a z37_effective_end_time of 20100319 be included?

    I believe that some sites *want* to see booking requests for all starting dates <= the specified date and end dates >= the specified end date, so I do not believe that changing this logic would be possible, but if you feel strongly that what you want is only z37's with the *exact* starting and end dates that you specify, I could try to make a case for this.

    You requested that the report be sorted by "SD" (Start Date) and I see that it is:

    SQL-ABC50>>grep z37-effective-start-time mise-de-cote-AudioVideo_20100317
    <z37-effective-start-time>201003122358</z37-effective-start-time>
    <z37-effective-start-time>201003162358</z37-effective-start-time>
    <z37-effective-start-time>201003162358</z37-effective-start-time>
    <z37-effective-start-time>201003162358</z37-effective-start-time>
    <z37-effective-start-time>201003162358</z37-effective-start-time>
    <z37-effective-start-time>201003162358</z37-effective-start-time>
    <z37-effective-start-time>201003172358</z37-effective-start-time>
    <z37-effective-start-time>201003172358</z37-effective-start-time>
    <z37-effective-start-time>201003172358</z37-effective-start-time>
    <z37-effective-start-time>201003172358</z37-effective-start-time>
    <z37-effective-start-time>201003182358</z37-effective-start-time>
    <z37-effective-start-time>201003182358</z37-effective-start-time>
    <z37-effective-start-time>201003182358</z37-effective-start-time>
    <z37-effective-start-time>201003182358</z37-effective-start-time>
    <z37-effective-start-time>201003182358</z37-effective-start-time>
    <z37-effective-start-time>201003182358</z37-effective-start-time>
    <z37-effective-start-time>201003182358</z37-effective-start-time>
    <z37-effective-start-time>201003182358</z37-effective-start-time>
    <z37-effective-start-time>201003182358</z37-effective-start-time>
    <z37-effective-start-time>201003182358</z37-effective-start-time>


    Staff can go to the section of the report which includes the date they are interested in -- and skip the other (earlier) dates.

    There is no provision for a subsort by requester or any other value.

    • Article last edited: 10/8/2013