Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Voyager

     

    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Voyager
    3. Knowledge Articles
    4. Selection of Courtesy Discharge Route To location in Voyager Circulation not specific

    Selection of Courtesy Discharge Route To location in Voyager Circulation not specific

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    1. Symptoms
    2. Cause:
    3. Defect Status
    4. Additional Information
    5. Possible Workaround
    • Relevant for Installation Type: Multi-Tenant Direct, Dedicated-Direct, Local, TotalCare
    • Product: Voyager

    Symptoms

    When doing courtesy discharge at foreign circ desk, Voyager should choose a Route To location in the home Circ policy that is consistent and conforms to specific logic; instead, it chooses the first circulation happening location in the home policy returned by Oracle in the SQL - it does not appear to use an "order by" clause.

    When a new happening location is added to a circ policy, the Route To location suddenly changes.  This can also happen when a site is moved to a new server.
     

    The circulation happening location is also checked for the "Courtesy Discharge" checkbox status to see if the discharge is allowed.  See the "No Courtesy Discharge" section of the System Administration User's Guide for details.

    Cause:

    This behavior is a result of Issue VYG-4547.


    Defect Status

    Issue VYG-4547 is currently in Development.

    Additional Information

    Workflow implications

    • Data migration, adding new circ happening locations and other events that may change the order of data in the circ_policy_locs table cause confusion when a different route to location suddenly appears in Circulation; items cannot be routed efficiently.
    • Unchecking "Courtesy Discharge" box for multiple happening locations in a policy group can be confusing or problematic.


    Replication steps
    1. In SysAdmin, set up a policy (Policy 1) that has more than one circ happening location.
    2. In Circulation, log in to a circ happening location for a different policy (Policy 2)
    3. Discharge an item that belongs to Policy 1 at the circ desk in Policy 2.
    4. Note the "route to" location.
    5. If you query the circ_policy_locs table using the circ_policy_group for Policy 1:
    SELECT * from CIRC_POLICY_LOCS where CIRC_LOCATION='Y' and CIRC_GROUP_ID=1;
    you will note that the first row returned by this query is the location used as the route to location in Circulation.Replication Steps
     

    Possible Workaround

    If you remove the location used as the route to location from the circ policy, then discharge an item at a foreign circ desk and move the location back in to the policy, it will no longer be the route to location; the location that had been in the second row when querying as in the replication steps will now be the first row returned and the new route to location.

    Category: Circulation


    • Article last edited: 2-Oct-2020
    View article in the Exlibris Knowledge Center
    1. Back to top
      • Selecting print preview just closes the report window
      • Self Check - patrons not blocked from charging items via SelfCheck
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Voyager
    2. Tags
      1. 7.2.5
      2. Circulation
      3. contype:kba
      4. Prod:Voyager
      5. Type:General
    1. © Copyright 2025 Ex Libris Knowledge Center
    2. Powered by CXone Expert ®
    • Term of Use
    • Privacy Policy
    • Contact Us
    2025 Ex Libris. All rights reserved