- ODUE1,Overdue 1
- ODUE2, Overdue 2
- ODUE3, Overdue 3
System preferences
- If sending SMS messages, set SMSSendDriver to "Springshare".
- If sending Voice messages, set PhoneNotification to "Enable".
To configure the notices, you'll clear out the text in the Koha notice and input the YAML blob. The YAML can be found on the github page which we've linked to previously in the article.
The YAML should be input when you're ready to start sending notices through the plugin. This cannot be done ahead of time. See "When should I input the YAML blob" below.
The patron facing notices will be configured in Springshare's "LibConnectPro" interface, not in Koha.
The YAML should be input in the Koha notice when you're ready to start sending notices via the webhook plugin but not before. Springshare might ask you to test sending notices by sending notices to staff members, and this can be accomplished with some template toolkit in the notice. If you need help with this, submit a ticket.
Plugin configuration
Install and configure the Springshare plugin on your site, adding library credentials (OAuth2 Token Endpoint URL, Client ID, Client Secret, Webhook Endpoint URL, and Customer ID).
This information should be given to you by Springshare. If they have not given it to you yet, reach out to them.
Notice configuration
In Tools > Notices and slips, for all notices the library will be sending through Springshare:
- Copy/paste the YAML syntax from the Github documentation into the Email, SMS, and/or Phone tabs, as applicable.
- Keep content in the Print tab for any notices that the library will want to print.
Note that Springshare requires that overdue notices use the letter codes ODUE1, ODUE2, and ODUE3.
Do staff need to capture patrons' mobile provider for Springshare SMS messages?
No, the mobile provider is not necessary for SMS messages sent through Springshare.
Do SMS numbers need hyphens?
No, SMS numbers do not need hyphens.
Do SMS numbers need the leading 1?
No, SMS numbers do not need the leading 1. Springshare will add it on their end. If your phone numbers have the leading 1, you do not need to remove them.
How does Springshare know what messages to send?
When a message to a patron is triggered by messaging preferences or overdue notice triggers, anything in a template where Koha finds "webhook: yes" will be compiled and transmitted to Springshare via the plugin. When the process_message_queue.pl cron runs, it passes those YAML bits to the plugin, the plugin pulls the related metadata for the indicated patron, checkout, item, etc. and this information is formatted into a JSON file and sent to Springshare.
How will libraries know what Springshare-controlled notices have been sent/delivered?
Patrons’ Notices tab will display the YAML data that was transmitted to Springshare via the plugin. The notice status in Koha will indicated whether or not the notice was successfully transmitted to Springshare, rather that whether or not it was delivered to the patron. Libraries should contact Springshare for the specific formatted notices sent to patrons and details of their delivery status.
Frequently Asked Questions
Can a message be resent?
Libraries can resend notices from the patron screen. The message status reverts to pending and the plugin will grab that message, and transmit it to Springshare again.
If a checked out item is returned to the library, will the patron still get a message?
Yes. The plugin will check the issues table before compiling the JSON file to send to Springshare. If it doesn't find the checkout, it will look to the oldissues table and pull the data for the JSON blob to send to Springshare from there instead. For this reason, a checkout message can be sent to Springshare, even after an item has been returned.