Creating or Editing Groups to Define Circulation Privileges and Parameters

Your library may have large numbers of locations, ITYPEs, and BTYPEs, often with similar setup and regulatory requirements. On the other hand, your library may have only a few locations, ITYPEs, or BTYPEs, each with unique requirements. Horizon uses groups of locations, ITYPEs, and BTYPEs to simplify how you set up circulation rules.

When you initially set up locations, ITYPEs, or BTYPEs, Horizon automatically creates a corresponding group that contains only the code for the location, ITYPE, or BTYPE that you set up. (Horizon uses the same name and description for the group that you defined for the individual location, ITYPE, or BTYPE.) You can also create new groups of locations, ITYPEs, or BTYPEs that have similar requirements by adding multiple codes to a single group. You use these groups to set up circulation privileges and parameters, including hold priorities. When you use multiple-code groups, you can set up fewer privilege defaults. Multiple-code groups also let you set up fewer exceptions to those defaults.

For example, you may have ITYPEs that you do not want to let borrowers request. You can create an ITYPE group that contains any non-requestable ITYPEs. This lets you avoid creating exceptions for each location and each ITYPE.

You can edit your groups at any time. After you move a location, ITYPE, or BTYPE into a group, you should exit Horizon and log back in to assure that the privileges and parameters that apply to that group take effect for the new entry. Similarly, after you remove an entry from a group, you should exit Horizon and log back in to assure that the privileges and parameters no longer affect that entry. (For example, if you create a new ITYPE that has the same rules as an existing ITYPE group, the new ITYPE adopts the rules of the existing group as soon as you add it to that group and restart Horizon.)

If you want to apply one set of privileges and parameters to multiple ITYPEs, BTYPEs, or locations, you may need to define new groups, and put into the new groups the set of locations, BTYPEs, or ITYPEs that you want to group together.

For each privilege, you specify a default value that applies to all standard situations at each location group you designate. You also set up any exceptions based on your library’s policies. For example, you may allow a faculty member to request any item from any location group; however, you may want to restrict a student’s ability to request items to only certain ITYPE groups from only one location. (For more information and examples related to request privileges [circulation parameter 29], see Working with Parameter 29 (Request Privileges).)

 


© 1998-2017 Sirsi Corporation