From 5889f893cb88b710c1c39ff89b337686565f5d83 Mon Sep 17 00:00:00 2001 From: "Nicole C. Engard" Date: Tue, 13 May 2014 08:19:56 -0500 Subject: [PATCH] Bug 12244 - Update Notices Help Files Updates the 2 notices help files with new info. To test: * Visit Tools > Notices & Slips * Click help and confirm it's there and right * Visit Tools > Overdue notices/status triggers * Click help and confirm it's there and right Signed-off-by: Bernardo Gonzalez Kriegel Long help ok Signed-off-by: Jonathan Druart Signed-off-by: Galen Charlton --- .../prog/en/modules/help/tools/letter.tt | 246 ++++++++++++++---- .../en/modules/help/tools/overduerules.tt | 6 +- 2 files changed, 199 insertions(+), 53 deletions(-) diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/tools/letter.tt b/koha-tmpl/intranet-tmpl/prog/en/modules/help/tools/letter.tt index 18d90a19f2..94977ef1cf 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/tools/letter.tt +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/tools/letter.tt @@ -10,62 +10,82 @@

Adding Notices & Slips

-

To add a new notice or slip +

To add a new notice or slip

  • Click 'New Notice'
    • -
  • Choose which library this notice or slip is for
    • +
  • Choose which library this notice or slip is for
  • Choose the module this notice is related to
    • -
  • The Code is limited to 20 characters
    • -
  • Use the name field to expand on your Code
    • -
  • If you plan on writing the notice or slip in HTML check the 'HTML Message' box, otherwise the content will be generated as plain text
    • +
  • The Code is limited to 20 characters +
      +
    • Important: When working with the overdue notices you want each notice at each branch to have a unique code. Think about using the branch code in front of the notice code for each branch.
      • +
    +
    • +
  • Use the name field to expand on your Code +
      +
    • Tip: With overdue notices, be sure to put your branch name in the description as well so that it will be visible when setting up your triggers.
      • +
    +
    • +
  • Next you can customize the notice for every possible delivery method +
      +
    • Every notice should have an Email template set for it
      • +
    • Next, you can set up a Feed template
      • +
    • If you're using the TalkingTechItivaPhoneNotification service you can set up a Phone notification
      • +
    • If you plan on printing this notice you can set the Print template next
      • +
    • If you have enabled SMS notices with the SMSSendDriver preference you can set the text for your SMS notices next
      • +
    +
    • +
  • Each notice offers you the same options +
      +
    • If you plan on writing the notice or slip in HTML check the 'HTML Message' box, otherwise the content will be generated as plain text
    • Message Subject is what will appear in the subject line of the email
    • In the message body feel free to type whatever message you feel is best, use the fields on the left hand side to enter individualized data from the from database.
        -
      • Important: Overdue notices can use <<items.content>> tags by themselves, or use <item></item> to span all of the tags. Learn more about the Overdue Notice Markup
        • +
      • Important: Overdue notices can use <<items.content>> tags by themselves, or use <item></item> to span all of the tags.
          -
        • On overdue notices make sure to use <<items.content>> tags to print out the data related to all items that are overdue.
          • +
        • On overdue notices make sure to use <<items.content>> tags to print out the data related to all items that are overdue.
          -
        • The other option, only for overdue notices, is to use the <item></item> tags to span the line so that it will print out multiple lines One example for the <item></item> tag option is:<item>"<<biblio.title>>" by <<biblio.author>>, <<items.itemcallnumber>>, Barcode: <<items.barcode>> , Checkout date: <<issues.issuedate>>, Due date: <<issues.date_due>> Fine: <<items.fine>> Due date: <<issues.date_due>> </item>
          • +
        • The other option, only for overdue notices, is to use the <item></item> tags to span the line so that it will print out multiple lines. One example for the <item></item> tag option is:<item>"<<biblio.title>>" by +<<biblio.author>>, <<items.itemcallnumber>>, +Barcode: <<items.barcode>> , Checkout date: +<<issues.issuedate>>, Due date: +<<issues.date_due>> Fine: <<items.fine>> Due date: +<<issues.date_due>> </item>
        +
        • +
      • Important: Only the overdue notices take advantage of the <item></item> tags, all other notices referencing items need to use <<items.content>>
        • +
      • Tip: To add today's date you can use the <<today>> syntax
        • +
      +
    • -
  • Important: Only the overdue notices take advantage of the <item></item> tags, all other notices referencing items need to use <<items.content>>
-

Overdue Notice Markup

+
Overdue Notice Markup

When creating your overdue notices there are two tags in addition to the various database fields that you can use in your notices.

-

Important These new tags only work on the overdue notices, not other circulation related notices at this time.

+

Important: These new tags only work on the overdue notices, not other circulation related notices at this time.

-
    -
  • <item></item> which should enclose all fields from the biblio, biblioitems, and items tables.
    • -
  • <fine></fine> which should be enclosed by the item tag and should enclose a currency identifier per ISO 4217. If this tag is present with a proper identifier, the fine for that item will be displayed in the proper currency format. -
      -
    • Note: ISO 4217 changes from time to time therefore all currencies may not be supported. If you find one that is not supported, please file a bug with the Locale::Currency::Format author Tan D Nguyen <tnguyen at cpan doe org>
      • -
    -
    • -
+

These tags are <item> and </item> which should enclose all fields from the biblio, biblioitems, and items tables.

-

An example of using these two tags in a notice template might be like:

+

An example of using these tags in a notice template might be like:

-
The following item(s) is/are currently overdue:
+
The following item(s) is/are currently overdue:

 
-   <item>"<<biblio.title>>" by <<biblio.author>>, <<items.itemcallnumber>>, Barcode: <<items.barcode>> Fine: <<items.fine>> </item>
+

<item>"<<biblio.title>>" by <<biblio.author>>, <<items.itemcallnumber>>, Barcode: <<items.barcode>> Fine: <<items.fine>></item>

Which, assuming two items were overdue, would result in a notice like:

-
The following item(s) is/are currently overdue:
+
The following item(s) is/are currently overdue:

 
-   "A Short History of Western Civilization" by Harrison, John B, 909.09821 H2451, Barcode: 08030003 Fine: £3.50
-   "History of Western Civilization" by Hayes, Carlton Joseph Huntley, 909.09821 H3261 v.1, Barcode: 08030004 Fine: £3.50
+

"A Short History of Western Civilization" by Harrison, John B, 909.09821 H2451, Barcode: 08030003 Fine: 3.50
+ "History of Western Civilization" by Hayes, Carlton Joseph Huntley, 909.09821 H3261 v.1, Barcode: 08030004 Fine: 3.50

-

Existing Notices & Slips

+

Existing Notices & Slips

Among the default notices are notices for several common actions within Koha. All of these notices can be customized by altering their text via the Notices & Slips tool and their style using the NoticeCSS preference to define a stylesheet. Here are some of what those notices do

-
  • ACCTDETAILS
      @@ -75,78 +95,200 @@
    • ACQCLAIM (Acquisition Claim)
      • Used in the claim acquisition module
        • -
      • Get there: More > Acquisitions > Late issues
        • +
      • Get there: More > Acquisitions > Late issues
        • +
      +
      • +
    • CHECKIN +
        +
      • This notice is sent as the 'Check in' notice for all items that are checked in
        • +
      • This notice is used if two criteria are met: +
          +
        1. The EnhancedMessagingPreferences is set to 'Allow'
          2. +
        2. The patron has requested to receive this notice +
            +
          • Get there: OPAC > Login > my messaging
            • +
          • Get there: Staff Client > Patron Record > Notices
            • +
          +
          3. +
        +
        • +
      +
      • +
    • CHECKOUT +
        +
      • This notice is sent as the 'Check out' notice for all items that are checked out
        • +
      • This notice is used if two criteria are met: +
          +
        1. The EnhancedMessagingPreferences is set to 'Allow'
          2. +
        2. The patron has requested to receive this notice +
            +
          • Get there: OPAC > Login > my messaging
            • +
          • Get there: Staff Client > Patron Record > Notices
            • +
          +
          3. +
        +
        • +
      +
      • +
    • DUE +
        +
      • This notice is sent as the 'Item due' for an item is due
        • +
      • This notice is used if two criteria are met: +
          +
        1. The EnhancedMessagingPreferences is set to 'Allow'
          2. +
        2. The patron has requested to receive this notice +
            +
          • Get there: OPAC > Login > my messaging
            • +
          • Get there: Staff Client > Patron Record > Notices
            • +
          +
          3. +
        +
        • +
      +
      • +
    • DUEDGST +
        +
      • This notice is sent as the 'Item due' for all items that are due
        • +
      • This notice is used if two criteria are met: +
          +
        1. The EnhancedMessagingPreferences is set to 'Allow'
          2. +
        2. The patron has requested to receive this notice as a digest +
            +
          • Get there: OPAC > Login > my messaging
            • +
          • Get there: Staff Client > Patron Record > Notices
            • +
          +
          3. +
        +
    • HOLD (Hold Available for Pickup)
      • This notice is used if two criteria are met:
          -
        1. The EnhancedMessagingPreferences is set to 'Allow'
          2. +
        2. The EnhancedMessagingPreferences is set to 'Allow'
        3. The patron has requested to receive this notice
            -
          • Get there: OPAC > Login > my messaging
            • -
          • Get there: Staff Client > Patron Record > Notices
            • +
          • Get there: OPAC > Login > my messaging
            • +
          • Get there: Staff Client > Patron Record > Notices
        • -
      • When this notice references the branches table it is referring to the pickup library information.
        • +
      • When this notice references the branches table it is referring to the pickup branch information.
    • HOLDPLACED (a notice to the library staff that a hold has been placed)
      • This notice requires the emailLibrarianWhenHoldIsPlaced system preference to be set to 'Enable'
        • -
      • When this notice references the branches table it is referring to the pickup library information.
        • +
      • When this notice references the branches table it is referring to the pickup branch information.
    • ODUE (Overdue Notice)
      • This notice is used to send Overdue Notices to Patrons
        • -
      • See a Sample Overdue Notice
        • -
      • Requires that you set Overdue Notice/Status Triggers
        • +
      • Requires that you set Overdue Notice/Status Triggers
        • +
      +
      • +
    • PREDUE +
        +
      • This notice is sent as the 'Advanced notice' for an item is due
        • +
      • This notice is used if two criteria are met: +
          +
        1. The EnhancedMessagingPreferences is set to 'Allow'
          2. +
        2. The patron has requested to receive this notice +
            +
          • Get there: OPAC > Login > my messaging
            • +
          • Get there: Staff Client > Patron Record > Notices
            • +
          +
          3. +
        +
        • +
      +
      • +
    • PREDUEDGST +
        +
      • This notice is sent as the 'Advanced notice' for all items that are due
        • +
      • This notice is used if two criteria are met: +
          +
        1. The EnhancedMessagingPreferences is set to 'Allow'
          2. +
        2. The patron has requested to receive this notice as a digest +
            +
          • Get there: OPAC > Login > my messaging
            • +
          • Get there: Staff Client > Patron Record > Notices
            • +
          +
          3. +
        +
        • +
      +
      • +
    • RENEWAL +
        +
      • This notice is sent as the 'Check out' notice for all items that are renewed
        • +
      • This notice is used if three criteria are met: +
          +
        1. The EnhancedMessagingPreferences is set to 'Allow'
          2. +
        2. The RenewalSendNotice preference is set to 'Send'
          3. +
        3. The patron has requested to receive the checkout notice +
            +
          • Get there: OPAC > Login > my messaging
            • +
          • Get there: Staff Client > Patron Record > Notices
            • +
          +
          4. +
        +
    • RLIST (Routing List)
      • Used in the serials module to notify patrons/staff of new issues of a serial
          -
        • Get there: More > Serials > New Subscription
          • +
        • Get there: More > Serials > New Subscription
      • You have the option to select the 'Routing List' notice when creating a new subscription (Choose from the 'Patron notification' drop down).
        • -
      • Tip: Notice also that if you'd like to notify patrons of new serial issues, you can click on 'define a notice' which will take you to the 'Notices' tool
        • +
      • Tip: Notice also that if you'd like to notify patrons of new serial issues, you can click on 'define a notice' which will take you to the 'Notices' tool
        • +
      +
      • +
    • SHARE_ACCEPT +
        +
      • Used to notify a patron when another patron has accepted their shared list.
        • +
      • Requires that you set OpacAllowSharingPrivateLists to 'Allow'
        • +
      +
      • +
    • SHARE_INVITE +
        +
      • Used to notify a patron that another patron would like to share a list with them.
        • +
      • Requires that you set OpacAllowSharingPrivateLists to 'Allow'
    -

    There are also a set of predefined slips (or receipts) listed on this page. All of these slips can be customized by altering their text via the Notices & Slips tool and their style using the SlipCSS preference to define a stylesheet.

    - -

    Here is what those slips are used for:

    +

    There are also a set of predefined slips (or receipts) listed on this page. All of these slips can be customized by altering their text via the Notices & Slips tool and their style using the SlipCSS preference to define a stylesheet. Here is what those slips are used for:

      -
    • ISSUEQSLIP +
    • ISSUEQSLIP
        -
      • Used to print the quick slip in circulation
        • -
      • The quick slip only includes items that were checked out today
        • +
      • Used to print the quick slip in circulation
        • +
      • The quick slip only includes items that were checked out today
      • -
    • ISSUESLIP +
    • ISSUESLIP
        -
      • Used to print a full slip in circulation
        • -
      • The slip or receipt will show items checked out today as well as items that are still checked out
        • +
      • Used to print a full slip in circulation
        • +
      • The slip or receipt will show items checked out today as well as items that are still checked out
      • -
    • RESERVESLIP +
    • RESERVESLIP
        -
      • Used to print a holds slip
        • -
      • The holds slip is generated when a hold is confirmed
        • +
      • Used to print a holds slip
        • +
      • The holds slip is generated when a hold is confirmed
      • -
    • TRANSFERSLIP +
    • TRANSFERSLIP
        -
      • Used to print a transfer slip
        • -
      • The transfer slip is printed when you confirm a transfer from one library to another in your system
        • +
      • Used to print a transfer slip
        • +
      • The transfer slip is printed when you confirm a transfer from one branch to another in your system
    diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/help/tools/overduerules.tt b/koha-tmpl/intranet-tmpl/prog/en/modules/help/tools/overduerules.tt index f2b7f7ce12..83c3d710a6 100644 --- a/koha-tmpl/intranet-tmpl/prog/en/modules/help/tools/overduerules.tt +++ b/koha-tmpl/intranet-tmpl/prog/en/modules/help/tools/overduerules.tt @@ -15,7 +15,11 @@
  • To send additional notices, click on the tabs for 'Second' and 'Third' notice
    • -
  • If you would like to prevent a patron from checking items out because of their overdue items, check the 'Restrict' box, this will put a notice on the patron's record at checkout informing the librarian that the patron cannot check out due to overdue items.
    • +
  • If you would like to prevent a patron from checking items out because of their overdue items, check the 'Restrict' box, this will put a notice on the patron's record at checkout informing the librarian that the patron cannot check out due to overdue items. +
      +
    • If you choose to restrict a patron in this way you can also have Koha automatically remove that restriction with the AutoRemoveOverduesRestrictions preference.
      • +
    • +
  • Next you can choose the delivery method for the overdue notice. You can choose from Email, Feed, Phone (if you are using the iTiva Talking Tech service), Print and SMS (if you have set your SMSSendDriver).
  • See a Sample Overdue Notice
    • -- 2.39.5