If your library isn`t just working, you already have your list of loans and fine rules. However, you might. Each time you check out or check in an item, a new transaction is saved in the plugin`s local database and you can see at the bottom of the plugin how many transactions were made during offline distribution. For example, „10 row(s) added“ means that you have made 10 transactions. Traffic guidelines and fines are set by the library that lent the item to the user. You can use the output rule matrix to define rules that depend on user/item type combinations. To define your rules, select a library from the drop-down list (or „All libraries“ if you want to apply these rules to all branches): The value „This tag“ is the only part of the system preference that is replaced in traffic rules. The basic criterion „Try to shorten the loan period if we have more than 1 withholding on the number of durable items“ is always universally defined in the system preference. In my library example, I set my system preference to „Use calendar to skip days when the library is closed.“ When I look at my circ matrix, my previous rules for All/All, All/Visual Media, and All/Maps, I set the Day Mode column to Default, which means that these extractions follow the system settings. Once done, you can go to the self-registration page: YOUR_KOHA_OPAC_URL/cgi-bin/koha/sci/sci-main.pl Here are some proper traffic rules. Note the values in the „Reduced loan period for high hold periods (day)“ column.
When paying, all the values in this column are used instead of the 7 days I set in my system settings. This follows Koha`s general logic of „always using the most specific traffic rule“. Traffic messages are short messages that librarians can leave with clients or colleagues and that appear at the time of distribution. Payment option in the quick search bar on the loan page Arrival: borrowing > Pending offline traffic actions This setting defines certain keywords that cause Koha to restrict payment based on age. These restrictions can be overridden by the AgeRestrictionOverride parameter. In this field, enter a series of keywords separated by a bar (|) without spaces. For example, PG| A| E| THIS | Age| PG search followed by an age number, R followed by an age number, age followed by an age number, etc. These values can be displayed in any MARC field, but the Library of Congress recommends $521a (Target Audience Note). Whichever field you choose, you must map the age restriction of words in the biblioitems table to that field in the Koha to MARC map. When cataloguing, you can enter values such as PG 13 or E 10 within $521 and Koha will then inform lending librarians that the material may not be recommended to the customer due to their age. This preference is a binary parameter that determines whether or not library staff can override lending and fine rules regarding the location of cargo spaces. Setting this value to „Do not allow“ prevents anyone from overwriting it, and setting it to „Allow“ will allow it.
This setting is important because it determines how rigorous library rules are to place stops. If this setting is set to „Allow“, exceptions may be made for users who generally have a good reputation in the library, but it is possible that staff will abuse this feature. If it is set to „Do not allow“, no abuse of the system is possible, but this makes the system completely inflexible in terms of suspensions. When pending objects are checked in or checked out, the system reminds the lending librarian that the object is pending and provides options to manage the queue. Koha allows you to continue offline traffic actions using one of three utilities. Sometimes lending librarians need to quickly add a record to the system for a document they want to borrow. This is called a „quick add-on.“ To give librarians access to the Quick Add Cataloguing tool, just make sure they have fast_cataloging permissions. There are two ways to add titles via quick add. If you know you want to check out an item that is not in your catalog, you can go to the loan module and click on „Quick Cataloging“. These rules define how your items will be distributed, how/when fines will be charged, and how to process blocks. Request: ___ Hide customers` phone number, email address, address, and city on the loan page When these rules are triggered at checkout, you will receive a pop-up window alerting you to the situation. You have the option not to shorten the loan period, if you wish.
Using the values I`ve set here, Koha will quickly calculate at checkout to count the number of durable items on that title (excluding damaged, lost, non-borrowed, or withdrawn items). If the number of breakpoints for this title exceeds the number of durable items by more than 1, Koha will attempt to use the loan period (7 days) indicated here instead of the loan period set out in the rules of my circle. If the initial loan period would have been longer than 7 days, the shortest value will be replaced. Koha`s Price Reserves module allows you to temporarily move items to „Book“ and assign different traffic rules to those items while they are being used for a particular price. When the AgeRestriction Marker parameter is set, Koha attempts to warn librarians before they remove an item that may have an age restriction listed in the MARC record. This preference asks if you want staff to continue to be able to check these items for customers below the age limit. There is an offline traffic tool that you can add to your Firefox browser as an addon. To do this, simply go to addons.mozilla.org/en/firefox/addon/koct/ page and click on the „Install Now“ button. You may need to confirm the installation, just click „Install Now“ and restart Firefox to complete the installation.
This setting allows you to decide whether checkouts that are considered on-premises checkouts count towards the total number of checkouts a customer can have. You can also set your traffic and fine rules to allow only a certain number of normal and on-site checkouts. Withdrawn items may be renewed (extracted for a different period) depending on your traffic rules and renewal preferences. When this setting is set to Allow, all employees will see the option to remove more items from a customer than is normally allowed under traffic and fine rules. If this setting is set to Do not allow, no employee can retrieve more than the traffic limit. These rules take effect only when the UseBranchTransferLimits parameter is set to Application. The offline interface uses HTML LocalStorage, which is limited to 2.5 MB or 5 MB per domain, depending on the browser and user settings. This means that mainframes cannot sync their data and it is recommended to use the Firefox or Windows app for offline distribution.
