Consortia Notices critically needed in LX Starter
Help your consortia friends and vote - please!
In Sierra consortia have the ability to send notices across all locations. This is a critical service used daily. Large consortia that spread across large geographical areas use system holds to meet local demand. This means a patron may have a title that has been provided by a library they never stepped foot in or may not even heard of. Seeing an email that hails from an unkown entity looks like spam. A message from the library system has a fighting chance of getting opened.
Consortia use central messaging for courtesy notices also to keep patrons from being bombarded with multiple messages in a single day. One courtesy notice covers all of their checked out items.
If Sierra can do this, shouldnt LX Be able to do this too? Please help consortia leave Jasper based circ notices behind too. You lucky standalone libraries should vote for this too- give us poor consortia a chance to achieve what you already have - Please - yes - I am begging (it is what you do when your are a consortia).
-
Alexis Camarda commented
This is vital for consortia! The number of notices that would be sent if we didn't have central messaging would be absolutely staggering. I will also wholeheartedly agree that we are also SO ready to leave (the very outdated and tired) Jasper-based circ notices behind.
-
Denise Heid Scarbeck commented
This is an absolute necessity for us poor little consortia. Getting patrons to read our communications is hard enough without our power users feeling bombarded by email after email after email for each individual item they have checked out or reserved. This would be ideal.
-
Nicole Castellano commented
One thing to note is that patrons will not only disregard spam, but an email who's been bombarding them with messages (at least I do). Consolidating messages will increase the chances of the emails being read as well.
-
Kathryn Brew commented
In a consortium, it would be very useful to have a system level as well as library level (and branch level below that). I would want this ability for all notice types, so that different consortia can choose to send any or all notice types from the system as opposed to from members, according to what makes sense in their context. Additionally, having a functionality in which the individual consortia members can choose to use or copy+modify the system-level notifications would be ideal. Not all libraries want to do their own emails (from scratch, or at all).