Notices and Slips Library

From Koha Wiki

Jump to: navigation, search

Contents

Notices and Slips Library

Template (Do not edit)


foo

  • Developer: Your Name Here
  • Letter Code: foo
  • Message Transport Type: foo
  • Purpose: foo
  • Status: Complete
  • Notes: foo
  • How to test: Give a description of how to generate the notice or slip
fooo

How it looks


Current Notices and Scripts

Notification on receiving

  • Developer: Barton Chittenden
  • Letter Code: ACQ_NOTIF_ON_RECEIV
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
Dear <<borrowers.firstname>> <<borrowers.surname>>,
 
 The order <<aqorders.ordernumber>> (<<biblio.title>>) has been received.
 
Your library.

Article Request - Email - Canceled

  • Developer: Barton Chittenden
  • Letter Code: AR_CANCELED
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
<<borrowers.firstname>> <<borrowers.surname>> (<<borrowers.cardnumber>>)
 
Your request for an article from <<biblio.title>> (<<items.barcode>>) has been canceled for the following reason:
 
<<article_requests.notes>>
 
Article requested:
Title: <<article_requests.title>>
Author: <<article_requests.author>>
Volume: <<article_requests.volume>>
Issue: <<article_requests.issue>>
Date: <<article_requests.date>>
Pages: <<article_requests.pages>>
Chapters: <<article_requests.chapters>>
Notes: <<article_requests.patron_notes>>

Article Request - Email - Completed

  • Developer: Barton Chittenden
  • Letter Code: AR_COMPLETED
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
<<borrowers.firstname>> <<borrowers.surname>> (<<borrowers.cardnumber>>)
 
We are have completed your request for an article from <<biblio.title>> (<<items.barcode>>).
 
Article requested:
Title: <<article_requests.title>>
Author: <<article_requests.author>>
Volume: <<article_requests.volume>>
Issue: <<article_requests.issue>>
Date: <<article_requests.date>>
Pages: <<article_requests.pages>>
Chapters: <<article_requests.chapters>>
Notes: <<article_requests.patron_notes>>
 
You may pick your article up at <<branches.branchname>>.
 
Thank you!

Article Request - Email - Open

  • Developer: Barton Chittenden
  • Letter Code: AR_PENDING
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
<<borrowers.firstname>> <<borrowers.surname>> (<<borrowers.cardnumber>>)
 
We have received your request for an article from <<biblio.title>> (<<items.barcode>>).
 
Article requested:
Title: <<article_requests.title>>
Author: <<article_requests.author>>
Volume: <<article_requests.volume>>
Issue: <<article_requests.issue>>
Date: <<article_requests.date>>
Pages: <<article_requests.pages>>
Chapters: <<article_requests.chapters>>
Notes: <<article_requests.patron_notes>>
 
 
Thank you!

Article Request - Email - Processing

  • Developer: Barton Chittenden
  • Letter Code: AR_PROCESSING
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
<<borrowers.firstname>> <<borrowers.surname>> (<<borrowers.cardnumber>>)
 
We are now processing your request for an article from <<biblio.title>> (<<items.barcode>>).
 
Article requested:
Title: <<article_requests.title>>
Author: <<article_requests.author>>
Volume: <<article_requests.volume>>
Issue: <<article_requests.issue>>
Date: <<article_requests.date>>
Pages: <<article_requests.pages>>
Chapters: <<article_requests.chapters>>
Notes: <<article_requests.patron_notes>>
 
Thank you!

Article Request - Print Slip

  • Developer: Barton Chittenden
  • Letter Code: AR_SLIP
  • Message Transport Type: print
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
Article Request:
 
<<borrowers.firstname>> <<borrowers.surname>> (<<borrowers.cardnumber>>)
 
Title: <<biblio.title>>
Barcode: <<items.barcode>>
 
Article requested:
Title: <<article_requests.title>>
Author: <<article_requests.author>>
Volume: <<article_requests.volume>>
Issue: <<article_requests.issue>>
Date: <<article_requests.date>>
Pages: <<article_requests.pages>>
Chapters: <<article_requests.chapters>>
Notes: <<article_requests.patron_notes>>

Item Check-in (Digest)

  • Developer: Barton Chittenden
  • Letter Code: CHECKIN
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
The following items have been checked in:
----
<<biblio.title>>
----
Thank you.

Item Check-out (Digest)

  • Developer: Barton Chittenden
  • Letter Code: CHECKOUT
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
The following items have been checked out:
----
<<biblio.title>>
----
Thank you for visiting <<branches.branchname>>.

Item Due Reminder

  • Developer: Barton Chittenden
  • Letter Code: DUE
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
Dear <<borrowers.firstname>> <<borrowers.surname>>,
 
The following item is now due:
 
<<biblio.title>>, <<biblio.author>> (<<items.barcode>>)

Item Due Reminder (Digest)

  • Developer: Barton Chittenden
  • Letter Code: DUEDGST
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
You have <<count>> items due

Hold Slip

  • Developer: Barton Chittenden
  • Letter Code: HOLD_SLIP
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
<h5>Date: <<today>></h5>
 
<h3> Transfer to/Hold in <<branches.branchname>></h3>
 
<h3><<borrowers.surname>>, <<borrowers.firstname>></h3>
 
<ul>
    <li><<borrowers.cardnumber>></li>
    <li><<borrowers.phone>></li>
    <li> <<borrowers.address>><br />
         <<borrowers.address2>><br />
         <<borrowers.city>>  <<borrowers.zipcode>>
    </li>
    <li><<borrowers.email>></li>
</ul>
<br />
<h3>ITEM ON HOLD</h3>
<h4><<biblio.title>></h4>
<h5><<biblio.author>></h5>
<ul>
   <li><<items.barcode>></li>
   <li><<items.itemcallnumber>></li>
   <li><<reserves.waitingdate>></li>
</ul>
<p>Notes:
<pre><<reserves.reservenotes>></pre>
</p>

Issue Quick Slip

  • Developer: Barton Chittenden
  • Letter Code: ISSUEQSLIP
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
<h3><<branches.branchname>></h3>
Checked out to <<borrowers.title>> <<borrowers.firstname>> <<borrowers.initials>> <<borrowers.surname>> <br />
(<<borrowers.cardnumber>>) <br />
 
<<today>><br />
 
<h4>Checked Out Today</h4>
<checkedout>
<p>
<<biblio.title>> <br />
Barcode: <<items.barcode>><br />
Date due: <<issues.date_due>><br />
</p>
</checkedout>


Issue Slip

  • Developer: Barton Chittenden
  • Letter Code: ISSUESLIP
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
<h3><<branches.branchname>></h3>
Checked out to <<borrowers.title>> <<borrowers.firstname>> <<borrowers.initials>> <<borrowers.surname>> <br />
(<<borrowers.cardnumber>>) <br />
 
<<today>><br />
 
<h4>Checked Out</h4>
<checkedout>
<p>
<<biblio.title>> <br />
Barcode: <<items.barcode>><br />
Date due: <<issues.date_due>><br />
</p>
</checkedout>
 
<h4>Overdues</h4>
<overdue>
<p>
<<biblio.title>> <br />
Barcode: <<items.barcode>><br />
Date due: <<issues.date_due>><br />
</p>
</overdue>
 
<hr>
 
<h4 style="text-align: center; font-style:italic;">News</h4>
<news>
<div class="newsitem">
<h5 style="margin-bottom: 1px; margin-top: 1px"><b><<opac_news.title>></b></h5>
<p style="margin-bottom: 1px; margin-top: 1px"><<opac_news.new>></p>
<p class="newsfooter" style="font-size: 8pt; font-style:italic; margin-bottom: 1px; margin-top: 1px">Posted on <<opac_news.timestamp>></p>
<hr />
</div>
</news>

Overdue Notice

  • Developer: Barton Chittenden
  • Letter Code: ODUE
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
Dear <<borrowers.firstname>> <<borrowers.surname>>,
 
According to our current records, you have items that are overdue.Your library does not charge late fines, but please return or renew them at the branch below as soon as possible.
 
<<branches.branchname>>
<<branches.branchaddress1>>
<<branches.branchaddress2>> <<branches.branchaddress3>>
Phone: <<branches.branchphone>>
Fax: <<branches.branchfax>>
Email: <<branches.branchemail>>
 
If you have registered a password with the library, and you have a renewal available, you may renew online. If an item becomes more than 30 days overdue, you will be unable to use your library card until the item is returned.
 
The following item(s) is/are currently overdue:
 
<item>"<<biblio.title>>" by <<biblio.author>>, <<items.itemcallnumber>>, Barcode: <<items.barcode>> Fine: <<items.fine>></item>
 
Thank-you for your prompt attention to this matter.
 
<<branches.branchname>> Staff

Overdues Slip

  • Developer: Barton Chittenden
  • Letter Code: OVERDUES_SLIP
  • Message Transport Type: print
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
The following item(s) is/are currently overdue:
 
<item>"<<biblio.title>>" by <<biblio.author>>, <<items.itemcallnumber>>, Barcode: <<items.barcode>> Fine: <<items.fine>></item>

Advance Notice of Item Due

  • Developer: Barton Chittenden
  • Letter Code: PREDUE
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
Dear <<borrowers.firstname>> <<borrowers.surname>>,
 
The following item will be due soon:
 
<<biblio.title>>, <<biblio.author>> (<<items.barcode>>)

Advance Notice of Item Due (Digest)

  • Developer: Barton Chittenden
  • Letter Code: PREDUEDGST
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
You have <<count>> items due soon

Item Renewals

  • Developer: Barton Chittenden
  • Letter Code: RENEWAL
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
The following items have been renewed:
----
<<biblio.title>>
----
Thank you for visiting <<branches.branchname>>.

Transfer Slip

  • Developer: Barton Chittenden
  • Letter Code: TRANSFERSLIP
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
<h5>Date: <<today>></h5>
 
<h3>Transfer to <<branches.branchname>></h3>
 
<h3>ITEM</h3>
<h4><<biblio.title>></h4>
<h5><<biblio.author>></h5>
<ul>
   <li><<items.barcode>></li>
   <li><<items.itemcallnumber>></li>
</ul>

Acquisition Claim

  • Developer: Barton Chittenden
  • Letter Code: ACQCLAIM
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
<<aqbooksellers.name>>
<<aqbooksellers.address1>>
<<aqbooksellers.address2>>
<<aqbooksellers.address3>>
<<aqbooksellers.address4>>
<<aqbooksellers.phone>>
 
<order>Ordernumber <<aqorders.ordernumber>> (<<biblio.title>>) (<<aqorders.quantity>> ordered) ($<<aqorders.listprice>> each) has not been received.</order>

Account Details Template - DEFAULT

  • Developer: Barton Chittenden
  • Letter Code: ACCTDETAILS
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
Hello <<borrowers.title>> <<borrowers.firstname>> <<borrowers.surname>>.
 
Your new Koha account details are:
 
User:  <<borrowers.userid>>
Password: <<borrowers.password>>
 
If you have any problems or questions regarding your account, please contact your Koha Administrator.
 
Thank you,
Koha Administrator
kohaadmin@yoursite.org

Discharge

  • Developer: Barton Chittenden
  • Letter Code: DISCHARGE
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
<h1>Discharge</h1>
 
The library <<borrowers.branchcode>> certifies that the following borrower :
 
    <<borrowers.firstname>> <<borrowers.surname>>
   Cardnumber : <<borrowers.cardnumber>>
 
returned all his documents.

Account expiration

  • Developer: Barton Chittenden
  • Letter Code: MEMBERSHIP_EXPIRY
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
Dear <<borrowers.title>> <<borrowers.firstname>> <<borrowers.surname>>,
 
Your library card will expire soon, on:
 
<<borrowers.dateexpiry>>
 
Thank you,
 
Librarian
 
<<branches.branchname>>

Opac Self-Registration Verification Email

  • Developer: Barton Chittenden
  • Letter Code: OPAC_REG_VERIFY
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
Hello!
 
Your library account has been created. Please verify your email address by clicking this link to complete the signup process:
 
http://<<OPACBaseURL>>/cgi-bin/koha/opac-registration-verify.pl?token=<<borrower_modifications.verification_token>>
 
If you did not initiate this request, you may safely ignore this one-time message. The request will expire shortly.

Online password reset

  • Developer: Barton Chittenden
  • Letter Code: PASSWORD_RESET
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
<html>
<p>This email has been sent in response to your password recovery request for the account <strong><<user>></strong>.
</p>
<p>
You can now create your new password using the following link:
<br/><a href="<<passwordreseturl>>"><<passwordreseturl>></a>
</p>
<p>This link will be valid for 2 days from this email's reception, then you must reapply if you do not change your password.</p>
<p>Thank you.</p>
</html>

Notification about an accepted share

  • Developer: Barton Chittenden
  • Letter Code: SHARE_ACCEPT
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
Dear patron,
 
We want to inform you that <<borrowers.firstname>> <<borrowers.surname>> accepted your invitation to share your list <<listname>> in our library catalog.
 
Thank you.
 
Your library.

Invitation for sharing a list

  • Developer: Barton Chittenden
  • Letter Code: SHARE_INVITE
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
Dear patron,
 
One of our patrons, <<borrowers.firstname>> <<borrowers.surname>>, invites you to share a list <<listname>> in our library catalog.
 
To access this shared list, please click on the following URL or copy-and-paste it into your browser address bar.
 
<<shareurl>>
 
In case you are not a patron in our library or do not want to accept this invitation, please ignore this mail. Note also that this invitation expires within two weeks.
 
Thank you.
 
Your library.

Acquisition order

  • Developer: Barton Chittenden
  • Letter Code: ACQORDER
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
<<aqbooksellers.name>>
<<aqbooksellers.address1>>
<<aqbooksellers.address2>>
<<aqbooksellers.address3>>
<<aqbooksellers.address4>>
<<aqbooksellers.phone>>
 
Please order for the library:
 
<order>Ordernumber <<aqorders.ordernumber>> (<<biblio.title>>) (quantity: <<aqorders.quantity>>) ($<<aqorders.listprice>> each).</order>
 
Thank you,
 
<<branches.branchname>>

Hold Available for Pickup

  • Developer: Barton Chittenden
  • Letter Code: HOLD
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
Dear <<borrowers.firstname>> <<borrowers.surname>>,
 
You have a hold available for pickup as of <<reserves.waitingdate>>:
 
Title: <<biblio.title>>
Author: <<biblio.author>>
Copy: <<items.copynumber>>
Location: <<branches.branchname>>
<<branches.branchaddress1>>
<<branches.branchaddress2>>
<<branches.branchaddress3>>
<<branches.branchcity>> <<branches.branchzip>>

Hold Available for Pickup

  • Developer: Barton Chittenden
  • Letter Code: HOLD
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
Dear <<borrowers.firstname>> <<borrowers.surname>>,
 
You have a hold available for pickup as of <<reserves.waitingdate>>:
 
Title: <<biblio.title>>
Author: <<biblio.author>>
Copy: <<items.copynumber>>
Location: <<branches.branchname>>
<<branches.branchaddress1>>
<<branches.branchaddress2>>
<<branches.branchaddress3>>
<<branches.branchcity>> <<branches.branchzip>>

Hold Available for Pickup (print)

  • Developer: Barton Chittenden
  • Letter Code: HOLD
  • Message Transport Type: print
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
<<branches.branchname>>
<<branches.branchaddress1>>
<<branches.branchaddress2>>
 
 
Change Service Requested
 
 
 
 
 
 
 
<<borrowers.firstname>> <<borrowers.surname>>
<<borrowers.address>>
<<borrowers.city>> <<borrowers.zipcode>>
 
 
 
 
 
 
 
 
 
 
<<borrowers.firstname>> <<borrowers.surname>> <<borrowers.cardnumber>>
 
You have a hold available for pickup as of <<reserves.waitingdate>>:
 
Title: <<biblio.title>>
Author: <<biblio.author>>
Copy: <<items.copynumber>>

Hold Placed on Item

  • Developer: Barton Chittenden
  • Letter Code: HOLDPLACED
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
A hold has been placed on the following item : <<biblio.title>> (<<biblio.biblionumber>>) by the user <<borrowers.firstname>> <<borrowers.surname>> (<<borrowers.cardnumber>>).

Routing List

  • Developer: Barton Chittenden
  • Letter Code: RLIST
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
<<borrowers.firstname>> <<borrowers.surname>>,
 
The following issue is now available:
 
<<biblio.title>>, <<biblio.author>> (<<items.barcode>>)
 
Please pick it up at your convenience.

Suggestion accepted

  • Developer: Barton Chittenden
  • Letter Code: ACCEPTED
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
Dear <<borrowers.firstname>> <<borrowers.surname>>,
 
You have suggested that the library acquire <<suggestions.title>> by <<suggestions.author>>.
 
The library has reviewed your suggestion today. The item will be ordered as soon as possible. You will be notified by mail when the order is completed, and again when the item arrives at the library.
 
If you have any questions, please email us at <<branches.branchemail>>.
 
Thank you,
 
<<branches.branchname>>

Suggestion ordered

  • Developer: Barton Chittenden
  • Letter Code: ORDERED
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
Dear <<borrowers.firstname>> <<borrowers.surname>>,
 
You have suggested that the library acquire <<suggestions.title>> by <<suggestions.author>>.
 
We are pleased to inform you that the item you requested has now been ordered. It should arrive soon, at which time it will be processed for addition into the collection.
 
You will be notified again when the book is available.
 
If you have any questions, please email us at <<branches.branchemail>>
 
Thank you,
 
<<branches.branchname>>

Suggestion rejected

  • Developer: Barton Chittenden
  • Letter Code: REJECTED
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
Dear <<borrowers.firstname>> <<borrowers.surname>>,
 
You have suggested that the library acquire <<suggestions.title>> by <<suggestions.author>>.
 
The library has reviewed your request today, and has decided not to accept the suggestion at this time.
 
The reason given is: <<suggestions.reason>>
 
If you have any questions, please email us at <<branches.branchemail>>.
 
Thank you,
 
<<branches.branchname>>

Notify budget owner

  • Developer: Barton Chittenden
  • Letter Code: TO_PROCESS
  • Message Transport Type: email
  • Purpose: foo
  • Status: In process, needs rendered example
  • Notes: foo
  • How to test: foo
Dear <<borrowers.firstname>> <<borrowers.surname>>,
 
A new suggestion is ready to be processed: <<suggestions.title>> by <<suggestions.autho    r>>.
 
Thank you,
 
<<branches.branchname>>

Other Examples

Hold slip with barcode

  • Developer: Candice Hope, Payson City Library
  • Purpose: Include item barcode in Hold Slip
  • Letter Code: HOLDSLIP (AKA RESERVESLIP)
  • Message Transport Type: email
  • Status: Complete
  • Notes: See Using svc/barcode for notes on individual barcode types.
  • How to test: Put a title on hold, then check the item in. Click Accept and print slip.
<h5>Date: <<today>></h5>
 
<h3>Hold at <<branches.branchname>></h3>
 
<h3>ITEM ON HOLD</h3>
<h4><<biblio.title>></h4>
<h5><<biblio.author>></h5>
<img src="/cgi-bin/koha/svc/barcode?barcode=*<<items.barcode>>*&type=Code39"></img>
<ul>
   <li><<items.barcode>></li>
   <li><<items.itemcallnumber>></li>
   <li><<items.copynumber>></li>
</ul>
<p>Notes:
<pre><<reserves.reservenotes>></pre>
</p>
<br />
<br />
<br />
<h3><<borrowers.surname>>, <<borrowers.firstname>></h3>
 
<ul>
    <li><<borrowers.cardnumber>></li>
    <li><<borrowers.phone>></li>
</ul>
<br />
<br />
<br />

How it looks

Notices and slips using template toolkit

Documentation on using Template Toolkit in notices could be found on page Notices_with_Template_Toolkit


Hold slip with barcode

  • Developer: Kyle Hall
  • Purpose: Hold slip using template Toolkit.
  • Letter Code: Customising_Notices_and_Slips#HOLD_SLIP (AKA HOLDSLIP or RESERVESLIP)
  • Message Transport Type: email
  • Status: Complete
  • Notes: Uses [% USE Branches %]. See Koha/Template/Plugin/Branches.pm, as well as other modules in Koha/Template/Plugin/.
  • How to test: Put a title on hold, then check the item in. Click Accept and print slip.
[% USE Branches %]
<h5>Date: <<today>></h5>
 
<h5>Transfer to/Hold in <<branches.branchname>></h5>
 
<h5><<borrowers.surname>>, <<borrowers.firstname>></h5>
 
<ul>
    <li><<borrowers.cardnumber>></li>
    <li><strong><<borrowers.phone>></strong></li>
    <li> <<borrowers.address>><br />
         <<borrowers.address2>><br />
         <<borrowers.city >>  <<borrowers.zipcode>>
    </li>
    <li><<borrowers.email>></li>
</ul>
<br />
<h3>ITEM ON HOLD</h3>
<h5><<biblio.title>></h5>
<h5><<biblio.unititle>></h5>
<h5><<biblio.author>></h5>
<ul>
   <li><<items.barcode>></li>
<img src="/cgi-bin/koha/svc/barcode?barcode=*<<items.barcode>>*"></img>
</ul>
   <li><<items.itemcallnumber>></li>
   <li><<reserves.waitingdate>></li>
</ul>
<h5>Transferred From: [% Branches.GetName('<<items.holdingbranch>>') %]</h5>
<h5>Home Library: [% Branches.GetName('<<items.homebranch>>') %] </h5>
<p>Notes:
<pre><<reserves.reservenotes>></pre>
</p>


Hold slip using only Template Toolkit

  • Developer: Josef Moravec
  • Letter Code: HOLD_SLIP
  • Message Transport Type: email
  • Purpose: Hold slip using template Toolkit
  • Status: Complete
  • Notes: Tested on 17.11 with TSP 143 printer
  • How to test: Put a title on hold, then check the item in. Click Accept and print slip.
<p><small>Printed on: [% today | $KohaDates with_hours => 1 %]</small></p>
 
<h2 style="border-bottom: 1px solid black; margin-bottom: 1em;">[% branch.branchname %]</h2>
<div style="font-size: 1.2em; font-weight: bold;">[% IF ( biblio.author ) %]<i>[% biblio.author %]</i>:<br />[% END %][% biblio.title %]</div>
 
<ul>
   <li>Barcode: [% item.barcode %]</li>
   <li>Waiting until: <strong>[% hold.expirationdate | $KohaDates%]</strong></li>
</ul>
[% IF ( hold.reservenotes ) %]
<p style="margin-bottom: 1em;">Note:<b>[% hold.reservenotes %]</b></p>
[% END %]
 
<p style="font-size: 1em; font-weight: bold; margin-bottom: 0;">[% borrower.cardnumber %]</p>
<p style="font-size: 1.2em; font-weight: bold; margin-top: 0;">[% borrower.surname %][% IF ( borrower.firstname ) %], [% borrower.firstname %][% END %]</p>

Checkouts slip using only Template Toolkit

  • Developer: Josef Moravec
  • Letter Code: ISSUSLIP
  • Message Transport Type: email
  • Purpose: Checkouts slip using template Toolkit
  • Status: Complete
  • Notes: Tested on 17.11 with TSP 143 printer
  • How to test: Go to circulation and print checkouts slip.
[% USE ItemTypes %]
[% BLOCK detail %]
<p style="font-size: 1.1em; border-bottom: 1px dotted black;">
[% IF checkout.item.biblio.author %]<i>[% checkout.item.biblio.author | $Remove_MARC_punctuation) %]</i>:[% END %]
<strong>[% checkout.item.biblio.title | $Remove_MARC_punctuation %]</strong>
[%- IF checkout.item.enumchron %], [% checkout.item.enumchron %][% END %]
([% ItemTypes.GetDescription(checkout.item.effective_itemtype) %])
<br />
Checked out on: [% checkout.issuedate | $KohaDates %]<br />
Due date: <b>[% checkout.date_due | $KohaDates as_due_date=1 %]</b><br />
[% branch.branchname %]
[% IF checkout.item.biblio.holds.count %]<br /><i><strong>Reserved</strong>, this checkout cannot be renewed</i>[% END %]
</p>
[% END # Block %]
 
<small>Printed on: [% today | $KohaDates with_hours=1 %]</small>
<img src="https://path.to.logo" style="width: 6cm" />
[% branch.branchemail %]<br />
[% branch.branchphone %]<br />
<p style="font-size: 1.2em; border-bottom: 1px solid black;">
Patron: <strong>[% IF ( borrower.firstname ) %][% borrower.firstname %] [% END %][% borrower.surname %]</strong> ([% borrower.cardnumber %]) <br />
Checkouts count: <strong>[% checkouts.count %]</strong><br />
</p>
[% FOREACH checkout IN checkouts %]
[% PROCESS detail checkout = checkout %]
[% END %]
 
[% IF overdues.count %]
[% FOREACH overdue IN overdues %]
[% PROCESS detail checkout = overdue %]
[% END %]
[% END # if overdues %]

Manipulating Dates in Notices using Template Toolkit

  • Developer: Kyle Hall
  • Purpose: To show how dates can be manipulated *within* notices using TT
  • Letter Code: All notices
  • Message Transport Type: All types
  • Status: Complete

For options, see https://metacpan.org/pod/distribution/Date-Manip/lib/Date/Manip/Examples.pod#PARSING-AN-AMOUNT-OF-TIME

This example takes the pickup date for a hold, subtracts one day from it, then converts it to the format MM/DD/YYYY

[%- USE date -%]
[%- manip = date.manip -%]
[%- date_prev = manip.DateCalc( hold.expirationdate, '1 day ago' ) -%]
[%- formatted_date_prev = manip.UnixDate(date_prev,"%m/%d/%Y") -%] 
 
Pick up hold on or before: [% formatted_date_prev %]