Evergreen 2.12-beta Release Notes

SMS carrier definitions are now included for Google Fi and Republic Wireless. These will be automatically loaded when installing a new Evergreen system; admins who wish to add these definitions during an upgrade can use the following email gateway values:

The bibliographic fingerprint will now incorporate subfield n and p from MARC title fields to better distinguish between records of the same series that may share the same title but have a different part. With this change, these MARC records will no longer be grouped together in a Group Formats & Editions search.

The bibliographic fingerprint was also changed to better distinguish between a the fields contributing to the fingerprint. This change will help the system distinguish between a record for the movie Blue Steel and another record for the book Blue written by Danielle Steel.

Adds a new open-ils.hold-targeter service, supporting new targeting options and runtime optimizations to speed up targeting. The service is launched from a new targeting script, hold_targeter_v2.pl (default location: /openils/bin/hold_targeter_v2.pl).

This code has no effect on the existing hold targeter, which is still available as of this release and functions as before.

Add a separate make target during installation for translator to allow for easier installation of i18n prerequisites.

Required permissions that were previously missing from the stock data have now been added. If Evergreen sites have already manually added these permissions, the upgrade script will remove the old permission and create the new one, maintaining any maps to permission groups, with the stock permission ID.

In action trigger templates it’s now possible to call helpers.get_org_unit_ancestor_at_depth($id_or_aou, $depth) in order to retrieve a fleshed aou for the target aou’s ancestor at the chosen depth. This could be used to retrieve the name of the library system rather than a specific branch name, for instance.

There was an unused duplicate selfcheck password setting that was removed to avoid confusion over which library setting was supposed to be set to enable passwords for selfcheck. After upgrading, verify that your library policy remains consistent for this setting.

Unprivileged users can retrieve organizational unit setting values for setting types lacking a "view" permission. When the feature adding Stripe credit card processing was added, the upgrade script neglected to add the VIEW_CREDIT_CARD_PROCESSING permission to the organizational unit setting type. This means that anyone can retrieve and view the settings for Stripe credit card processing.

Any system that upgraded from Evergreen version 2.5 to 2.6 is affected. If you use Stripe for credit card processing, it is strongly recommended that you apply this upgrade. Even if you do not use Stripe, applying this upgrade is still recommended. If you did not upgrade from version 2.5 to 2.6 of Evergreen, but started with a later version, applying this upgrade is harmless.

Catalogers can now select a MARC merge/overlay profile to apply when merging records in the (browser client) record bucket merge and Z39.50 record overlay interfaces. In both interfaces, if the user selects a merge profile, the results of the merge are displayed, giving the user the opportunity to choose a different merge profile or edit the records involved prior to committing to the merge.

A new library setting, "Default Merge Profile (Z39.50 and Record Buckets)", specifies the merge profile to preselect in the new merge profile selectors in the record bucket merge and Z39.50 overlay logs. The selectors will also remember the last selection that the user made.

Two library settings are used to control the display of copy alert messages or copy location check in alerts when recording in-house-use in Evergreen.

Setting Display copy alert for in-house-use to true for an organization will cause an alert to appear with the copy’s alert message, if it has one, when recording in-house-use for the copy.

Setting Display copy location check in alert for in-house-use to true for an organization will cause an alert to display a message indicating that the item needs to be routed to its location if the location has check in alert set to true.

The settings are independent of one another because you may want to display one and not the other when recording in-house-use.

The active date will now be available as a column picker option in the Item Status screen.

When performing a patron search, punctuation characters will be ignored. So if the patron is named O’Brien, then you can enter Obrien, O’Brien, O Brien, etc. in the search box.

This behavior affects the Last Name (internally: family_name), First Name (first_given_name), and Middle Name (second_given_name) fields of the search.

Improvements were made to the Evergreen self-check interface to make it easier to use in a touch-screen environment.

The new web staff client is ready for trial production use in all functional areas with the exception of serials and offline transactions. In addition to many bug fixes in the areas of circulation, cataloging, administration and reporting, Release 2.12 sees the following additions to web client functionality.

The Evergreen developers will keep pilot libraries updated about known web client issues by posting known bugs to https://wiki.evergreen-ils.org/doku.php?id=dev:browser_staff:known_issues .

Previously, adjusting the time zone in which a database session operates could not be done in any way except globally, directly within the database. However, allowing modification of the timezone parameter now supports localization efforts for those consortia that span multiple time zones.

New subject browse index definitions have been added that display the entire heading as a unit with hyphens between terms instead of displaying individual terms separately.

For example, the browse heading for:

=650 \0$aCats$zUnited States$vCorrespondence.

will display in a single entry as:

Cats — United States — Correspondence

Rather than separate entries for Cats and United States.

Name subjects will continue to display as separate entries because additional work would be required for the heading to be punctuated correctly.

Advanced search limiters will no longer propagate to the basic search box in the catalog. Instead, the limiters applied to the search will appear in the left sidebar of the search results screen where they can be easily cleared by clicking an x. On a small, mobile device, the advanced search limiters can be seen by clicking an x filter applied link or by clicking the Refine these results button that typically shows facets to the user.

The selected limiters will be applied to any search from the search bar until: * The user actively removes the filters from the search or * The user starts a new basic or advanced search from scratch.

New stylesheets and other changes to the catalog to allow for better support of right-to-left (RTL) languages, such as Arabic.

Also add Arabic (Jordan) as a new supported language.

OverDrive and OneClickdigital integration has been added to Evergreen. The system will now support: * Display of e-book availability in the search results and record summary pages. * Display of e-book checkouts and holds in a patron’s My Account pages.

To enable this feature, Evergreen sites need to: * Ensure the new <http_client> block and open-ils.ebook_api service have been added to opensrf.xml and (in the case of the open-ils.ebook_api_service) opensrf_core.xml. Both blocks are now included in the example files. * Contact their vendor to obtain credentials for their API account. * Edit the config.tt2 file to set ebook_api.enabled to true. Administrators will also need to enable specific vendor APIs and add base URIs that are used in 856 fields. * Add the credentials for their API account in the new Ebook API Integration settings provided in the Library Settings Editor.

The record summary pages in the catalog will now link to other formats and editions of a title. The links will allow users to quickly jump to another format of the title or an edition written in another language.

This release brings several improvement to the Group Formats and Editions search.

Before the TPAC, a site could configure the public catalog to use metarecord searching by default, via a configuration file. Here we bring that back.

A new setting called search.metarecord_default is present in templates/opac/parts/config.tt2 to enable this feature. By setting this to a true value (normally 1) the TPAC will silently include the #metabib search modifier in the search form on any interfaces that do not have a UI component that allows the user to control the setting.