How to use Branch Transfer Limits in Koha

The Branch Transfer Limits Table in Koha allows you to limit the ability to transfer items between libraries based on the library sending, the library receiving, and the collection code or itemtype involved. You can also use branch transfer limits to deny holds for specific itemtypes or collection codes for specific branches.

System Preference

In your Administration Module within your Global System Preferences you have a preference called UseBranchTransferLimits & BranchTransferLimitsType. This allows you to enforce or not enforce the rules of the Branch Transfer limits. You can choose to limit by itemtype or collection code.

Keep in mind, if you do not have a collection code for every item you may want to limit by itemtype.

Setting up the Table

This table will build your itemtypes or collectioncodes (based on what you choose in the system preference above) along with your branches. By default, all branches and itemtypes or collection codes will be selected. Meaning, everything can be transferred, holds can be placed by each library / branch.

To enable the limits, you will want to go to Administration > Library Transfer Limits.

In the example above, you can see I have the Main Library selected. In this case, I am limiting the Audio itemtype from being transferred from West Branch also prohibiting a hold being place from a patron at another location.

In the screenshot above, I have disabled the ability to transfer holds on any Audio Itemtype to and from the West Branch. That also means patrons from other branches can not place holds on that item if their branch does not match that location.

• Related Articles

• Koha Offline Circulation Tool

  The Koha Offline Circulation Tool that was created by Kyle Hall for Windows. The offline circulation tool for Windows will generate a KOC (koha offline circulation) file that you can upload into Koha once your system comes back up. This tool works ...

• Changing Circulation Rules

  Let's take a look at what happens when you change your circulation and fine rules and discuss how Koha receives the data and processes a circulation transaction. At checkout When you scan a barcode into the checkout box, Koha zips through a lot of ...

• Circulation Rules Default Policies

  In addition to the circulation and fine matrix, the Default Policies control other aspects of circulation. Koha reads the Default Policies from the bottom of the page to the top. Default checkout, hold, and return policy You can set a default maximum ...

• Grouping Item Types in Circulation Rules

  Parent and Child item types allow you to create combined rules to incorporate several item type rules together. In the circulation and fine rule matrix, there is the ability to limit the number of checkouts by item type. However, a further option ...

• Circulation and Fine Rule Matrix

  Koha reads the circulation matrix from the top to the bottom. The bottom rule is usually (and recommended) to have what is called an ALL/ALL rule. This rule will capture any combination of patron category/item type that does not have its own specific ...