Evergreen 3.2 Release Notes

Like the AngularJS application, Evergreen releases will come with all web browser staff client code pre-compiled. Admins only need to add an Apache configuration change.

Add the following stanza to /etc/apache2/eg_vhost.conf.

For multi-locale sites, see the bottom section of Open-ILS/examples/apache[_24]/eg_vhost.conf.in for a sample fr-CA configuration. The section starts with "/eg2/ client setup and locale configuration"

Developers building Angular code on existing installations need to update their version of NodeJS by re-running the -developer prereqs installer.

When a copy (line item detail) is canceled through the Acquisitions interface, the parent line item is also canceled if all copies for that line item are also canceled. The cancel reason given will come from:

Acquisitions invoices have 2 new fields:

As with the now-defunct complete field, but new fields are cleared in the event an invoice is reopened.

These new fields are visible in the invoice interface under the Show Details action for closed invoices.

The existing interface for staff-mediated patron acquisition requests has been replaced in the web staff client with a re-implementation written in AngularJS, with some minor bug fixes (including access from the Patron interface) and other improvements.

The original hold_targeter.pl script has been renamed to "hold_targeter_legacy.pl", and the new-style hold targeting script has been renamed to "hold_targeter.pl". Administrators will want to change their crontab files to reflect this.

The sample crontab file at Open-ILS/examples/crontab.example reflects this change.

With Evergreen 3.2, we introduce the initial infrastructure for migrating to a new version of Angular. The structure of the new code is quite different from the AngularJS code and it runs as a separate application which communicates with the AngularJS app via shared storage and in-page URLs that link back and forth between the two.

For this release, users will only be directed to the new Angular site when navigating to Administration ⇒ Acquisitions Administration. Once on this page, some of the admin interfaces will presented as Angular6 interfaces, while others will direct users back to the AngularJS application. The Angular6 interfaces are the simpler, grid-based interfaces.

Add UPC as a search attribute for both OCLC and LOC targets in z39.50 for cataloging.

Vandelay imports are now monitored from the browser client asynchronously, meaning the client requests updates from the server instead of waiting for the server to respond to the original import request. This changes allows for incremental progress updates in the browser client.

Evergreen now provides an option to add an inventory date to items to facilitate the process of performing inventory in libraries. Staff can add an inventory date to an item in one of the following ways: * From the check in screen, there is now an Update Inventory check in modifier. When selected, scanned barcodes will have the current date/time added as the inventory date while the item is checked in. * From the Item Status screen, an action is available to add the current date/time as the inventory date to selected items.

This new feature will also store the workstation that was used when the inventory date was updated.

A program named pingest.pl is now installed to allow faster bibliographic record ingest. It performs ingest in parallel so that multiple batches can be done simultaneously. It operates by splitting the records to be ingested up into batches and running all of the ingest methods on each batch. You may pass in options to control how many batches are run at the same time, how many records there are per batch, and which ingest operations to skip.

A new interface allows catalogers to retrieve a specific authority record using its database ID. Catalogers can find those IDs in subfield $0 of matching fields in bibliographic records.

To use the new authority record viewer:

Circulation policies in Evergreen can now be configured to automatically renew certain items checked out on patron accounts. Circulations will be renewed automatically up to a custom limit (the max_auto_renewal field) and patrons will not need to log in to their OPAC accounts or ask library staff to manually renew materials.

Two new action triggers have been added to Evergreen that permit the Auto-Renew feature. They can be found, configured, and enabled in Administration>Local Administration>Notifications/Action Triggers. They are named Autorenew and AutorenewNotify.

The Autorenew A/T definition uses the checkout.due hook to automatically validate and renew (in the reactor) circulations on the day they are due, grouped by user. The output events of this definition is is the input used by the related AutorenewNotify A/T that simply uses a new hook called autorenewal to notify patrons via email of their currently due or auto-renewed items.

In the webstaff’s Patron Items Out page, the new column AutoRenewalsRemaining indicates how many autorenewals are available for a particular circulation.

Staff are provided with interfaces and mechanisms to create library closings that, in addition to affecting future circulation and booking due dates, and hold shelf expirations, will automatically move existing circulation and booking due dates and hold shelf expiration times. This new functionality is conceptually described as Emergency Closings and business logic implementing it as the Emergency Closing Handler. It contains additions and adjustments to the user interface, business logic, and database layers. Access to this functionality is available through the Closed Dates Editor interface in the staff client which has been ported to AngularJS.

The legacy XUL staff client is no longer supported in Evergreen 3.2.x and the server-side installation no longer supports a direct connection by a version XUL client by default. All users of Evergreen 3.2.x are strongly urged to complete their switch to the web staff client as part of upgrading to 3.2.x.

Evergreen administrators who for some reason continue to wish to deploy the XUL staff client can do so at their risk by supplying STAFF_CLIENT_STAMP_ID during the make install step and using make_release to create installers for the staff client. However, no community support will be provided for the XUL client.

In some cases, it is useful to have the ability to reorder permission, or to make only specific groups available in the permission group selector for specific Org Units. An interface has been made available to allow this.

Browser client settings and preferences that should persist over time are now stored as settings on the server. This allows settings to follow users and workstations and reduces problems associated with losing settings as a result of clearing browser data.

The browser client honors setting values stored as user settings, workstation settings, and org unit settings, depending on which setting types are locally configured.

Terminology has been updated in the staff client so that we consistently use the same name to describe the same thing. The following updates have been made:

The public catalog now displays checkboxes on the bibliographic and metarecord constituents results pages. Selecting one or more titles by using the checkboxes will dynamically add those title to the temporary list, which is now renamed the cart.

Above the results lists there is now a bar with a select-all checkbox, a link to the cart management page that also indicates the number of of titles in the cart, and a link to remove from the cart titles that are selected on the currently displayed results page.

The search bar now includes an icon of a cart and displays the number of titles currently in the cart. Next to that icon is a menu of cart actions.

The cart actions available are Place Hold, Print Title Details, Email Title Details, Add Cart to Saved List, and Clear Cart. In the web staff client, the cart actions also include Add Cart to Bucket. When an action is selected from this menu, the user is given an opportunity to confirm the action and to optionally empty the cart when the action is complete. The action is applied to all titles in the cart.

Clicking on the cart icon brings the user to a page listing the titles in the cart. From there, the user can select specific records to request, print, email, add to a list, or remove from the cart.

The list of actions on the record details page now provides separate links for adding the title to a cart or to a permanent list.

The permanent list management page in the public catalog now also includes batch print and email actions.

This adds the .searchbar-home class to the div that contains the searchbar when on the homepage. This allows sites to customize the searchbar differently on the homepage than in other places the search bar appears (for example, offering a large, Google-style search bar on the homepage only).

To make customization easier, the username hint on the OPAC login page ("Please include leading zeros…") has been moved to a separate TT2 template. If you have customized the hint text, you will need to add your modifications to username_hint.tt2.