C4::Reserves - Koha functions for dealing with reservation.
use C4::Reserves;
this modules provides somes functions to deal with reservations.
Reserves are stored in reserves table.
The following columns contains important values :
- priority >0 : then the reserve is at 1st stage, and not yet affected to any item.
=0 : then the reserve is being dealed
- found : NULL : means the patron requested the 1st available, and we haven't choosen the item
W(aiting) : the reserve has an itemnumber affected, and is on the way
F(inished) : the reserve has been completed, and is done
- itemnumber : empty : the reserve is still unaffected to an item
filled: the reserve is attached to an item
The complete workflow is :
==== 1st use case ====
patron request a document, 1st available : P >0, F=NULL, I=NULL
a library having it run "transfertodo", and clic on the list
if there is no transfer to do, the reserve waiting
patron can pick it up P =0, F=W, I=filled
if there is a transfer to do, write in branchtransfer P =0, F=NULL, I=filled
The pickup library recieve the book, it check in P =0, F=W, I=filled
The patron borrow the book P =0, F=F, I=filled
==== 2nd use case ====
patron requests a document, a given item,
If pickup is holding branch P =0, F=W, I=filled
If transfer needed, write in branchtransfer P =0, F=NULL, I=filled
The pickup library recieve the book, it checks it in P =0, F=W, I=filled
The patron borrow the book P =0, F=F, I=filled
AddReserve($branch,$borrowernumber,$biblionumber,$constraint,$bibitems,$priority,$notes,$title,$checkitem,$found)
($count, $title_reserves) = &GetReserves($biblionumber);
This function gets the list of reservations for one $biblionumber, returning a count of the reserves and an arrayref pointing to the reserves for $biblionumber.
( $reservedate, $borrowernumber, $branchcode ) = GetReservesFromItemnumber($itemnumber); TODO :: Description here
$borrowerreserv = GetReservesFromBorrowernumber($borrowernumber,$tatus);
TODO :: Descritpion
$error = &CanBookBeReserved($borrowernumber, $biblionumber)
$error = &CanItemBeReserved($borrowernumber, $itemnumber)
this function return 1 if an item can be issued by this borrower.
$number = &GetReserveCount($borrowernumber);
this function returns the number of reservation for a borrower given on input arg.
($messages,$nextreservinfo)=$GetOtherReserves(itemnumber);
Check queued list of this document and check if this document must be transfered
$fee = GetReserveFee($borrowernumber,$biblionumber,$constraint,$biblionumber);
Calculate the fee for a reserve
@transreserv = GetReservesToBranch( $frombranch );
Get reserve list for a given branch
@transreserv = GetReservesForBranch($frombranch);
($status, $reserve) = &CheckReserves($itemnumber); ($status, $reserve) = &CheckReserves(undef, $barcode);
Find a book in the reserves.
$itemnumber is the book's item number.
As I understand it, &CheckReserves looks for the given item in the reserves. If it is found, that's a match, and $status is set to Waiting.
Otherwise, it finds the most important item in the reserves with the same biblio number as this book (I'm not clear on this) and returns it with $status set to Reserved.
&CheckReserves returns a two-element list:
$status is either Waiting, Reserved (see above), or 0.
$reserve is the reserve item that matched. It is a reference-to-hash whose keys are mostly the fields of the reserves table in the Koha database.
&CancelReserve($biblionumber, $itemnumber, $borrowernumber);
Cancels a reserve.
Use either $biblionumber or $itemnumber to specify the item to cancel, but not both: if both are given, &CancelReserve does nothing.
$borrowernumber is the borrower number of the patron on whose behalf the book was reserved.
If $biblionumber was given, &CancelReserve also adjusts the priorities of the other people who are waiting on the book.
ModReserve($rank, $biblio, $borrower, $branch[, $itemnumber])
Change a hold request's priority or cancel it.
$rank specifies the effect of the change. If $rank is 'W' or 'n', nothing happens. This corresponds to leaving a request alone when changing its priority in the holds queue for a bib.
If $rank is 'del', the hold request is cancelled.
If $rank is an integer greater than zero, the priority of the request is set to that value. Since priority != 0 means that the item is not waiting on the hold shelf, setting the priority to a non-zero value also sets the request's found status and waiting date to NULL.
The optional $itemnumber parameter is used only when $rank is a non-zero integer; if supplied, the itemnumber of the hold request is set accordingly; if omitted, the itemnumber is cleared.
FIXME: Note that the forgoing can have the effect of causing item-level hold requests to turn into title-level requests. This will be fixed once reserves has separate columns for requested itemnumber and supplying itemnumber.
&ModReserveFill($reserve);
Fill a reserve. If I understand this correctly, this means that the reserved book has been found and given to the patron who reserved it.
$reserve specifies the reserve to fill. It is a reference-to-hash whose keys are fields from the reserves table in the Koha database.
&ModReserveStatus($itemnumber, $newstatus);
Update the reserve status for the active (priority=0) reserve.
$itemnumber is the itemnumber the reserve is on
$newstatus is the new status.
&ModReserveAffect($itemnumber,$borrowernumber,$diffBranchSend);
This function affect an item and a status for a given reserve The itemnumber parameter is used to find the biblionumber. with the biblionumber & the borrowernumber, we can affect the itemnumber to the correct reserve.
if $transferToDo is not set, then the status is set to "Waiting" as well. otherwise, a transfer is on the way, and the end of the transfer will take care of the waiting status
($messages,$nextreservinfo) = &ModReserveCancelAll($itemnumber,$borrowernumber);
function to cancel reserv,check other reserves, and transfer document if it's necessary
&ModReserveMinusPriority($itemnumber,$borrowernumber,$biblionumber)
Reduce the values of queuded list
&GetReserveInfo($borrowernumber,$biblionumber);
Get item and borrower details for a current hold. Current implementation this query should have a single result.
my $is_available = IsAvailableForItemLevelRequest($itemnumber);
Checks whether a given item record is available for an item-level hold request. An item is available if
* it is not lost AND * it is not damaged AND * it is not withdrawn AND * does not have a not for loan value > 0
Whether or not the item is currently on loan is also checked - if the AllowOnShelfHolds system preference is ON, an item can be requested even if it is currently on loan to somebody else. If the system preference is OFF, an item that is currently checked out cannot be the target of an item-level hold request.
Note that IsAvailableForItemLevelRequest() does not check if the staff operator is authorized to place a request on the item - in particular, this routine does not check IndependantBranches and canreservefromotherbranches.
&_FixPriority($biblio,$borrowernumber,$rank);
Only used internally (so don't export it) Changed how this functions works # Now just gets an array of reserves in the rank order and updates them with the array index (+1 as array starts from 0) and if $rank is supplied will splice item from the array and splice it back in again in new priority rank
@results = &_Findgroupreserve($biblioitemnumber, $biblionumber, $itemnumber);
Looks for an item-specific match first, then for a title-level match, returning the first match found. If neither, then we look for a 3rd kind of match based on reserve constraints.
TODO: add more explanation about reserve constraints
&_Findgroupreserve returns : @results is an array of references-to-hash whose keys are mostly fields from the reserves table of the Koha database, plus biblioitemnumber.
_koha_notify_reserve( $itemnumber, $borrowernumber, $biblionumber );
Sends a notification to the patron that their hold has been filled (through ModReserveAffect, _not_ ModReserveFill)
$new_priority = _ShiftPriorityByDateAndPriority( $biblionumber, $reservedate, $priority );
This increments the priority of all reserves after the one with either the lowest date after $reservedate or the lowest priority after $priority.
It effectively makes room for a new reserve to be inserted with a certain priority, which is returned.
This is most useful when the reservedate can be set by the user. It allows the new reserve to be placed before other reserves that have a later reservedate. Since priority also is set by the form in reserves/request.pl the sub accounts for that too.
Koha Developement team <info@koha.org>