[Bug 22507] New: Modification of the Holds Slip
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22507 Bug ID: 22507 Summary: Modification of the Holds Slip Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs@lists.koha-community.org Reporter: jzairo@bywatersolutions.com QA Contact: testopia@bugs.koha-community.org CC: gmcharlt@gmail.com Target Milestone: --- 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. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22507 robbinsk@middlesex.mass.edu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |robbinsk@middlesex.mass.edu -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22507 AspenCat Team <aspencatteam@clicweb.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aspencatteam@clicweb.org --- Comment #1 from AspenCat Team <aspencatteam@clicweb.org> --- 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. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22507 Josef Moravec <josef.moravec@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |josef.moravec@gmail.com --- Comment #2 from Josef Moravec <josef.moravec@gmail.com> --- 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_usi... -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22507 Lisette Scheer <lisetteslatah@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lisetteslatah@gmail.com --- Comment #3 from Lisette Scheer <lisetteslatah@gmail.com> --- 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 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22507 --- Comment #4 from Jessie Zairo <jzairo@bywatersolutions.com> --- 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 %] -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22507 Jessie Zairo <jzairo@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22507 --- Comment #5 from Jessie Zairo <jzairo@bywatersolutions.com> --- 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. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org