 |   | |
| HomePrev | Chapter 3. Release notes | Next |
|---|---|---|
Evergreen enables you to create an organizational tree that describes the systems, branches, or other units that comprise your organization. By default, the org unit tree that appears to patrons in the OPAC is identical to the one that appears to users of the staff client. Using this feature, you can condense or re-order the organizational tree into a simpler structure for patrons using the OPAC while maintaining the complex organizational tree that is available to users of the staff client.
As a further enhancement, you can hide a parental org unit yet still make its child org units visible in the OPAC. In previous versions of Evergreen, child org units inherited the visibility setting of their parents.
Documentation for this feature is available in the Book of Evergreen at http://docs.evergreen-ils.org/2.2/
By default, fines accrue only on dates that the library is open. This feature enables you to charge patrons fines on dates the library is closed. Fines accrue during scheduled closings as well as during normal weekly closed dates.
Documentation for this feature is available in the Book of Evergreen at http://docs.evergreen-ils.org/2.2/
By default, when a patron places a hold on a title, the hold targeter will search for copies to fill the hold only at circulating libraries that are open. Copies at closed libraries are not targeted to fill holds. When turned on, this feature enables Evergreen to target copies that have closed circulating libraries to fill holds. Two new org unit settings control this feature.
Documentation for this feature is available in the Book of Evergreen at http://docs.evergreen-ils.org/2.2/
The basic catalog has been replaced by the Template Toolkit OPAC (TPAC).
Compared to the traditional catalog (JSPAC), TPAC uses far fewer network
calls for each page, resulting in faster loading pages. TPAC is built on the
Template Toolkit language to enable simple but
powerful customization, and supports integrated gettext-based translation
for strings—including placeholders and quantities—for better
internationalization support.
The next feature release of Evergreen will make TPAC the primary catalog and deprecate the use of the JSPAC.
The auto suggest feature suggests the completion of search terms as the user enters his query. By default, the user will see ten suggestions although this number is configurable at the database level. Scroll through suggestions with your mouse, or use the arrow keys to scroll through the suggestions. Select a suggestion to view records that are linked to this suggestion.
This feature is not turned on by default. You must turn it on in the Admin module.
This feature allows staff to create and name sets of copy locations to use as a search filter in the catalog. OPAC-visible groups will display within the library selector in the template toolkit OPAC. When a user selects a group and performs a search, the set of results will be limited to records that have copies in one of the copy locations within the group. Groups can live at any level of the library hierarchy and may include copy locations from any parent org unit or child org unit.
For advanced users, this change includes a new Query Parser filter called location_groups().
The My Lists feature replaces the bookbag feature that was available in versions proior to 2.2. This feature enables you to create temporary and permanent lists; create and edit notes for items in lists; place holds on items in lists; and share lists via RSS feeds and CSV files.
Documentation for this feature is available in the Book of Evergreen at http://docs.evergreen-ils.org/2.2/
The SMS Text Messaging feature enables users to receive hold notices via text message. Users can opt-in to this hold notification as their default setting for all holds, or they can receive specific hold notifications via text message. Users can also send call numbers and copy locations via text message.
Documentation for this feature is available in the Book of Evergreen at http://docs.evergreen-ils.org/2.2/
Users will now have the ability to designate the following preferences in the Template Toolkit catalog (TPAC):
Patrons can now use credit cards to pay fines and bills in My Account of the TPAC.
Implements Print and Email actions as links below the Add to List link in the TPAC record detail page.
When a user is logged into the TPAC and performs a search, this feature indicates in the results set when any of the result items were ever checked out by the logged-in user. Items will only be tagged when the related org setting is enabled and the user has opted in to circ history tracking.
The following enhancements have been added to patron statistical categories:
Staff can now access and update user settings, like notification prefererences and default pickup library, in the patron editor.
Staff can mark a patron’s email address or phone number as invalid in the
patron editor. The system will clear the email (or phone) field from
actor.usr, and [both optionally, per OU setting]:
Enhancements to notifications by telephony, including:
cron, schedule the
set_pbx_holidays script on an Evergreen system to periodically update
the PBX’s table of holidays, based on a given org unit’s closed date ranges.
The new Circulation Limit Groups interface found in the Server administration menu can be thought of as tags the system places on circulations so that it can find them later. The Limit Sets interface found in the Local administration menu defines rules for limiting the number of active circulations a patron may have based on Circulation Modifiers and Limit Groups. These new features support the following options:
The following modifiers have been added to the check-in interface:
This enhancement adds a new checkin_alert column to copy locations. If true (defaults to false), then a routing alert is generated at reshelving time for the location. This is intended for special locations, such as Display, that may require special handling, or that temporarily contain items that are not normally in that location.
Allow choice of placing hold despite age protection. This alters the backend to watch when so much as one copy failed only due to age protection. In JSPAC, an alternate confirm message is shown. In TPAC, the failure message is changed and override is always allowed for the hold in question.
Creates two new types of copy-level holds, Force and Cataloging Recall, that cut in front of all other holds and ignore hold rules. For cataloging recall holds, the copy’s status changes to cataloging when it reaches its destination.
Circulation-time copy locations are now archived with circulations (aged or active).
Using the Statistical Categories Editor, staff can also designate statistical categories (patron and copy) to archive with circulations.
The Acquisitions Load MARC Order Record interface enables you to add MARC records to selection lists and purchase orders and upload the records into the catalog. The Vandelay interface enables you to create specific match points between incoming MARC records and exisiting catalog records. Combining these two features enables you to track on order MARC records through the Acquisitions interface and to utilize the record matching mechanisms available in Vandelay when importing acquisitions records.
Documentation for this feature is available in the Book of Evergreen at http://docs.evergreen-ils.org/2.2/
This feature enables users to receive items from an invoice. Staff can receive individual copies, or they can receive items in batch.
Documentation for this feature is available in the Book of Evergreen at http://docs.evergreen-ils.org/2.2/
Users can now access lineitem actions (for example, receive, unreceive, update barcodes, new invoice) from the acquisitions lineitem search results and selection list interfaces. Also available on these interfaces is a link to copy details where users can take receive actions (receive, unreceive, cancel) on individual copies.
The tags and subfields that display in authority records in Evergreen are defined by control sets. The Library of Congress control set is the default control set in all versions of Evergreen. However, in Evergreen release 2.2, you can create customized control sets for authority records, and you can define thesauri and authority fields for these control sets.
Patrons and staff can browse authorities in the JSPAC. The following fields are browsable by default: author, series, subject, title, and topic. You can add custom browse axes in addition to these default fields.
Documentation for this feature is available in the Book of Evergreen at http://docs.evergreen-ils.org/2.2/
The MARC Batch Import interface features improved matching of records and managing of your import queue. In version 2.2, you can specify match points between incoming and existing records to better detect matching records and prevent record duplication. You can also create quality controls to ensure that incoming matching records are superior in quality to existing catalog records.
You also have new options for managing your queue. You can apply filters to your queue, and you can generate a list of import errors. You can also print your queue, email your queue, or export your queue as a CSV file.
Documentation for this feature is available in the Book of Evergreen at http://docs.evergreen-ils.org/2.2/
You can customize the Copy Editor for staff by hiding fields in the Copy Editor that are not relevant for workflows at particular org units. Descendant org units inherit the settings of their parents.
Documentation for this feature is available in the Book of Evergreen at http://docs.evergreen-ils.org/2.2/
To enable libraries to designate specific sets of records as only for use as
electronic resources, it is possible to configure a bibliographic source such
that physical copies or MFHD records may not be attached to records from that
source. The config.bib_source table now includes a new Boolean column,
can_have_copies, that controls this behavior. If can_have_copies for a
given bibliographic source is TRUE, then the staff client will prevent a
cataloger from adding volumes or MFHD records to records belonging to that
source.
Documentation for this feature is available in the Book of Evergreen at http://docs.evergreen-ils.org/2.2/
You can replace an existing catalog record with a record obtained through a Z39.50 search. No new permissions or administrative settings are needed to use this feature.
Documentation for this feature is available in the Book of Evergreen at http://docs.evergreen-ils.org/2.2/
You can use a permission to restrict users' access to Z39.50 servers. You can apply a permission to the Z39.50 servers to restrict access to that server, and then assign that permission to users or groups so that they can access the restricted servers.
Documentation for this feature is available in the Book of Evergreen at http://docs.evergreen-ils.org/2.2/
By default, the copy editor shows the library shortname (BR1 or CONS) followed by the copy location name (Stacks, Reference). A new workstation setting, under Admin → Workstation Administration → Copy Editor: Copy Location Name First, enables staff to change the display so that the copy location name is displayed first, followed by the library shortname. This may be particularly useful for libraries that have defined one set of copy locations at the consortial level and want to enable quick keyboard navigation to copy locations by typing just the first letters of the copy location.
Documentation for this feature is available in the Book of Evergreen at http://docs.evergreen-ils.org/2.2/
The User Activity Types feature enables you to specify the user activity that you want to record in the database. You can use this feature for reporting purposes. This function will also display a last activity date in a user’s account. Currently, this feature only tracks user authentication.
Documentation for this feature is available in the Book of Evergreen at http://docs.evergreen-ils.org/2.2/
To support integration of Evergreen with organizational authentication systems,
and to reduce the proliferation of user names and passwords, Evergreen offers
a new service called open-ils.auth_proxy. If you enable the service,
open-ils.auth_proxy supports different authentication mechanisms
that implement the authenticate method. You can define a chain of these
authentication mechanisms to be tried in order within the <authenticators>
element of the opensrf.xml configuration file, with the option of falling
back to the native mode that uses Evergreen’s internal method of password
authentication.
This service only provides authentication; there is no support for automatic provisioning of accounts. To authenticate against any authentication system, the user account must first be defined within the Evergreen system, and authentication will be based on the user name as it exists in Evergreen.
A sample authentication mechanism for LDAP is provided in
Open-ILS::Application::AuthProxy::LDAP_AUTH, and corresponding sample
attributes can be found in opensrf.xml.example.
This enhancement adds user and workstation IDs to the auditor tables. It also adds/changes auditor functions to allow for setting, getting, and clearing auditor information, as well as adding a couple of utility functions for updating auditors after changes to their origin columns.
To support the creation of collection development reports, the following reporting sources have been added:
By default, two toolbars are available in the staff client: circulation and cataloging. This feature enables you to customize toolbars in the staff client. You can add buttons that will enable quick access to a variety of features. You can create toolbars for specific org unit(s), workstation(s), or login(s).
Documentation for this feature is available in the Book of Evergreen at http://docs.evergreen-ils.org/2.2/
You can search for a patron’s record, and double click on a result to access that record. You can double click on an item in the Holdings Maintenance screen to access copy information. The item is linked to the Volume/Copy Creator, if you turned it on in the staff client’s org unit settings. If you did not turn on the Volume/Copy Creator, then the item links to the Item Attributes.
Documentation for this feature is available in the Book of Evergreen at http://docs.evergreen-ils.org/2.2/
You can view your recent searches as you perform them in the staff client. By default, staff can view their recent searches, although the number is configurable. This feature is only available through the staff client; it is not available to patrons in the OPAC.
Documentation for this feature is available in the Book of Evergreen at http://docs.evergreen-ils.org/2.2/
This feature enables you to return to your title search results directly from any view of the MARC record, including the OPAC View, MARC Record, MARC Edit, and Holdings Maintenance views. You can use this feature to page through records in the MARC Record View or Edit interfaces. You do not have to return to the OPAC View to access title results.
Documentation for this feature is available in the Book of Evergreen at http://docs.evergreen-ils.org/2.2/
This feature enables you to sort by multiple display columns so that you can find easily the information that you need on a screen. You can sort display columns on any screen that is built on a grid, such as the Check In screen or the On Shelf Pull List.
You can also sort the columns on the following Administration screens:
You can sort items in an ascending or descending order, and you can prioritize the order in which columns will sort.
Documentation for this feature is available in the Book of Evergreen at http://docs.evergreen-ils.org/2.2/
This feature enables you to add a new tab to the Evergreen staff client by clicking the + sign adjacent to the tab that you currently have opened. As in previous versions, you can also add new tabs by clicking File → New Tab, or use the hotkey, Ctrl+T.
Documentation for this feature is available in the Book of Evergreen at http://docs.evergreen-ils.org/2.2/
Previously, all hold list interfaces shared the same column picker settings and receipt templates. This enhancement creates independent settings for the following interfaces:
List displays in the staff client now have a non-sortable line number column which displays the ordinal position of each row in the list. The first row in such a list will always have a value of 1 in the ordinal column, no matter how the list is sorted. There is no special handling for paged interfaces; the first row on any given page still gets an ordinal value of 1.