Evergreen 3.7.0 Release Notes

The Evergreen OPAC can now be used as a Service Provider (SP) in a Single Sign On infrastructure. This allows system administrators to connect the Evergreen OPAC to an identity provider (IdP). Such a scenario offers significant usability improvements to patrons:

It can also offer security benefits, if it enables a Shibboleth-enabled Evergreen installation to move away from insecure autogenerated user passwords (e.g. year of birth or last four digits of a phone number).

Different Org Units can use different IdPs. This development also supports a mix of Shibboleth and non-Shibboleth libraries.

Note that only the OPAC can be integrated with Shibboleth at this time; no such support exists for the staff client, self-check, etc.

Also note that this development does not include automatic provisioning of accounts. At this time, matching accounts must already exist in Evergreen for a patron to successfully authenticate into the OPAC via Single Sign On.

Evergreen now has the ability to prevent staff users whose accounts have expired from logging in. This is controlled by the new global flag "auth.block_expired_staff_login", which is not enabled by default. If that flag is turned on, accounts that have the STAFF_LOGIN permission and whose expiration date is in the past are prevented from logging into any Evergreen interface, including the staff client, the public catalog, and SIP2.

It should be noted that ordinary patrons are allowed to log into the public catalog if their circulation privileges have expired. This feature prevents expired staff users from logging into the public catalog (and all other Evergreen interfaces and APIs) outright in order to prevent them from getting into the staff interface anyway by creative use of Evergreen’s authentication APIs.

Evergreen admins are advised to check the expiration status of staff accounts before turning on the global flag, as otherwise it is possible to lock staff users out unexpectedly. The following SQL query will identify expired but otherwise un-deleted users that would be blocked by turning on the flag:

Note that this query can take a long time to run in large databases given the general way that it checks for users that have the STAFF_LOGIN permission. Replacing the use of permission.usr_has_perm_at_all() with a query on expired users with profiles known to have the STAFF_LOGIN permission will be much faster.

Evergreen now uses GIN indexes for full text search in PostgreSQL. GIN indexes offer better performance than GIST. For more information on the differences in the two index types, please refer to the PostgreSQL documentation.

An upgrade script is provided as part of this migration. If you upgrade normally from a previous release of Evergreen, this upgrade script should run as part of the upgrade process. The migration script recommends that you run a VACUUM ANALYZE in PostgreSQL on the tables that had the indexes changed. The migration process does not do this for you, so you should do it as soon as is convenient after the upgrade.

Evergreen had a method of making a custom build of the Dojo JavaScript library. Following this procedure could improve the load times for the OPAC and other interfaces that use Dojo. However, very few sites took advantage of this process or even knew of its existence.

As a part of the process, an openils_dojo.js file was built and installed along with the other Dojo files. Evergreen had many references to load this optional file. For the majority of sites that did not use this custom Dojo process, this file did not exist. Browsers would spend time and resources requesting this nonexistent file. This situation also contributed noise to the Apache logs with the 404 errors from these requests.

In keeping with the goal of eliminating Dojo from Evergreen, all references to openils_dojo.js have been removed from the OPAC and other files. The profile script required to make the custom Dojo build has also been removed.

This release adds 7 Czech-language MARC records to the sample data set (also known as Concerto data set).

Publisher values are now extracted for display from tags 260 OR 264.

This feature allows staff to add multiple users to a named hold group bucket and place title-level holds for a record for that entire set of users. Users can be added to such a hold group bucket from either the patron search result interface, via the Add to Bucket dropdown, or through a dedicated Hold Group interface available from the Circulation menu. Adding new patrons to a hold group bucket will require staff have the PLACE_HOLD permission.

Holds can be placed for the users in a hold group bucket either directly from the normal staff-place hold interface in the embedded OPAC, or by supplying the record ID within the hold group bucket interface. In the latter case, the list of users for which a hold was attempted but failed to be placed can be downloaded by staff in order to address any placement issues. Placing a hold group bucket hold will requires staff have the MANAGE_HOLD_GROUPS permission, which is new with this development.

In the event of a mistaken hold group hold, staff with the MANAGE_HOLD_GROUPS permission will have the ability to cancel all unfulfilled holds created as part of a hold group event.

A link to the title’s hold interface is available from the list of hold group events in the dedicated hold group interface.

The Scan Item As Missing Pieces interface is now an Angular interface. The functionality is the same, but the interface displays more details on the item in question (title/author/callnum) before proceeding with the missing pieces process.

The "Receive Overdue and Courtesy Emails" user setting permits users to control whether they receive email notifications about overdue items.

To use the setting, modify any action trigger event definitions which send emails about overdue items, setting the "Opt In Setting" to "circ.default_overdue_notices_enabled" and the "User Field" to "usr". You can accomplish this by running the following query in your database:

Once this is done, the patron registration screen in the staff client will show a "Receive Overdue and Courtesy Emails" checkbox, which will be checked by default. To ensure that existing patrons continue to recieve email notifications, you will need to add the user setting to their accounts, which you can do by running the following query in your database:

The "Allow renewal request if renewal recipient privileges have expired" organizational unit setting can be set to true to permit expired patrons to renew circulations. Allowing renewals for expired patrons reduces the number of auto-renewal failures and assumes that a patron with items out eligible for renewals has not been expired for very long and that such patrons are likely to renew their privileges in a timely manner.

The setting is referenced based on the current circulation library for the renewal. It takes into account the global flags for "Circ: Use original circulation library on desk renewal instead of the workstation library" and "Circ: Use original circulation library on opac renewal instead of user home library."

Carousel ordering is now stable and predictable:

The public catalog now defaults to the Bootstrap skin rather than the legacy TPAC skin.

Bootstrap is now the default in order to encourage more testing, but users should be aware of the following issues; certain specific functionality is available only in the TPAC skin.

The TPAC skin remains available for use, but current Evergreen users should start actively considering migrating to the Bootstrap skin.

In order to continue to use the TPAC skin, comment out the following line in eg_vhost.conf

This feature is the first in the series to add native search suggestions to the Evergreen search logic. A significant portion of the code is dedicated to infrastructure that will be used in later enhancements to the functionality.

This functionality integrates 3rd party geographic lookup services to allow patrons to enter an address on the record details page in the OPAC and sort the holdings for that record based on proximity of their circulating libraries to the entered address. To support this, latitude and longitude coordinates may be associated with each org unit. Care is given to not log or leak patron provided addresses or the context in which they are used.

Requires the following Perl modules: Geo::Coder::Free, Geo::Coder::Google, and Geo::Coder::OSM

Configuration instructions:

Two new permissions, VIEW_GEOLOCATION_SERVICES and ADMIN_GEOLOCATION_SERVICES, control viewing and editing values in the Geolocation Location Services interface. They are added to the System Administrator and Global Administrator permissions groups by default.

The Library Groups search feature revives a longstanding internal concept in Evergreen called “Lassos,” which allows an administrator to define a group of organizational units for searching outside of the standard organizational unit hierarchy.

Use case examples include creating a group of law or science libraries within a university consortium, or grouping all school libraries together within a mixed school/public library consortium.

Searches can be restricted to a particular Library Group from the library selector in the public catalog basic search page and from the new "Where" selector on the advanced search page.

Restricting catalog searches by Library Group is available only in the public catalog and "traditional" staff catalog; it is not available in the Angular staff catalog.

This feature adds a new permission, ADMIN_LIBRARY_GROUPS, that allows updating Library Groups and Library Group Maps. This permission is not associated with any profiles by default, and replaces the CREATE_LASSO, UPDATE_LASSO, and DELETE_LASSO permissions.

To define new library groups, use the Server Administration Library Groups and Library Group Maps pages. An autogen and a reload of Apache should be performed after making changes to Library Groups.

Evergreen now has IDs associated with logos and cart images in the TPAC and Bootstrap OPACs to aid in customization. Images are as follows:

The Bootstrap OPAC does not have a homesearch logo icon as it is added in the background by CSS and can be directly styled through the CSS.

Twelve new colors for TPAC have been added to the colors.tt2 file as well as having corresponding changes to the style.css.tt2 file. These use descriptive rather than abstract names. These changes help avoid situations were unreadable values are placed on top of each other and where different values are wanted for elements that only refernece a single color previously. Guidelines are below for setting values that correspond to the previous values used in the colors.tt2 file. For more diverse customizations the OPAC should be reviewed before a production load.

Note that is patch is primarily meant for users who wish to continue using TPAC rather than the Bootstrap skin for a while; new Evergreen users are advised to use the now-default Bootstrap skin.

Previously, the reports scheduler allowed duplicated reports under certain circumstances. A uniqueness constraint now disallows this without adversely affecting the reports process.