LibAnswers 2.12.0 Encryption Update Now Live

Exciting news for LibAnswers subscribers, especially for those of you who are concerned about ensuring patron privacy (so, everyone, right?? 😉 ) – in today’s release, we’re rolling out encryption for key patron identifying information as it’s being stored in the LibAnswers database (aka “at rest”). This is one more step in our continuing efforts to ensure that patron data is safe and secure.

Patron Data Encrypted At Rest

Your patrons’ email address and SMS numbers are now encrypted as they’re being stored in the LibAnswers database, as long as they’re in fields that we know to contain email and SMS numbers, ie this does not yet apply to information shared in the text of a patron’s reply. There’s nothing you need to do to opt in to this change – as of this morning, all key patron email addresses and SMS numbers have been encrypted. This also won’t impact your ability to see the “history” of transactions with specific patrons or to run statistics.

Additional Bug Fixes

While testing for the big Encryption update, we ran into a few small bugs which we squashed like Godzilla. Here’s the rundown:

  • Reply Editing – Sometimes patron replies that are submitted into the system can either show up as too long (where they include the entire reply thread in a single reply), or too short (where a key piece of information gets cut off). To help with these, we’ve added a new option to edit the patron’s reply, so you can simplify or clarify individual patron replies. To do this, head to any ticket with patron replies, click the cog icon on a particular reply, and select “Edit Reply” – this will bring up the text of the original patron reply alongside a rich text editor, which you can use to edit the reply’s content.
  • Manage Assets: Edit File & Click Filename – We noted a couple of small issues on the Manage Assets screen, where clicking on an asset’s title didn’t do anything (instead of loading a preview of the file as intended), and editing a file lead to some pretty odd errors. We’ve squashed both of these issues – to see the fixes in action, head to Admin > Manage Assets.
  • Chat Widgets Now Load via HTTPS – This has been an optional setting for LibChat, but in this update we’ve streamlined things so that chat widgets now load via HTTPS by default, so patron chats load via SSL right from the get go.
  • Systems Status Management: Image Manager – We realized the image manager icon was missing from the product description field – oops! This is now back – Admins, head to Admin > System Status Management > Edit Product and you’ll see it’s back.
  • API Issues:
    • There was a minor issue where the search API was not properly returning the total number of results, which we’ve since quashed.
    • There was also an issue where adding an IP restriction for the API wasn’t being applied properly to widget – this is also fixed.
  • Accessibility Updates:
    • We’ve added an aria label to the hamburger menu (visible when viewing a site on a mobile device).
    • For screenreaders, we’ve added aria-hidden=true to the hidden input for the typeahead widget, as it was causing accessibility errors.

Leave a Reply

Your email address will not be published. Required fields are marked *

Confirm you aren't spamming: * Time limit is exhausted. Please reload the CAPTCHA.

%d bloggers like this: