572c586793
This patch uses the version number of the Koha database to dynamically generate links from help to the appropriate version of the manual. Test plan (for 3.15 branch): - Open a help page - Verify the manual link is correct (point to 3.14 manual) - change the version in mysql: update systempreferences set value="3.1600000" where variable="version"; - Verify the manual link now points to the future 3.16 manual. Signed-off-by: Bernardo Gonzalez Kriegel <bgkriegel@gmail.com> Work as described. No koha-qa errors Tested on top of Bug 10671 On master (BD version 3.13.xxx) help links point to 3.12 manual Changing version to 3.14/15 points to 3.14 manual Changing version to 3.16 points to the future :) Signed-off-by: Kyle M Hall <kyle@bywatersolutions.com>
23 lines
No EOL
2.4 KiB
Text
23 lines
No EOL
2.4 KiB
Text
[% INCLUDE 'help-top.inc' %]
|
|
|
|
<h1>Holds queue</h1>
|
|
|
|
<p>This report will show you all of the holds at your library.</p>
|
|
|
|
<p>To generate this report, you must have the Build Holds Queue cron job running. This cron job is a script that should be run periodically if your library system allows borrowers to place on-shelf holds. This script decides which library should be responsible for fulfilling a given hold request.</p>
|
|
|
|
<p>It's behavior is controlled by the system preferences StaticHoldsQueueWeight and RandomizeHoldsQueueWeight.</p>
|
|
|
|
<p>If you do not want all of your libraries to participate in the on-shelf holds fulfillment process, you should list the the libraries that *do* participate in the process here by inputting all the participating library's branchcodes, separated by commas ( e.g. "MPL,CPL,SPL,BML" etc. ).</p>
|
|
|
|
<p>By default, the holds queue will be generated such that the system will first attempt to hold fulfillment using items already at the pickup library if possible. If there are no items available at the pickup library to fill a hold, build_holds_queue.pl will then use the list of libraries defined in StaticHoldsQueueWeight. If RandomizeHoldsQueueWeight is disabled ( which it is by default ), the script will assign fulfillment requests in the order the libraries are placed in the StaticHoldsQueueWeight system preference.</p>
|
|
|
|
<p>For example, if your system has three libraries, of varying sizes ( small, medium and large ) and you want the burden of holds fulfillment to be on larger libraries before smaller libraries, you would want StaticHoldsQueueWeight to look something like "LRG,MED,SML".</p>
|
|
|
|
<p>If you want the burden of holds fulfillment to be spread out equally throughout your library system, simply enable RandomizeHoldsQueueWeight. When this system preference is enabled, the order in which libraries will be requested to fulfill an on-shelf hold will be randomized each time the list is regenerated.</p>
|
|
|
|
<p>Leaving StaticHoldsQueueWeight empty is contraindicated at this time. Doing so will cause the build_holds_queue script to ignore RandomizeHoldsQueueWeight, causing the script to request hold fulfillment not randomly, but by alphabetical order.</p>
|
|
|
|
<p><strong>See the full documentation for the Holds Queue in the <a href="http://manual.koha-community.org/[% helpVersion %]/en/circreports.html#holdsqueue">manual</a> (online).</strong></p>
|
|
|
|
[% INCLUDE 'help-bottom.inc' %] |