- Article Type: General
- Product: Voyager
- Product Version: 7.2.5
? 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 behavior is a result of Issue VYG-4547.
Issue VYG-4547 is currently in Development.
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.
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_POLICY_GROUP=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
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.
- Article last edited: 2/9/2014