Bug 22507 - Modification of the Holds Slip
Summary: Modification of the Holds Slip
Status: CLOSED FIXED
Alias: None
Product: Koha
Classification: Unclassified
Component: Hold requests (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-13 17:55 UTC by Jessie Zairo
Modified: 2020-11-30 21:45 UTC (History)
5 users (show)

See Also:
GIT URL:
Initiative type: ---
Sponsorship status: ---
Comma delimited list of Sponsors:
Crowdfunding goal: 0
Crowdfunding committed: 0
Crowdfunding contact:
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jessie Zairo 2019-03-13 17:55:42 UTC
Some libraries have expressed wanting to change the format of how the hold slip prints for multi branch systems. Currently, when you check an item in, and a hold is triggered, when you print the hold slip you get a message at the top of the slip indicating "Transfer to/Hold in <<branches.branchname>>". If the item is not at the final location of the patron pickup, it is transferred to the branch pick up location. Once the item arrives, the staff member again checks the item in, a hold is triggered, when you print the hold slip you get the same message "Transfer to/Hold in <<branches.branchname>>". 

Multi branch libraries would like to have an option to either split this slip so staff can easily identify that it is a transfer or it is a hold awaiting pickup. Having "Transfer to/Hold in <<branches.branchname>>" at the top of the slip (even though it is at the final destination for hold pickup, is causing confusion for staff.
Comment 1 AspenCat Team 2019-03-14 21:37:11 UTC
We would very much like to have the option to have the hold slip split into a sending slip and a receiving slip.  There are two reasons for this.  The first is that it is just more clear what the slip is being used for.  The second reason has to do with privacy.  When a library is placing an item on their hold shelf awaiting to be picked up they need to know information about the patron that could include a phone number or an email if that is how they contact them.  When the item is in transit, it is a huge privacy concern to be including private information on a hold slip that can be seen by both a library that the requesting patron is not a member of and non library staff involved in the transporting of these materials.
Comment 2 Josef Moravec 2019-03-18 11:10:29 UTC
I do think you can do much with setting HOLD_SLIP notices.

Give a try to this: https://wiki.koha-community.org/wiki/Notices_and_Slips_Library#Hold_slip_using_only_Template_Toolkit
Comment 3 Lisette Scheer 2019-06-04 16:37:05 UTC
We use some JQ in our notice to make this happen as well, though we are working on switching it to TT. 
I could see how separating it out could be useful, even though it is technically possible now. 

Lisette
Comment 4 Jessie Zairo 2019-07-29 15:37:28 UTC
Thank you Joseph. Lucas wrote another example that is working for us

[% USE Branches %]
[% loggedinbranchname = Branches.GetName( Branches.GetLoggedInBranchcode() ) %]
[% IF loggedinbranchname == branch.branchname%]
This is the branch 
[% ELSE %]
Transfer this to branch
[% END %]
Comment 5 Jessie Zairo 2020-03-11 15:59:20 UTC
This can be accomplished with template toolkit. Example below:

[% USE Branches %]
[% loggedinbranchname = Branches.GetName( Branches.GetLoggedInBranchcode() ) %]
[% IF loggedinbranchname == branch.branchname%]
This is the branch 
[% ELSE %]
Transfer this to branch
[% END %]

Marking resolved.