Home → Administration Manual for Libraries → Notifications and Action Triggers → Creating Alternate Message Templates
Last Updated 11/09/2023
Administrators can create alternate templates for action triggers that will generate Locale Specific messages. If you send notices in multiple languages, we recommend putting some words to that effect in your notice templates. The template, message and message title can all be localized. This allows libraries to set patrons' accounts to receive messages in languages other than English.
Note: This feature does not automatically translate existing templates, and an Evergreen administrator must create new alternate templates for each desired locale.
This feature requires two separate elements to function properly:
System administrators can create alternate templates by following these steps:
In order for the alternate template you created in the last step to actually go out, patrons must have a language preference set in their accounts. Staff can set it via the Staff Client in the Edit screen of the patron's account, or while registering a patron.
To use the feature the following UI elements have been added:
When you double-click on an Event Definition under Notifications / Action Triggers to edit it there will be a tab option for Edit Alternate Template if the reactor is ProcessTemplate, SendEmail, or SendSMS.
In the Patron Registration and Patron Editor screens staff members may select a locale for a patron and edit it in the Patron Preferred Language field.
The templates used on the Edit Definition tab are the defaults that are used if there are no alternate templates available that match the preferred language. If alternate templates are available the system will use a locale that is an exact match and then if failing that use one where the language code matches and then fall back to the default one.
For example, if a patron has a locale of fr-CA and there are templates for both fr-CA and fr-FR it will use the fr-CA. If the fr-CA template was deleted it would fall back on using the fr-FR for the patron since it at least shares the same base language.
Valid locales are the codes defined in the i18n_locale
table in the config schema.