Chapter 7. 2.11.0 New Features

Table of Contents

Administration
Add Date Header to Action Trigger Email/SMS Templates
Support for Ubuntu 16.04
Purge User Activity
Cataloging
Authority Record Import Updates Editor, Edit Date.
Authority Propagation Updates Bib Editor / Edit Date
Bibliographic Record Source Now Copied to 901$s
Option to Update Bib Source and Edit Details on Record Import
Circulation
Staff Client Honors Aged Circulations
"Canceled Transit" Item Status
Copy Status "Is Available" Flag
Email Checkout Receipts
Set Per-OU Limits on Allowed Payment Amounts
Client
Additional Fields Available for Display in Some Interfaces
OPAC
Merge Notification Preferences Tables in TPAC
Improved Holds Screens in My Account
Popularity Boost for Ranking Search Results
Removal of Advanced Hold Options link when part holds are expected
SIP
SIP Renewals
Treat SIP Location Field as Login Workstation
Translations
Translation Updates

Administration

Add Date Header to Action Trigger Email/SMS Templates

The Date: header specified in RFC 2822 has been added to the seed data for the example Action Trigger email and SMS templates, but no attempt has been made to automatically modify existing templates. To add this header (and end any "Why are my library emails from 1969/70?" questions you may have heard) make sure the following lines are in all templates that use the SendEmail or SendSMS reactors:

The first is already in most sample templates, but you may need to add it to the top of any custom templates: [%- USE date -%]

And this line should be inserted into the header block of each template: Date: [%- date.format(date.now, '%a, %d %b %Y %T -0000', gmt => 1) %]

Support for Ubuntu 16.04

Adds support for Ubuntu Xenial Xerus (16.04).

Purge User Activity

User activity types are now set to transient by default for new Evergreen installs.. This means only the most recent activity entry per user per activity type is retained in the database.

This change does not affect existing activity types, which were set to non-transient by default. To make an activity type transient, modify the Transient field of the desired type in the staff client under Admin → Server Administration → User Activity Types.

Setting an activity type to transient means data for a given user will be cleaned up automatically if and when the user performs the activity in question. However, administrators can also force an activity cleanup via SQL. This is useful for ensuring that all old activity data is deleted and for controlling when the cleanup occurs, which may be useful on very large actor.usr_activity tables.

To force clean all activity types:

SELECT actor.purge_usr_activity_by_type(etype.id)
    FROM config.usr_activity_type etype;

Note

This could take hours to run on a very large actor.usr_activity table.