Circulation Parameter 29 Examples

Suppose you are a three-city consortium with three branch libraries in each city, and that you allow requests between libraries in the same city, but not between cities. Suppose the cities are C1, C2, and C3, and the branches in each city are B1, B2, and B3. When you set up the individual locations (such as C1B1, C1B2, C1B3, C2B1, C2B2, and so on), Horizon automatically creates a group for each location containing only that location.

Suppose you also set up the location groups to contain all the individual locations:

This location group

Contains these libraries

C1 (City 1)

C1B1, C1B2, and C1B3

C2 (City 2)

C2B1, C2B2, and C2B3

C2 (City 2)

C3B1, C3B2, and C3B3

Example 1

To let the correct groups loan items to each other, you could set up the request privileges parameter (parameter 29) with a default value of 0 (zero) and exceptions like this (a value indicates the request priority, with 1 being the highest):

Exception

Circulation (Pickup) Location Group

Item Location Group

Value

1

C1

C1

1

2

C2

C2

1

3

C3

C3

1

Suppose a borrower places a request on an item at location C2B1 (City 2, Branch 1), and the borrower wants to pick it up at location C2B3 (City 2, Branch 3). Horizon examines each of the three exceptions, looking for Item Location Groups that contain the location C2B1. It finds only one—the location group C2. Next Horizon looks at the pickup location, and finds it in the Circulation Location Group C2 which is part of the same exception as the Item Location Group being considered. Since you have set the value as 1, Horizon places the request.

Now, suppose a borrower places a request for an item owned by C2B1 and wants to pick it up at location C1B1. Horizon finds Item Location C2B1 in Item Location Group C2 (exception 2), and then looks to see if the pickup location C1B1 is in the Circulation Location Group for exception 2 (C2). Since the pickup location is not in that group, there is no match and Horizon does not fill the request.

Example 2

Suppose that, in your consortium, the request for an item at its owning library has a higher priority than a request for an item at another library within the same group. You could set up the request privileges parameter (parameter 29) with a default value of 0 (zero) and exceptions like this:

Exception

Circulation (Pickup) Location Group

Item Location Group

Value

1

C1

C1

10

2

C2

C2

10

3

C3

C3

10

4

C1B1

C1B1

1

5

C1B2

C1B2

1

6

C1B3

C1B3

1

7

C2B1

C2B1

1

8

C2B2

C2B2

1

9

C2B3

C2B3

1

10

C3B1

C3B1

1

11

C3B2

C3B2

1

12

C3B3

C3B3

1

Suppose a borrower places a request on an item owned by C1B1 and wants to pick up the item at that same location. The table shows two exceptions that satisfy that criteria: numbers 1 and 4. C1B1 is a location in the Location Group C1 as well as in the Location Group C1B1, and so both exceptions are candidates.

Whenever someone places a request, Horizon must first identify which possible exceptions it can use. In this example, Horizon can use exceptions 1 and 4. Next Horizon looks at how many locations are defined within the location groups for each row, and uses the one that has the fewest locations. In this case, this means that, although Location C1B1 is in both Location Group C1 and Location Group C1B1, since location group C1 has three defined locations and C1B1 has only one, Horizon uses the C1B1 location group. Horizon uses this identification process for each applicable group (in this example, Item Location Group and Circulation Location Group), and as long as there is an exception where for each group the count is less than the others, Horizon chooses that exception. In this example, since exception 4 has the lowest count for both of the matches, Horizon returns a value of 1—the highest possible fill priority.

If a borrower places a request on an item owned by C1B1 and wants to pick up the item at C1B2, only row 1 matches. The value of 10 means that the request has a lower fill priority (value 1 is highest).

If a borrower places a request on an item owned by C1B1 and wants to pick up the item at C2B1, then no rows match, and the request is not allowed.

If there are two rows where for one group the count is higher than the other, and for another group the count is lower than the other, Horizon notifies you that an error has occurred. You need to check your setup.

Example 3

Suppose that from city C1, borrowers can request items from any other location, but for cities C2 and C3, borrowers from each city can request items only from their own library. However, requests across cities (from C1 to either C2 or C3) have the lowest priority. You could set up the request privileges parameter (parameter 29) with a default value of 0 (zero) and exceptions like this:

Exception

Circulation (Pickup) Location Group

Item Location Group

Value

1

C1

C1

10

2

C2

C2

10

3

C3

C3

10

4

C1B1

C1B1

1

5

C1B2

C1B2

1

6

C1B3

C1B3

1

7

C2B1

C2B1

1

8

C2B2

C2B2

1

9

C2B3

C2B3

1

10

C3B1

C3B1

1

11

C3B2

C3B2

1

12

C3B3

C3B3

1

13

C1

 

255

 

The setup is the same as in the previous example, except for the added row, “13.”

255 is the lowest priority possible.

Suppose a borrower requests an item owned by C2B1 and wants to pick it up at C1B1. As Horizon looks at each exception, only number thirteen matches on the Item Location Group (Location C1B1 is in Location Group C1). Since the Circulation Location Group is empty, any circulation location will match. Horizon makes the request, but with a low priority level.

Now suppose a borrower places a request on an item owned by C1B1 and wants to pick it up at that same location. Horizon first identifies exceptions 1, 4, and 13 as candidates. Since exceptions 1 and 4 each have two matches but exception 13 has only one, Horizon ignores exception 13. Horizon checks again to find the exception with the lowest count for the various matches, and identifies number 4 because each of its location groups has only one location (in exception 1, each location group has three locations).

 


© 1998-2017 Sirsi Corporation